[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-ua-dev] BuildHelpIndex ant task problem in 3.2
|
Hi Curtis,
thank you so much for answering all my questions. I feel better already :)
Integrating our doc plugin into Eclipse 3.2 won't be as complicated as I
first imagined.
I added some comments to your answers.
Regards,
Pierre
Shouldn't you rather detect xhtml documents that use dynamic content
specific markup?
- It can, but there would be a significant performance cost. For example,
if you only have one instance of dynamic content at the very end of your
long document, it has to scan through the entire document just to find out
whether it has dynamic content.
You're absolutely right.
What if xhtml documents with dynamic content had a specific "dynamic
content" meta tag in their head element:
ex: <meta name="DynamicContent" content="true"/>
Would it be better, performance wise?
- While it is true that it now contains eclipse-specific content, browsers
must still be able to handle the xhtml and ignore the extra
eclipse-specific content. So it should not break any browsers as long as
they're compliant.
I wonder if Internet Explorer is XHTML 1.0 compliant...
Btw, how are you gonna overcome the problem mentioned at the bottom of this
page:
http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-doc-home/docs/EclipseStyle.htm
Can xhtml files and html files coexist in the same documentation plugin?
- Yes.
Then the XHTML conversion tool will have to be really careful when (and if)
link updating is implemented:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=135069
So as to not change a link from a non-javadoc file to a javadoc file, for
instance.
