[
https://issues.apache.org/jira/browse/DOXIA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626639#comment-17626639
]
ASF GitHub Bot commented on DOXIA-678:
--------------------------------------
michael-o commented on PR #126:
URL: https://github.com/apache/maven-doxia/pull/126#issuecomment-1297241475
> Looks good @michael-o ! However, how future proof is this approach? As you
mentioned, there aren't a ton of people able to maintain Doxia any more and I'm
a bit worried about all these specific tag lists in the code. Say 5 years from
now they invent a `<vr>` tag for Virtual Reality... will that now blow up the
logs with warnings if we use that in our site?
I do understand your concerns and you are right. While I cannot look into
the future, I have talked already about Doxia 3 with @hboutemy and Doxia 3 will
likely complete drop the parser/sink approach it will be a thin layer about
FlexMark/Asciidoctor maybe with JBake. I don't like Doxia's current complexity
and it isn't as useful as we it was be 10 or 15 years ago. We don't need a
Swiss Army knife yet another Pandoc anymore.
The current target of Doxia 2 is to drop luggage and remove workarounds.
Also consider that I am the only one maintaining Doxia for the last couple of
years...
> Add missing elements in Xhtml5BaseParser
> ----------------------------------------
>
> Key: DOXIA-678
> URL: https://issues.apache.org/jira/browse/DOXIA-678
> Project: Maven Doxia
> Issue Type: Task
> Components: Module - Xhtml
> Affects Versions: 2.0.0-M4
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 2.0.0-M5
>
>
> As found in DOXIA-667 by [~jdimeo], some elements aren't recognized. If they
> have Sink counterparts we need to add them to the detection in the parser.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
