v3 is not up to date and will be deleted in the process of FOR-798.
Further http://localhost:8888/samples/xhtml2_subset.html is using xhtml2 as input and not xdocs. This means that the pdf will not work anyway since we do not have a xhtml2-to-fo transformation established.
Another point is that the xhtml2 integration demonstrated in v3 needs to be done in a different way like I described in a couple of threads on dev (e.g. [RT] structurer location and resource types).
This issue will be actual when we base the dispatcher on xhtml2 as input format.
Thorsten Scherler added a comment - 20/Apr/06 10:07 PM v3 is not up to date and will be deleted in the process of FOR-798.
Further http://localhost:8888/samples/xhtml2_subset.html is using xhtml2 as input and not xdocs. This means that the pdf will not work anyway since we do not have a xhtml2-to-fo transformation established.
Another point is that the xhtml2 integration demonstrated in v3 needs to be done in a different way like I described in a couple of threads on dev (e.g. [RT] structurer location and resource types).
This issue will be actual when we base the dispatcher on xhtml2 as input format.
FOR-798.Further http://localhost:8888/samples/xhtml2_subset.html is using xhtml2 as input and not xdocs. This means that the pdf will not work anyway since we do not have a xhtml2-to-fo transformation established.
Another point is that the xhtml2 integration demonstrated in v3 needs to be done in a different way like I described in a couple of threads on dev (e.g. [RT] structurer location and resource types).
This issue will be actual when we base the dispatcher on xhtml2 as input format.