Re: XML Source Codes for 10.0 available
How can I compile for example English version of doc from that source code? I dont know how to work with NovDoc. I don't see enything suitable for building html or pdf. There is no documentation. SVN is empty. I'm not so cool hacker to understand it. -- Lafox.Net DocTeam Freelance Translator
Hi Pavel, On Thursday, 8. December 2005 14:54, Pavel Maryanov wrote:
How can I compile for example English version of doc from that source code?
Well, building books can be complicated for an inexperienced user. There are several Makefiles and stylesheets around our XML files. You need to setup this XML build environment first, before you can think of transforming the XML sources. After this it should be fairly easy. :)
I dont know how to work with NovDoc. I don't see enything suitable for building html or pdf. There is no documentation.
See [1]. In general you don't "work" directly with NovDoc. The Novdoc ist needed by the XML files to validate it. You only interact with the XML files, modify, add, delete them. But you don't change the Novdoc. However, the NovDoc is essential for building the books, because it contains not only the DTD but also a fair amount of XSLT stylesheets. These stylesheets transform it from our XML source into HTML or XSL-FO (which in an other step creates PDF).
SVN is empty.
I don't know where did you look but try [2]. HTH, Tom ------------ [1] svn cat \ svn+ssh://anonymous@forgesvn1.novell.com/svn/novdoc/trunk/doc/susemakedoc.pdf\
susemakedoc.pdf
[2] http://forge.novell.com/modules/xfmod/svn/svnbrowse.php?repname=novdoc -- Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX Products GmbH >o) Technical Editor Maxfeldstrasse 5 /\\ Documentation Team 90409 Nuernberg, Germany _\_v http://www.suse.com
SVN is empty.
I don't know where did you look but try [2].
My mistake. I've talked about suselinux-docs not novdoc. After fetching full tree of NovDoc it became more clearly for me.
[1] svn cat \
svn+ssh://anonymous@forgesvn1.novell.com/svn/novdoc/trunk/doc/susemakedoc.pdf\
susemakedoc.pdf
That is all I've needed. RTFM'ing :) -- Lafox.Net DocTeam Freelance Translator
Ufff... Quotation from susemakedoc.pdf ------------- 1. Adding a New Project <...> MAIN This is the MAIN file. The top level file of your document. All required files are included directly in this file, or in one of the included files. This file must exist in the xml subdirectory. ------------- I don't see this file in downloaded xml source code. But I have to declarate it in me ENV-* file. As I understood this MAIN file contains all structure of manual like a master.top.xml in Borges DMS (Mandriva). In other words it have to combine all xml-files in some order. I don't know its syntax. So can anyone provide this file to me? Or I just wrong understood idea of building docs? In Borges DMS it is much eaise to begin translation from scratch. Even compilation. Even for unexpirienced user. -- Lafox.Net DocTeam Freelance Translator
Hi Pavel, On Thursday, 8. December 2005 18:24, Pavel Maryanov wrote:
Ufff...
I didn't say it is easy. ;-)
Quotation from susemakedoc.pdf ------------- 1. Adding a New Project <...> MAIN This is the MAIN file. The top level file of your document. All required files are included directly in this file, or in one of the included files. This file must exist in the xml subdirectory. -------------
I don't see this file in downloaded xml source code. But I have to declarate it in me ENV-* file.
Yes, this file is missing. I will provide a new archive as soon as possible.
As I understood this MAIN file contains all structure of manual like a master.top.xml in Borges DMS (Mandriva). In other words it have to combine all xml-files in some order.
That's true. The MAIN*.xml file contains XInclude elements that point to other chapters, appendices and such.
I don't know its syntax. So can anyone provide this file to me? Or I just wrong understood idea of building docs?
No, you are right. The file is just missing.
In Borges DMS it is much eaise to begin translation from scratch. Even compilation. Even for unexpirienced user.
I don't know very much about this system. We choosed to design our own because of our needs. We have to maintain different text for different products and sometimes different architectures. To maintain these sorts of texts can be complicated and probably this system might be limited in this regard. Have fun, Tom -- Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX Products GmbH >o) Technical Editor Maxfeldstrasse 5 /\\ Documentation Team 90409 Nuernberg, Germany _\_v http://www.suse.com
In Borges DMS it is much eaise to begin translation from scratch. Even compilation. Even for unexpirienced user.
I don't know very much about this system. We choosed to design our own because of our needs. We have to maintain different text for different products and sometimes different architectures. To maintain these sorts of texts can be complicated and probably this system might be limited in this regard.
It's just a funny. Every distro uses its own documentation system: * Mandriva - Borges DMS * Debian - DebianDoc-SGML * Slackware - FreeBSD Documentation Project * OpenSUSE - NovDoc * ... And poor translators have to adopt to every of them :) OK. So now I'll begin translation at a first approximation. I'll have to do it in any case. -- Lafox.Net DocTeam Freelance Translator
Hi Pavel, On Friday, 9. December 2005 11:19, Pavel Maryanov wrote:
In Borges DMS it is much eaise to begin translation from scratch. Even compilation. Even for unexpirienced user.
I don't know very much about this system. We choosed to design our own because of our needs. We have to maintain different text for different products and sometimes different architectures. To maintain these sorts of texts can be complicated and probably this system might be limited in this regard.
It's just a funny. Every distro uses its own documentation system: * Mandriva - Borges DMS * Debian - DebianDoc-SGML * Slackware - FreeBSD Documentation Project * OpenSUSE - NovDoc * ...
Yes, it seems that of lot of wasted resources. :) However each distro have different documentation restrictions and the system must be able to take this into account. It seems that no system at the moment have everything that is useful for all. But I might be wrong.
And poor translators have to adopt to every of them :) OK.
Are the translators not everytime poor victims? ;)
So now I'll begin translation at a first approximation. I'll have to do it in any case.
Which language do you want to translate into? :-) Thanks, Tom -- Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX Products GmbH >o) Technical Editor Maxfeldstrasse 5 /\\ Documentation Team 90409 Nuernberg, Germany _\_v http://www.suse.com
participants (2)
-
Pavel Maryanov -
Thomas Schraitle