I have converted the specification document into xhtml and added it to the SVN repository along with a default css.
A have been using Amaya as an editor - it seems like a capable enough editor for this kind of document allowing WYSIWIG editing in general and source editing for some finer tweaks. If you hae a recomendation for a better editor, by all means drop me a line.
I would like to continue to use xhtml (or pure xml) for the document from now on, however I don't really have a solid background in xml,xhtml, and css 'best practice'. For example, I have sectioned the document using div element using the id attribute to allow construction of the table of contents (e.g. <div id="introduction">). I think this is standard practice - please correct me if I'm wrong. Can someone advise if using xhtml as the base document type and transforming to other document types from there is a good idea.
I guess what I will be needing more and more as work on the specification progresses is two things:
1) Comments on the content of the specification (and new content if you would like to contribute) and
2) Comments on the structure of the specification.
At the moment, I am focusing on using strictly standard xhtml 1.0 and CSS2 (CSS2.1 when released) - i.e. no browser extensions etc.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have converted the specification document into xhtml and added it to the SVN repository along with a default css.
A have been using Amaya as an editor - it seems like a capable enough editor for this kind of document allowing WYSIWIG editing in general and source editing for some finer tweaks. If you hae a recomendation for a better editor, by all means drop me a line.
I would like to continue to use xhtml (or pure xml) for the document from now on, however I don't really have a solid background in xml,xhtml, and css 'best practice'. For example, I have sectioned the document using div element using the id attribute to allow construction of the table of contents (e.g. <div id="introduction">). I think this is standard practice - please correct me if I'm wrong. Can someone advise if using xhtml as the base document type and transforming to other document types from there is a good idea.
I guess what I will be needing more and more as work on the specification progresses is two things:
1) Comments on the content of the specification (and new content if you would like to contribute) and
2) Comments on the structure of the specification.
At the moment, I am focusing on using strictly standard xhtml 1.0 and CSS2 (CSS2.1 when released) - i.e. no browser extensions etc.