RE: ATeXHI 1.0 or Babel Scribe 1.0

Hi Karl,

> the verbiage was repeating the same principles along the 
> document. The 
> document to be read by the outline. I Would encourage the editors to 
> write atomic statement for each feature and to not repeat the same 
> verbiage BUT to point to these atomic statement from 
> different outlines.
> 
> 	It will be like having modules addressing some 
> problems, and profiles 
> collecting a set of modules or features applied to specific 
> problems or 
> readers. It will have the advantage for the editor to be easier to 
> maintain as well and less confusing for the reader in certain 
> circumstances.


If I understand your suggestion correctly, you'll find that we do
exactly that.  The individual techniques are written in a 'repository'
document.  There's one for HTML and one for CSS so far.  Each technique
appears only once in a repository.  In addition there's a separate file
for references.  What you have looked at is a 'view' on the data adapted
for XHTML and HTML content authors.  There is no technique text at all
in the XML source for the view document - just links to techniques in
the repositories. Where a technique is repeated, this is produced by two
or more links to the same technique in the repository. We run XSLT on
the XML to produce the XHTML document you read with technique text and
appropriate references.

This is all described in our Framework doc
http://www.w3.org/TR/i18n-guide-framework/

You can see the repositories and related documentation on the GEO home
page at http://www.w3.org/International/geo/ (look for Miscellaneous
working documents on the left).

RI

Received on Saturday, 25 October 2003 06:44:55 UTC