steveb, da li predlazes da cekamo? Zna li se otprilike koliko (developement nikad nije moguce vremenski oceniti, ali barem nesto okvirno)? Ako ne treba da cekamo, imam dve molbe. Prvo, da li bi jedan od vas dvojice (steveb, vec duze vreme pricas sa neysx-om dok nam je daniel vodja projekta) mogao da pita neysx-a da li da je greska ako mi prevedemo linkove? Drugo, da li da pravim error.xml?
Common mistakes u prevodima
To mi je Xavier napisao na Date: Tue, 21 Mar 2006 11:13:24 +0100 (moje pitanje je quoted):
Kako vidite, on pise:
Znaci je nabolje da cekamo, dok on to sredi.
Pozdrav
Stevan
> BTW2: Gorg is very sensitive to errors in the XML documents. When you
> use the or > id="whatever">whatever.xml 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 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 " " 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).
> use the
> 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
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 "
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).
Kako vidite, on pise:
Until I can do better, next version of gorg will return " " when
libxml2 asks for a missing file.
libxml2 asks for a missing file.
Znaci je nabolje da cekamo, dok on to sredi.
Pozdrav
Stevan
daniele, ako ostavimo linkove da su .../en/... onda naš gorg nema smisla. Možeš pročitati index.xml i na svaki drugi link na koji klikneš će te baciti na englesku dokumentaciju. Zbog toga mislim da je bolje da se prevodi.
Evo "simple" bash script za "mail handbook # for _xml in *.xml ; do for _link in $(sed -n "s:.* Fali za handbook-amd64.xml: hb-install-network.xml
Fali za handbook-amd64.xml: hb-install-stage.xml
Fali za handbook-amd64.xml: hb-install-config.xml
Fali za handbook-amd64.xml: hb-install-finalise.xml
Fali za handbook-amd64.xml: hb-install-next.xml
Fali za handbook-amd64.xml: hb-working-portage.xml
Fali za handbook-amd64.xml: hb-working-features.xml
Fali za handbook-amd64.xml: hb-working-rcscripts.xml
Fali za handbook-amd64.xml: hb-working-variables.xml
Fali za handbook-amd64.xml: hb-portage-files.xml
Fali za handbook-amd64.xml: hb-portage-configuration.xml
Fali za handbook-amd64.xml: hb-portage-branches.xml
Fali za handbook-amd64.xml: hb-portage-diverttree.xml
Fali za handbook-amd64.xml: hb-portage-ebuild.xml
Fali za handbook-amd64.xml: hb-net-start.xml
Fali za handbook-amd64.xml: hb-net-advanced.xml
Fali za handbook-amd64.xml: hb-net-modules.xml
Fali za handbook-amd64.xml: hb-net-wireless.xml
Fali za handbook-amd64.xml: hb-net-functions.xml
Fali za handbook-amd64.xml: hb-net-management.xml
Fali za handbook-x86.xml: hb-install-x86-medium.xml
Fali za handbook-x86.xml: hb-install-network.xml
Fali za handbook-x86.xml: hb-install-x86-disk.xml
Fali za handbook-x86.xml: hb-install-stage.xml
Fali za handbook-x86.xml: hb-install-x86-kernel.xml
Fali za handbook-x86.xml: hb-install-config.xml
Fali za handbook-x86.xml: hb-install-x86-bootloader.xml
Fali za handbook-x86.xml: hb-install-finalise.xml
Fali za handbook-x86.xml: hb-install-next.xml
Fali za handbook-x86.xml: hb-working-portage.xml
Fali za handbook-x86.xml: hb-working-features.xml
Fali za handbook-x86.xml: hb-working-rcscripts.xml
Fali za handbook-x86.xml: hb-working-variables.xml
Fali za handbook-x86.xml: hb-portage-files.xml
Fali za handbook-x86.xml: hb-portage-configuration.xml
Fali za handbook-x86.xml: hb-portage-branches.xml
Fali za handbook-x86.xml: hb-portage-diverttree.xml
Fali za handbook-x86.xml: hb-portage-ebuild.xml
Fali za handbook-x86.xml: hb-net-start.xml
Fali za handbook-x86.xml: hb-net-advanced.xml
Fali za handbook-x86.xml: hb-net-modules.xml
Fali za handbook-x86.xml: hb-net-wireless.xml
Fali za handbook-x86.xml: hb-net-functions.xml
Fali za handbook-x86.xml: hb-net-management.xml
mail handbook #
Fali za handbook-amd64.xml: hb-install-stage.xml
Fali za handbook-amd64.xml: hb-install-config.xml
Fali za handbook-amd64.xml: hb-install-finalise.xml
Fali za handbook-amd64.xml: hb-install-next.xml
Fali za handbook-amd64.xml: hb-working-portage.xml
Fali za handbook-amd64.xml: hb-working-features.xml
Fali za handbook-amd64.xml: hb-working-rcscripts.xml
Fali za handbook-amd64.xml: hb-working-variables.xml
Fali za handbook-amd64.xml: hb-portage-files.xml
Fali za handbook-amd64.xml: hb-portage-configuration.xml
Fali za handbook-amd64.xml: hb-portage-branches.xml
Fali za handbook-amd64.xml: hb-portage-diverttree.xml
Fali za handbook-amd64.xml: hb-portage-ebuild.xml
Fali za handbook-amd64.xml: hb-net-start.xml
Fali za handbook-amd64.xml: hb-net-advanced.xml
Fali za handbook-amd64.xml: hb-net-modules.xml
Fali za handbook-amd64.xml: hb-net-wireless.xml
Fali za handbook-amd64.xml: hb-net-functions.xml
Fali za handbook-amd64.xml: hb-net-management.xml
Fali za handbook-x86.xml: hb-install-x86-medium.xml
Fali za handbook-x86.xml: hb-install-network.xml
Fali za handbook-x86.xml: hb-install-x86-disk.xml
Fali za handbook-x86.xml: hb-install-stage.xml
Fali za handbook-x86.xml: hb-install-x86-kernel.xml
Fali za handbook-x86.xml: hb-install-config.xml
Fali za handbook-x86.xml: hb-install-x86-bootloader.xml
Fali za handbook-x86.xml: hb-install-finalise.xml
Fali za handbook-x86.xml: hb-install-next.xml
Fali za handbook-x86.xml: hb-working-portage.xml
Fali za handbook-x86.xml: hb-working-features.xml
Fali za handbook-x86.xml: hb-working-rcscripts.xml
Fali za handbook-x86.xml: hb-working-variables.xml
Fali za handbook-x86.xml: hb-portage-files.xml
Fali za handbook-x86.xml: hb-portage-configuration.xml
Fali za handbook-x86.xml: hb-portage-branches.xml
Fali za handbook-x86.xml: hb-portage-diverttree.xml
Fali za handbook-x86.xml: hb-portage-ebuild.xml
Fali za handbook-x86.xml: hb-net-start.xml
Fali za handbook-x86.xml: hb-net-advanced.xml
Fali za handbook-x86.xml: hb-net-modules.xml
Fali za handbook-x86.xml: hb-net-wireless.xml
Fali za handbook-x86.xml: hb-net-functions.xml
Fali za handbook-x86.xml: hb-net-management.xml
mail handbook #
A za "
Promeni "/var/www/vu-hosting/gentoo-srbija.org/htdocs.docs" sa tvojim root gde je dokumentacia.
Pozdrav
Stevan
Sve je to lepo ali mogao bi neko nesto i da prevede :)
Pa prevedi!
12. apr. 06. 16:00