Bug#257150: Any timeframe for updating the developers reference?
Hi, I think DDP documents are build from svn.debian.org (an alioth service) these days. cvs.debian.org is not used any more. http://svn.debian.org/wsvn/ddp/manuals/trunk/developers-reference/ (Unlike web contents where CVS is used and SVN is some kind of dummy) On Thu, Jun 04, 2009 at 09:55:39PM +0200, Helge Kreutzmann wrote: Hello, On Sun, Aug 05, 2007 at 02:14:17AM +0200, Nicolas François wrote: On Sat, Aug 04, 2007 at 08:43:58PM +0200, hert...@debian.org wrote: retitle 257150 Paragraph about i18ned documentation is outdated severity 257150 normal thanks Replying to an old bug and discussion. The same, trying to come to a conclusion On Sun, 18 Sep 2005, Frédéric Bothamy wrote: * Helge Kreutzmann kreu...@itp.uni-hannover.de [2005-09-18 13:15] : the french team has some people very capable of all the details regarding translation. Maybe you can ask them to update 6.6.2 Internationalized documentation which would a) close my bug and b) help other translators. Do you think this is possible for Etch? AFAIK doc-check is not available in any package now. It is available in some CVS (for instance for the securing-howto). I think that the whole paragraph is outdated anyway. It doesn't make much sense to update the link in those conditions. Well, it seems doc-check is still used in D-I, so I preferred to update the link to point to D-I's doc-check. Fine with me, but apparently (according to Lucas) this maybe is not true anymore? Could you provide a current link, valid for D-I? Currently this chapter is broken, it states: An interesting system is provided by doc-check in the boot-floppies package ... This is clearly outdated. Given that the reference is much broader, such left over use might not be worth mentioning it here? Nowadays, po4a or poxml are preferred to handle translations of documents. It looks like Nicolas François (in CC) could write us a little paragraph on this topic. I've added a paragraph mentioning these tools, and a paragraph mentioning the quite complete document written for DebConf6 by Christian and Javier about Internationalization in Debian. Sorry, I could not find this paragraph in chapter 6 of the developer refererence - where did you add it? I think such content would be highly desirable here. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#257150: Any timeframe for updating the developers reference?
Hello, On Sun, Aug 05, 2007 at 02:14:17AM +0200, Nicolas François wrote: On Sat, Aug 04, 2007 at 08:43:58PM +0200, hert...@debian.org wrote: retitle 257150 Paragraph about i18ned documentation is outdated severity 257150 normal thanks Replying to an old bug and discussion. The same, trying to come to a conclusion On Sun, 18 Sep 2005, Frédéric Bothamy wrote: * Helge Kreutzmann kreu...@itp.uni-hannover.de [2005-09-18 13:15] : the french team has some people very capable of all the details regarding translation. Maybe you can ask them to update 6.6.2 Internationalized documentation which would a) close my bug and b) help other translators. Do you think this is possible for Etch? AFAIK doc-check is not available in any package now. It is available in some CVS (for instance for the securing-howto). I think that the whole paragraph is outdated anyway. It doesn't make much sense to update the link in those conditions. Well, it seems doc-check is still used in D-I, so I preferred to update the link to point to D-I's doc-check. Fine with me, but apparently (according to Lucas) this maybe is not true anymore? Could you provide a current link, valid for D-I? Currently this chapter is broken, it states: An interesting system is provided by doc-check in the boot-floppies package ... This is clearly outdated. Given that the reference is much broader, such left over use might not be worth mentioning it here? Nowadays, po4a or poxml are preferred to handle translations of documents. It looks like Nicolas François (in CC) could write us a little paragraph on this topic. I've added a paragraph mentioning these tools, and a paragraph mentioning the quite complete document written for DebConf6 by Christian and Javier about Internationalization in Debian. Sorry, I could not find this paragraph in chapter 6 of the developer refererence - where did you add it? I think such content would be highly desirable here. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
Bug#257150: Any timeframe for updating the developers reference?
tags 257150 - patch thanks Hi, Since the patch for bug #257150 is apparently outdated itself, I'm removing the patch tag. It would really be great if someone from the i18n front would take some time to update the developers-reference on that. Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#257150: Any timeframe for updating the developers reference?
On Sat, Aug 04, 2007 at 08:43:58PM +0200, [EMAIL PROTECTED] wrote: retitle 257150 Paragraph about i18ned documentation is outdated severity 257150 normal thanks Replying to an old bug and discussion. On Sun, 18 Sep 2005, Frédéric Bothamy wrote: * Helge Kreutzmann [EMAIL PROTECTED] [2005-09-18 13:15] : Hello, the french team has some people very capable of all the details regarding translation. Maybe you can ask them to update 6.6.2 Internationalized documentation which would a) close my bug and b) help other translators. Do you think this is possible for Etch? AFAIK doc-check is not available in any package now. It is available in some CVS (for instance for the securing-howto). I think that the whole paragraph is outdated anyway. It doesn't make much sense to update the link in those conditions. Well, it seems doc-check is still used in D-I, so I preferred to update the link to point to D-I's doc-check. Nowadays, po4a or poxml are preferred to handle translations of documents. It looks like Nicolas François (in CC) could write us a little paragraph on this topic. I've added a paragraph mentioning these tools, and a paragraph mentioning the quite complete document written for DebConf6 by Christian and Javier about Internationalization in Debian. Kind Regards, -- Nekral diff -rauN ../orig/developers-reference-3.3.8/common.ent ./developers-reference-3.3.8/common.ent --- ../orig/developers-reference-3.3.8/common.ent 2006-11-11 19:13:05.0 +0100 +++ ./developers-reference-3.3.8/common.ent 2007-08-05 01:15:22.0 +0200 @@ -111,7 +111,7 @@ !ENTITY url-dmup http://www-debian-org;/devel/dmup; !ENTITY url-worldmap http://www-debian-org;/devel/developers.loc; -!ENTITY url-i18n-doc-check http://cvs.debian.org/boot-floppies/documentation/doc-check?rev=HEADamp;content-type=text/vnd.viewcvs-markup; +!ENTITY url-i18n-doc-check http://svn.debian.org/wsvn/d-i/trunk/manual/scripts/doc-check?op=file; !ENTITY url-eg-desc-upstream-info http://packages-host;/unstable/web/wml; diff -rauN ../orig/developers-reference-3.3.8/developers-reference.sgml ./developers-reference-3.3.8/developers-reference.sgml --- ../orig/developers-reference-3.3.8/developers-reference.sgml 2006-11-12 12:05:22.0 +0100 +++ ./developers-reference-3.3.8/developers-reference.sgml 2007-08-05 01:59:26.0 +0200 @@ -4577,6 +4577,12 @@ sect id=bpp-i18n headingInternationalization/heading +p +This section contains global information for developers to make translators' +life easier. More information for translators and developers interrested +in internationalization are available in the +url id=http://people.debian.org/~jfs/debconf6/html/; +name=Internationalisation and localisation in Debian documentation. sect1 id=bpp-i18n-debconf headingHandling debconf translations/heading @@ -4614,25 +4620,30 @@ labor. There's no way to eliminate all that work, but you can make things easier for translators. p -If you maintain documentation of any size, its easier for translators +If you maintain documentation of any size, it is easier for translators if they have access to a source control system. That lets translators see the differences between two versions of the documentation, so, for instance, they can see what needs to be retranslated. It is recommended that the translated documentation maintain a note about what source control revision the translation is based on. An interesting system is provided by url id=url-i18n-doc-check; -name=doc-check in the packageboot-floppies/package package, +name=doc-check in the packaged-i/package package, which shows an overview of the translation status for any given language, using structured comments for the current revision of the file to be translated and, for a translated file, the revision of the original file the translation is based on. You might wish to adapt -and provide that in your CVS area. +and provide that in your Subversion area. p If you maintain XML or SGML documentation, we suggest that you isolate any language-independent information and define those as entities in a separate file which is included by all the different translations. This makes it much easier, for instance, to keep URLs up to date across multiple files. + p +Some tools (e.g. po4a, poxml, or the translate-toolkit) are specialized in +extracting the translatable material from different formats. They produce +PO files, a format quite common to translators, which permits to see what +needs to be retranslated when the translated document is updated. /sect1 /sect
Bug#257150: Any timeframe for updating the developers reference?
retitle 257150 Paragraph about i18ned documentation is outdated severity 257150 normal thanks Replying to an old bug and discussion. On Sun, 18 Sep 2005, Frédéric Bothamy wrote: * Helge Kreutzmann [EMAIL PROTECTED] [2005-09-18 13:15] : Hello, the french team has some people very capable of all the details regarding translation. Maybe you can ask them to update 6.6.2 Internationalized documentation which would a) close my bug and b) help other translators. Do you think this is possible for Etch? AFAIK doc-check is not available in any package now. It is available in some CVS (for instance for the securing-howto). I think that the whole paragraph is outdated anyway. It doesn't make much sense to update the link in those conditions. Nowadays, po4a or poxml are preferred to handle translations of documents. It looks like Nicolas François (in CC) could write us a little paragraph on this topic. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/
Bug#257150: Any timeframe for updating the developers reference?
* Raphael Hertzog ([EMAIL PROTECTED]) [070804 20:44]: I think that the whole paragraph is outdated anyway. It doesn't make much sense to update the link in those conditions. Nowadays, po4a or poxml are preferred to handle translations of documents. It looks like Nicolas François (in CC) could write us a little paragraph on this topic. Last I looked at this bug the referenced link was not acceptable - of course if someone writes a good new paragraph about this topic, it will be included in the next round of updates to the developers reference. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#257150: Any timeframe for updating the developers reference?
Hello, the french team has some people very capable of all the details regarding translation. Maybe you can ask them to update 6.6.2 Internationalized documentation which would a) close my bug and b) help other translators. Do you think this is possible for Etch? Greetings Helge -- Dr. Helge Kreutzmann, Dipl.-Phys. [EMAIL PROTECTED] gpg signed mail preferred 64bit GNU powered http://www.itp.uni-hannover.de/~kreutzm Help keep free software libre: http://www.ffii.de/ pgp1s1YRsfayZ.pgp Description: PGP signature
Bug#257150: Any timeframe for updating the developers reference?
* Helge Kreutzmann ([EMAIL PROTECTED]) [050918 13:19]: the french team has some people very capable of all the details regarding translation. Maybe you can ask them to update 6.6.2 Internationalized documentation which would a) close my bug and b) help other translators. Do you think this is possible for Etch? well, basically my approach is: If someone updates the bug with a patch, I'll apply it. :) I proded Frans now. Cheers, Andi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#257150: Any timeframe for updating the developers reference?
* Helge Kreutzmann [EMAIL PROTECTED] [2005-09-18 13:15] : Hello, the french team has some people very capable of all the details regarding translation. Maybe you can ask them to update 6.6.2 Internationalized documentation which would a) close my bug and b) help other translators. Do you think this is possible for Etch? AFAIK doc-check is not available in any package now. It is available in some CVS (for instance for the securing-howto). What about this temporary patch: Index: common.ent === RCS file: /cvs/debian-doc/ddp/manuals.sgml/developers-reference/common.ent,v retrieving revision 1.67 diff -u -u -r1.67 common.ent --- common.ent 26 Jun 2005 21:13:05 - 1.67 +++ common.ent 18 Sep 2005 12:44:02 - @@ -111,7 +111,7 @@ !ENTITY url-dmup http://www-debian-org;/devel/dmup; !ENTITY url-worldmap http://www-debian-org;/devel/developers.loc; -!ENTITY url-i18n-doc-check http://cvs.debian.org/boot-floppies/documentation/doc-check?rev=HEADamp;content-type=text/vnd.viewcvs-markup; +!ENTITY url-i18n-doc-check http://cvs.debian.org/ddp/manuals.sgml/securing-howto/bin/doc-check?rev=HEADamp;cvsroot=debian-docamp;content-type=text/vnd.viewcvs-markup; !ENTITY url-eg-desc-upstream-info http://packages-host;/unstable/text/docbook-dsssl.html; Index: developers-reference.sgml === RCS file: /cvs/debian-doc/ddp/manuals.sgml/developers-reference/developers-reference.sgml,v retrieving revision 1.270 diff -u -u -r1.270 developers-reference.sgml --- developers-reference.sgml 13 Jul 2005 07:07:10 - 1.270 +++ developers-reference.sgml 18 Sep 2005 12:44:03 - @@ -4503,7 +4503,7 @@ recommended that the translated documentation maintain a note about what source control revision the translation is based on. An interesting system is provided by url id=url-i18n-doc-check; -name=doc-check in the packageboot-floppies/package package, +name=doc-check in the packagesecuring-howto/package CVS, which shows an overview of the translation status for any given language, using structured comments for the current revision of the file to be translated and, for a translated file, the revision of the Note: the amp; does not work correctly in HTML, pdf and txt output files, but I have not found a generic working solution (apart from putting the URL in the sgml file). Fred -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#257150: Any timeframe for updating the developers reference?
On Sun, Sep 18, 2005 at 03:12:48PM +0200, Frédéric Bothamy wrote: * Helge Kreutzmann [EMAIL PROTECTED] [2005-09-18 13:15] : Hello, the french team has some people very capable of all the details regarding translation. Maybe you can ask them to update 6.6.2 Internationalized documentation which would a) close my bug and b) help other translators. Do you think this is possible for Etch? AFAIK doc-check is not available in any package now. It is available in some CVS (for instance for the securing-howto). This is because this script does not separate data such as subdoc file names from executable. By the way, my doc-check script for debian-reference is the one created this issue. Sorry :-) By the way, people should think about what I do with this script during package building. When my debian-reference is build from upstream CVS, it create base CVS version table and include it to REAME file. Osamu
