ar 10 22:37:10 mail gorg[4966]: DEBUG Cache hit on /doc/sr/table.xml failed: (Empty/No meta file)
Mar 10 22:37:10 mail gorg[4966]: ERROR do_CGI() failed: xmlErrMsg:failed to load external entity "xsl/guide.xsl"<br/>xmlErrLevel:1<br/>xmlErrCode:1549
Mar 10 22:37:10 mail gorg[4966]: DEBUG Cache hit on /doc/sr/table.xml failed: (Empty/No meta file)
Mar 10 22:37:10 mail gorg[4966]: ERROR do_CGI() failed: xmlErrMsg:failed to load external entity "xsl/guide.xsl"<br/>xmlErrLevel:1<br/>xmlErrCode:1549
Mar 10 22:37:10 mail gorg[4966]: DEBUG Cache hit on /doc/sr/table.xml failed: (Empty/No meta file)
Mar 10 22:37:10 mail gorg[4966]: ERROR do_CGI() failed: xmlErrMsg:failed to load external entity "xsl/guide.xsl"<br/>xmlErrLevel:1<br/>xmlErrCode:1549

z10n reče da će izmeniti izgled, ali to se ne dešava. Sad ... ne bih da se trpam, ali pošto je prošlo 6 dana a nema pomaka, da li da ja to uzmem u svoje ruke? Nije mi problem samo da ne dupliramo posao.

> Hallo Xavier
>
> Want to keep you informed about their progress. Today they updated some
> stuff on the server. The look and feel is not anymore the same way as it
> is on gentoo.org. Have a look:
> http://docs.gentoo-srbija.org/doc/sr/index.xml
>

Much better indeed, Thanks.

> BTW2: Gorg is very sensitive to errors in the XML documents. When you
> use the <include href="whatever.xml"/> or <file
> id="whatever">whatever.xml</file> and the file is not on the file
> system, then gorg is crashing with "child pid 28931 exit signal
> Segmentation fault (11)". Turning on debug information does not show
> what the reason is for the crash. It would be a nice option, if I could
> turn on a switch in gorg.conf to force gorg to check the existence of
> the file, before including it and when needed print out error statements
> in the log so that tracing down the error can be done more easy. I can
> imagine, that this would slow down gorg, but that was the reason I wrote
> about a option in gorg.conf. Like this the option can be enabled or
> disabled.

Gorg does not know the <include> tag because it's a tag we made up like all
other GuideXML tags. Gorg does not know anything about guidexml at all because
that would tie it up with gentoo docs. It can apply any xsl to any xml, and it
uses libxslt/libxml2 for that.
I can't reproduce the segfault. Could be a problem in libxml2 itself?
You should get the following error as returned by libxml2:
"""
Internal Server Error
xmlErrMsg:failed to load external entity
"/home/neysx/gentoo.org/neysx.gentoo/tmp/htdocs/doc/fr/handbook/b-inst all-about.xml"
xmlErrLevel:1
xmlErrCode:1549
"""

I've tested gorg on various platforms: x86 (hardened and not), sparc, amd64,
hppa. It's ppc64 marked, so I suppose it works there too, I'll test it on my
PPC G3 in the coming months.

This happens when the document('file') XSL function is used and 'file' does
not exist. The standard says it's ok to either return an error or ignore it.
As AxKit (still used on 1 www.g.o node out of 3) returns a 500 error, I made
gorg do the same. I had thought about adding a parameter to ignore error 1549,
but it could be masked by another error. I'd have to investigate more deeply
in the libxml2 api and I'm not sure the xsl could test whether document()
returns nothing.
Until I can do better, next version of gorg will return "<empty/>" when
libxml2 asks for a missing file. No more error and the xsl can test whether
the file exists. It's a bit hackish because I don't know that libxml2 is
asking for an xml file as a result of a document() call. All files are
requested the same way (catalog, xsl, dtd, main xml file, a document() call).

> BTW3: What is the policy about including non standard characters in the
> documentation? Does Gentoo want the special characters to be included in
> the &#xxx; notation or is it enought if the XML file is in pure UTF-8
> format? (Writing cyrillic in &#xxx; notation would be hell, but if
> Gentoo requires &#xxx; notation, then I will help the SR guys out to
> write a small bash script to change the characters with GNU SED to the
> &#xxx; notation)

Policy is that &#xxx; or &entity; sould be the exception. Even the odd &#xxx;
makes the doc hard to read unless you happen to know which character it
corresponds to.
Look at all our Russian/Korean/Japanese/Chinese/Vietnamese/Greek...
Even European languages use "funny" characters with accents, cedillas,
strokes, tildes...
FYI, &nbsp; is defined in the DTD as some languages require non-breakable
spaces, eg. near punctuation marks in French, or after one-letter propositions
in Czech

Inace jedno pitanje svima sad: DA li treba da se prevode linkovi. npr /doc/en/guide.xml => /doc/sr/guide.xml ?

Mislim da ne treba prevoditi linkove, ali stvarno nisam siguran. Daniele, možeš li pitati ljude?

O kojim je dokumentima reč i gde se nalaze ti /doc/en/guide.xml linkovi ?

<rez>
Next, there's a <guide> tag -- the entire guide document is enclosed within a <guide> </guide> pair. The link attribute is compulsory and should preferably contain the absolute path to the document relatively to the document root even though the file name alone will work. It is mainly used to generate a link to a printer-friendly version of your document. If you use a wrong value, the link to the printable version will either not work or point to a wrong document. Translated documents must specify the full path because it is also used to check whether a more recent original document exists. The lang attribute should be used to specify the language code of your document. It is used to format the date and insert strings like "Note", "Content", etc. in the specified language. The default is English.
</rez>

to sam stavio samo primer i mislim da tako i pise. Pitao sam za linkove koji se nalaze u dokumentima koje prevodimo jel treba da promenimo sa ../en/.. na ../sr/.. ako razumes.

 
/doc/en/a.xml 
| 
+--[includes link to]--> /doc/en/b.xml 
| 
+--[includes/references]--> /doc/en/c.xml