 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
We are near to translate all the documentation of POV-Ray. My biggest
dude is There is a standard format to write the documentation? we'd like
to incorporate the documentation toevery platform where POV is, and we
don't want re-write it every time.
Someone can help me?
May be someone can tell me how the documentation is constructed, or
where can I read it.
Thanks
--
Hasta Pronto.
Roberto Selva
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Roberto Selva heeft geschreven in bericht <36CF3A84.E72336CF@ctv.es>...
>We are near to translate all the documentation of POV-Ray. My biggest
>dude is There is a standard format to write the documentation? we'd like
>to incorporate the documentation toevery platform where POV is, and we
>don't want re-write it every time.
A standard? HTML maybe...
>Someone can help me?
>
>May be someone can tell me how the documentation is constructed, or
>where can I read it.
>
>Thanks
>--
>Hasta Pronto.
>Roberto Selva
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Not HTML. You should write it in XML. What you describe is exactly the king
of thing XML was designed to handle.
Once you have good XML markup, then it's fairly easy to get it 'published'
into whatever format you need. At one talk I attended, the presentation was
HTML slides and RTF & Postscript printout to go along with it, both
automatically generated from the same XML source. He just applied a different
DSSL stylesheet. And if you 'publish' to the proper flavor of RTF you can get
the output you need for building Windows help files, etc.
In practice, as you go along you might need to convert your XML markup from
one form to another (depending on which tools, if any, are to be used), but
as long as all the needed logical information was included to begin with,
automatically converting from one 'flavor' of XML to another is easy.
XML is also Unicode (a big win for the non-English versions).
Zeger Knaepen wrote:
> Roberto Selva heeft geschreven in bericht <36CF3A84.E72336CF@ctv.es>...
> >We are near to translate all the documentation of POV-Ray. My biggest
> >dude is There is a standard format to write the documentation? we'd like
> >to incorporate the documentation toevery platform where POV is, and we
> >don't want re-write it every time.
>
> A standard? HTML maybe...
>
> >Someone can help me?
> >
> >May be someone can tell me how the documentation is constructed, or
> >where can I read it.
> >
> >Thanks
> >--
> >Hasta Pronto.
> >Roberto Selva
> >
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sat, 20 Feb 1999 23:43:16 +0100, Roberto Selva <rse### [at] ctv es>
wrote:
>We are near to translate all the documentation of POV-Ray. My biggest
>dude is There is a standard format to write the documentation? we'd like
>to incorporate the documentation toevery platform where POV is, and we
>don't want re-write it every time.
>
>Someone can help me?
>
>May be someone can tell me how the documentation is constructed, or
>where can I read it.
>
>Thanks
I would suggest HTML 1.0 or PDF
Peter
---------
Peter Popov
ICQ: 15002700
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Can you tell me where can I find more information about XML? I'm very int
erested.
> Not HTML. You should write it in XML. What you describe is exactly the
king
> of thing XML was designed to handle.
>
> Once you have good XML markup, then it's fairly easy to get it 'publish
ed'
> into whatever format you need. At one talk I attended, the presentation
was
> HTML slides and RTF & Postscript printout to go along with it, both
> automatically generated from the same XML source. He just applied a dif
ferent
> DSSL stylesheet. And if you 'publish' to the proper flavor of RTF you c
an get
> the output you need for building Windows help files, etc.
>
> In practice, as you go along you might need to convert your XML markup
from
> one form to another (depending on which tools, if any, are to be used),
but
> as long as all the needed logical information was included to begin wit
h,
> automatically converting from one 'flavor' of XML to another is easy.
>
> XML is also Unicode (a big win for the non-English versions).
>
> Zeger Knaepen wrote:
>
> > Roberto Selva heeft geschreven in bericht <36CF3A84.E72336CF@ctv.es>.
..
> > >We are near to translate all the documentation of POV-Ray. My bigges
t
> > >dude is There is a standard format to write the documentation? we'd
like
> > >to incorporate the documentation toevery platform where POV is, and
we
> > >don't want re-write it every time.
> >
> > A standard? HTML maybe...
> >
> > >Someone can help me?
> > >
> > >May be someone can tell me how the documentation is constructed, or
> > >where can I read it.
> > >
> > >Thanks
> > >--
> > >Hasta Pronto.
> > >Roberto Selva
> > >
--
Hasta Pronto.
Roberto Selva rse### [at] tandecom
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Well, one starting place is the World Wide Web Consortium
http://www.w3.org/
http://www.w3.org/XML/
If you want to do some coding in Java, I'd suggest getting IBM's XML parser from
alphaWorks http://www.alphaWorks.ibm.com/
James Clark has some good stuff
http://www.jclark.com/xml/
Just beware of any XML tools/stuff that Microsoft is putting out.
Oh, and here's the HTML version of that presentation I mentioned. It's by Jon Bosak.
http://www.unicode.org/unicode/iuc/iuc13/k2/sld00000.htm
It includes details about how it was made:
http://www.unicode.org/unicode/iuc/iuc13/k2/sld01005.htm
Roberto Selva wrote:
> Can you tell me where can I find more information about XML? I'm very interested.
>
>
> > Not HTML. You should write it in XML. What you describe is exactly the king
> > of thing XML was designed to handle.
> [SNIP]
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
