February 2005 - Devel - Po4a List Archives

[Po4a-devel]FOSDEM 2005

by Nicolas François

Hello, FYI: http://wiki.fosdem.org/tiki-index.php?page=LightningTalks -- Nekral

19 years, 2 months

1
0
0 / 0

[Po4a-devel]Re: [Po4a-commits] po4a/lib/Locale/Po4a Man.pm,1.76,1.77 Xml.pm,1.24,1.25

by Martin Quinson

On Tue, Feb 15, 2005 at 03:47:37PM +0000, Jordi Vilalta wrote: > Update of /cvsroot/po4a/po4a/lib/Locale/Po4a > In directory haydn:/tmp/cvs-serv7743 > > Modified Files: > Man.pm Xml.pm > Log Message: > Change "warn + exit 0" for "die" (exit 0 means "all ok" in the shell) Yes, exactly. warn + exit 0 is different than die, which means "problem". The difference between both is used to separate the cases where this is a user problem (try on pod generated pages => no error) from cases where we don't have any good solution to propose to the users... I'm not sure merging both it a good idea. Thanks for your time, Mt.

19 years, 2 months

2
1
0 / 0

[Po4a-devel]Minor documentation review

by Danilo Piazzalunga

Hello, While reading the documentation to translate it, I've found some spelling errors, typos, and such minor errors. At last, the time has come to submit this. A summary of the proposed changes follows: * Fix some (mostly cosmetic) typos, without changing the meaning of anything. For example: - Change case, e.g. s/french/French/. - Use consistently 'addenda' as the plural form for 'addendum'. - s/somehow/somewhat/ when the meaning is 'rather', 'to some degree' and not 'for some reason'. - Fix some spelling errors, like s/formating/formatting/ and s/dupplicate/duplicate/. If any changes are approved and if everybody agrees, I will also (try to) take care string unfuzzyfication. Cheers, Danilo -- Danilo Piazzalunga +--------------------+ PGP Key available at subkeys.pgp.net | Linux User #245762 | Fingerprint: D018 815E 8C7F 2AE2 5565 | ICQ #105550412 | 0C36 B5F6 DB20 B800 CB9F +--------------------+ [Danilo Piazzalunga] (documentation) * Fix some (mostly cosmetic) typos, without changing the meaning of anything. For example: - Change case, e.g. s/french/French/. - Use consistently 'addenda' as the plural form for 'addendum'. - s/somehow/somewhat/ when the meaning is 'rather', 'to some degree' and not 'for some reason'. - Fix some spelling errors, like s/formating/formatting/ and s/dupplicate/duplicate/. * TODO: string unfuzzyfication (let's be friendly to fellow translators). Index: po4a =================================================================== RCS file: /cvsroot/po4a/po4a/po4a,v retrieving revision 1.22 diff -u -r1.22 po4a --- po4a 11 Feb 2005 10:18:21 -0000 1.22 +++ po4a 14 Feb 2005 13:31:42 -0000 @@ -14,7 +14,7 @@ =head1 NAME -po4a - Update both the po files and translated documents in one shot +po4a - update both the po files and translated documents in one shot =head1 SYNOPSIS @@ -87,8 +87,8 @@ add_fr:doc/l10n/script.fr.add This should be rather self-explanatory also. Note that in the second case, -doc/l10n/script.fr.add is an addendum to add to the french version of this document. -Please refer to po4a(7) for more information about the addendums. +doc/l10n/script.fr.add is an addendum to add to the French version of this document. +Please refer to po4a(7) for more information about the addenda. More formally, the format is: @@ -99,7 +99,7 @@ [type: pod] script $lang:doc/$lang/script.1 add_fr:doc/l10n/script.fr.add -If all the languages had addendums with similar paths, you could also write +If all the languages had addenda with similar paths, you could also write something like: [type: pod] script $lang:doc/$lang/script.1 add_$lang:doc/l10n/script.$lang.add @@ -132,7 +132,8 @@ =item -A, --addendum-charset -Charset of the addenda. Note that all addenda should be in the same charset. +Charset of the addenda. Note that all the addenda should be in the same +charset. =item -V, --version @@ -152,7 +153,7 @@ =back -=head1 SHORTCOMING +=head1 SHORTCOMINGS =over 4 Index: po4a-gettextize =================================================================== RCS file: /cvsroot/po4a/po4a/po4a-gettextize,v retrieving revision 1.26 diff -u -r1.26 po4a-gettextize --- po4a-gettextize 5 Feb 2005 13:03:22 -0000 1.26 +++ po4a-gettextize 14 Feb 2005 13:31:42 -0000 @@ -14,7 +14,7 @@ =head1 NAME -po4a-gettextize - Convert an original file (and its translation) to a po file +po4a-gettextize - convert an original file (and its translation) to a po file =head1 SYNOPSIS Index: po4a-normalize =================================================================== RCS file: /cvsroot/po4a/po4a/po4a-normalize,v retrieving revision 1.20 diff -u -r1.20 po4a-normalize --- po4a-normalize 5 Feb 2005 13:03:22 -0000 1.20 +++ po4a-normalize 14 Feb 2005 13:31:42 -0000 @@ -14,7 +14,7 @@ =head1 NAME -po4a-normalize - Normalize a documentation file by parsing it in po4a, and writing it back +po4a-normalize - normalize a documentation file by parsing it in po4a, and writing it back =head1 SYNOPSIS Index: po4a-translate =================================================================== RCS file: /cvsroot/po4a/po4a/po4a-translate,v retrieving revision 1.32 diff -u -r1.32 po4a-translate --- po4a-translate 5 Feb 2005 13:03:22 -0000 1.32 +++ po4a-translate 14 Feb 2005 13:31:43 -0000 @@ -14,7 +14,7 @@ =head1 NAME -po4a-translate - convert back po file to documentation format. +po4a-translate - convert a po file back to documentation format =head1 SYNOPSIS @@ -51,7 +51,8 @@ =item -A, --addendum-charset -Charset of the addenda. Note that all addenda should be in the same charset. +Charset of the addenda. Note that all the addenda should be in the same +charset. =item -m, --master Index: po4a-updatepo =================================================================== RCS file: /cvsroot/po4a/po4a/po4a-updatepo,v retrieving revision 1.29 diff -u -r1.29 po4a-updatepo --- po4a-updatepo 5 Feb 2005 13:03:22 -0000 1.29 +++ po4a-updatepo 14 Feb 2005 13:31:43 -0000 @@ -14,7 +14,7 @@ =head1 NAME -po4a-updatepo - Update the translation (in po format) of documentation. +po4a-updatepo - update the translation (in po format) of documentation =head1 SYNOPSIS Index: doc/po4a.7.pod =================================================================== RCS file: /cvsroot/po4a/po4a/doc/po4a.7.pod,v retrieving revision 1.33 diff -u -r1.33 po4a.7.pod --- doc/po4a.7.pod 7 Jan 2005 22:50:51 -0000 1.33 +++ doc/po4a.7.pod 14 Feb 2005 13:31:44 -0000 @@ -91,16 +91,16 @@ I like the idea of open-source software, making it possible for everybody to access to software and to their source code. But being French, I'm well aware that the licensing is not the only restriction to the openness of -software: Non-translated free softwares are useless for non-English -speakers, and we still have some work to make them available to really +software: non-translated free software is useless for non-English +speakers, and we still have some work to make it available to really everybody out there. The perception of this situation by the open-source actors did dramatically -improved recently. We, as translators, won the first battle and convinced +improve recently. We, as translators, won the first battle and convinced everybody of the translations' importance. But unfortunately, it was the easy part. Now, we have to do the job and actually translate all this stuff. -Actually, the open-source software themselves benefit of a rather decent +Actually, open-source software themselves benefit of a rather decent level of translation, thanks to the wonderful gettext tool suite. It is able to extract the strings to translate from the program, present a uniform format to translators, and then use the result of their works at run time to @@ -108,7 +108,7 @@ But the situation is rather different when it comes to documentation. Too often, the translated documentation is not visible enough (not distributed -as a part of the program), only partial or, not up to date. This last +as a part of the program), only partial, or not up to date. This last situation is by far the worst possible one. Outdated translation can reveal worse than no translation at all to the users by describing old program behavior which are not in use anymore. @@ -154,7 +154,7 @@ =head3 nroff The good old manual pages' format, used by so much programs out there. The -po4a support is very welcome here since this format is somehow difficult to +po4a support is very welcome here since this format is somewhat difficult to use and not really friendly to the newbies. =head3 pod @@ -167,7 +167,7 @@ =head3 sgml -Even if somehow superseded by XML nowadays, this format is still used +Even if somewhat superseded by XML nowadays, this format is still used rather often for documents which are more than a few screens long. It allows you to make complete books. Updating the translation of so long documents can reveal to be a real nightmare. diff reveals often useless when the original @@ -395,7 +395,7 @@ faster than translating everything again. I was able to gettextize the existing French translation of the Perl documentation in one day, even if things B<did> went wrong. That was more than two megabytes of text, and a -new translation would have last months or more. +new translation would have lasted months or more. Let me explain the basis of the procedure first and I will come back on hints to achieve it when the process goes wrong. To ease comprehension, the @@ -435,7 +435,7 @@ Remove all extra parts of the translations, such as the section in which you give the translator name and thank every people who contributed to the -translation. Addendums, which are described in the next section, will allow +translation. Addenda, which are described in the next section, will allow you to re-add them afterward. =item - @@ -526,9 +526,9 @@ Because of the gettext approach, doing this becomes more difficult in po4a than it was when simply editing a new file along the original one. But it -remains possible, thanks to the so-called B<addendums>. +remains possible, thanks to the so-called B<addenda>. -It may help the comprehension to consider addendums as a sort of patches +It may help the comprehension to consider addenda as a sort of patches applied to the localized document after processing. They are rather different from the usual patches (they have only one line of context, which can embed perl regular expression, and they can only add new text without @@ -852,7 +852,7 @@ =head2 Addendum: How does it work? Well, that's pretty easy here. The translated document is not written -directly to disk, but kept in memory until all addendum are applied. The +directly to disk, but kept in memory until all the addenda are applied. The algorithms involved here are rather straightforward. We look for a line matching the position regexp, and insert the addendum before it if we're in mode=before. If not, we search for the next line matching the boundary and @@ -914,7 +914,7 @@ =item * This approach is the one used by professional translators. I agree, that -they have somehow different goals than open-source translators. The +they have somewhat different goals than open-source translators. The maintenance is for example often less critical to them since the content changes rarely. @@ -1136,7 +1136,7 @@ =item * -Addendum are ... strange at the first glance. +Addenda are... strange at the first glance. =item * Index: lib/Locale/Po4a/Chooser.pm =================================================================== RCS file: /cvsroot/po4a/po4a/lib/Locale/Po4a/Chooser.pm,v retrieving revision 1.21 diff -u -r1.21 Chooser.pm --- lib/Locale/Po4a/Chooser.pm 12 Feb 2005 14:02:20 -0000 1.21 +++ lib/Locale/Po4a/Chooser.pm 14 Feb 2005 13:31:44 -0000 @@ -7,7 +7,7 @@ # under the terms of GPL (see COPYING). # # This module converts POD to PO file, so that it becomes possible to -# translate POD formated documentation. See gettext documentation for +# translate POD formatted documentation. See gettext documentation for # more info about PO files. ############################################################################ @@ -53,13 +53,13 @@ sub list { warn wrap_msg(gettext("List of valid formats:\n". - " - kernelhelp: Help messages of each kernel compilation option.\n". -# " - html: HTML documents (EXPERIMENTAL).\n". - " - man: Good old manual page format.\n". - " - pod: Perl Online Documentation format.\n". - " - sgml: either debiandoc or docbook DTD.\n". - " - dia: uncompressed Dia diagrams.\n". - " - guide: Gentoo Linux's xml documentation format.")); + " - kernelhelp: help messages of each kernel compilation option.\n". +# " - html: HTML documents (EXPERIMENTAL).\n". + " - man: good old manual page format.\n". + " - pod: Perl Online Documentation format.\n". + " - sgml: either debiandoc or docbook DTD.\n". + " - dia: uncompressed Dia diagrams.\n". + " - guide: Gentoo Linux's xml documentation format.")."\n"; exit shift; } ############################################################################## Index: lib/Locale/Po4a/KernelHelp.pm =================================================================== RCS file: /cvsroot/po4a/po4a/lib/Locale/Po4a/KernelHelp.pm,v retrieving revision 1.10 diff -u -r1.10 KernelHelp.pm --- lib/Locale/Po4a/KernelHelp.pm 12 Feb 2005 14:02:20 -0000 1.10 +++ lib/Locale/Po4a/KernelHelp.pm 14 Feb 2005 13:31:44 -0000 @@ -7,7 +7,7 @@ # under the terms of GPL (see COPYING). # # This module converts POD to PO file, so that it becomes possible to -# translate POD formated documentation. See gettext documentation for +# translate POD formatted documentation. See gettext documentation for # more info about PO files. ############################################################################ Index: lib/Locale/Po4a/Man.pm =================================================================== RCS file: /cvsroot/po4a/po4a/lib/Locale/Po4a/Man.pm,v retrieving revision 1.75 diff -u -r1.75 Man.pm --- lib/Locale/Po4a/Man.pm 13 Feb 2005 23:06:45 -0000 1.75 +++ lib/Locale/Po4a/Man.pm 14 Feb 2005 13:31:44 -0000 @@ -398,7 +398,7 @@ sub pre_trans { my ($self,$str,$ref,$type)=@_; - # Preformating, so that translators don't see + # Preformatting, so that translators don't see # strange chars my $origstr=$str; print STDERR "pre_trans($str)=" @@ -455,7 +455,7 @@ print STDERR "post_trans($str)=" if ($debug{'postrans'}); - # Post formating, so that groff see the strange chars + # Post formatting, so that groff see the strange chars $str =~ s|\\-|-|sg; # in case the translator added some of them manually # change hyphens to minus signs # (this shouldn't be done for \s-<number> font size modifiers) @@ -685,7 +685,7 @@ # .Dd => Indicates that this is a mdoc page if ($macro eq 'Dd') { die wrap_mod("po4a::man", dgettext("po4a", - "This page seems to be a mdoc(7) formated one. This is not supported (yet).")); + "This page seems to be a mdoc(7) formatted one. This is not supported (yet).")); } unshift @args,$self; Index: lib/Locale/Po4a/Po.pm =================================================================== RCS file: /cvsroot/po4a/po4a/lib/Locale/Po4a/Po.pm,v retrieving revision 1.34 diff -u -r1.34 Po.pm --- lib/Locale/Po4a/Po.pm 12 Feb 2005 14:02:21 -0000 1.34 +++ lib/Locale/Po4a/Po.pm 14 Feb 2005 13:31:44 -0000 @@ -292,15 +292,15 @@ if ($poorig->count_entries() > $potrans->count_entries()) { warn wrap_mod("po4a gettextize", dgettext("po4a", - "Original have more strings that the translation (%d>%d). ". + "Original has more strings that the translation (%d>%d). ". "Please fix it by editing the translated version to add some dummy entry."), $poorig->count_entries() , $potrans->count_entries()); } elsif ($poorig->count_entries() < $potrans->count_entries()) { warn wrap_mod("po4a gettextize", dgettext("po4a", - "Original have less strings that the translation (%d<%d). ". + "Original has less strings than the translation (%d<%d). ". "Please fix it by removing the extra entry from the translated file. ". "You may need an addendum (cf po4a(7)) to reput the chunk in place after gettextization. ". - "A possible cause is that a text dupplicated in the original is not translated the same way each time. Remove one of the translations, and you're fine."), + "A possible cause is that a text duplicated in the original is not translated the same way each time. Remove one of the translations, and you're fine."), $poorig->count_entries(), $potrans->count_entries()); } @@ -773,7 +773,7 @@ =item wrap boolean indicating whether whitespaces can be mangled in cosmetic -reformatings. If true, the string is canonized before use. +reformattings. If true, the string is canonized before use. This information is written to the po file using the 'wrap' or 'no-wrap' flag. Index: lib/Locale/Po4a/Pod.pm =================================================================== RCS file: /cvsroot/po4a/po4a/lib/Locale/Po4a/Pod.pm,v retrieving revision 1.14 diff -u -r1.14 Pod.pm --- lib/Locale/Po4a/Pod.pm 7 Jan 2005 22:50:52 -0000 1.14 +++ lib/Locale/Po4a/Pod.pm 14 Feb 2005 13:31:45 -0000 @@ -7,7 +7,7 @@ # under the terms of GPL (see COPYING file). # # This module converts POD to PO file, so that it becomes possible to -# translate POD formated documentation. See gettext documentation for +# translate POD formatted documentation. See gettext documentation for # more info about PO files. ############################################################################ Index: lib/Locale/Po4a/Sgml.pm =================================================================== RCS file: /cvsroot/po4a/po4a/lib/Locale/Po4a/Sgml.pm,v retrieving revision 1.44 diff -u -r1.44 Sgml.pm --- lib/Locale/Po4a/Sgml.pm 12 Feb 2005 14:02:21 -0000 1.44 +++ lib/Locale/Po4a/Sgml.pm 14 Feb 2005 13:31:45 -0000 @@ -91,7 +91,7 @@ By default, msgids containing only one entity (like '&version;') are skipped for the translator comfort. Activating this option prevents this optimisation. It can be useful if the document contains a construction like -"<title>&Acute;</title>", even if I doubt such things to ever happen... +"<title>Á</title>", even if I doubt such things to ever happen... =back @@ -117,12 +117,12 @@ the document (not in a E<lt>pE<gt> tag or so). Everything works well with nsgmls's output redirected that way, but it will -prevent us to detect that the document is badly formated. +prevent us to detect that the document is badly formatted. =item * It does work only with the debiandoc and docbook dtd. Adding support for a -new dtd should be very easy. The mechanism is the same for all dtd, you just +new dtd should be very easy. The mechanism is the same for every dtd, you just have to give a list of the existing tags and some of their characteristics. I agree, this needs some more documentation, but it is still considered as @@ -131,7 +131,7 @@ =item * Warning, support for dtds is quite experimental. I did not read any -reference manual to find the definition of all tags. I did add tag +reference manual to find the definition of every tag. I did add tag definition to the module 'till it works for some documents I found on the net. If your document use more tags than mine, it won't work. But as I said above, fixing that should be quite easy. @@ -140,7 +140,7 @@ this document is quite big, and should use most of the docbook specificities. -For debiandoc, I tested some of the manual of the DDP, but not all yet. +For debiandoc, I tested some of the manuals from the DDP, but not all yet. =item * Index: lib/Locale/Po4a/TeX.pm =================================================================== RCS file: /cvsroot/po4a/po4a/lib/Locale/Po4a/TeX.pm,v retrieving revision 1.15 diff -u -r1.15 TeX.pm --- lib/Locale/Po4a/TeX.pm 13 Feb 2005 23:06:45 -0000 1.15 +++ lib/Locale/Po4a/TeX.pm 14 Feb 2005 13:31:45 -0000 @@ -164,7 +164,7 @@ sub pre_trans { my ($self,$str,$ref,$type)=@_; - # Preformating, so that translators don't see + # Preformatting, so that translators don't see # strange chars my $origstr=$str; print STDERR "pre_trans($str)=" Index: lib/Locale/Po4a/TransTractor.pm =================================================================== RCS file: /cvsroot/po4a/po4a/lib/Locale/Po4a/TransTractor.pm,v retrieving revision 1.57 diff -u -r1.57 TransTractor.pm --- lib/Locale/Po4a/TransTractor.pm 12 Feb 2005 14:02:21 -0000 1.57 +++ lib/Locale/Po4a/TransTractor.pm 14 Feb 2005 13:31:45 -0000 @@ -187,7 +187,7 @@ =item d. -Reads and applies all the addendum specified +Reads and applies all the addenda specified =item e. @@ -233,11 +233,11 @@ =item addendum (@) -list of filenames where we should read the addendum from. +list of filenames where we should read the addenda from. =item addendum_charset ($) -Charset for the addendum. +Charset for the addenda. =back @@ -489,13 +489,13 @@ =cut -=head2 Manipulating addendum +=head2 Manipulating addenda =over 4 =item addendum($) -Please refer to L<po4a(7)|po4a.7> for more information on what addendums are, +Please refer to L<po4a(7)|po4a.7> for more information on what addenda are, and how translators should write them. To apply an addendum to the translated document, simply pass its filename to this function and you are done ;)

19 years, 2 months

4
5
0 / 0

[Po4a-devel]Re: [Po4a-commits] po4a/lib/Locale/Po4a Man.pm,1.72,1.73

by Martin Quinson

Urgh. I seem to remember that we restricted this to macros to avoid rewriting verbatim sections. We had a man page containing >>>>>> Here is an example of how to use the line continuation with cpp: #define my_macro some text being too long to \ be on one line only, but it's \ not a problem since we can use \ line continuation like this Thanks for your attention. <<<<<< With you change, there is a risk that this verbatim block gets rewriten even if it really shouldn't. That being said, all this is based on remembrance. If it doesn't increase the number of pages for which we fail, I must be wrong. Thanks for your time, Mt. On Sun, Jan 09, 2005 at 06:04:10PM +0000, Nicolas FRAN??OIS wrote: > Update of /cvsroot/po4a/po4a/lib/Locale/Po4a > In directory haydn:/tmp/cvs-serv2440/lib/Locale/Po4a > > Modified Files: > Man.pm > Log Message: > input line continuations (\<RET>) are not reserved for macros > > > Index: Man.pm > =================================================================== > RCS file: /cvsroot/po4a/po4a/lib/Locale/Po4a/Man.pm,v > retrieving revision 1.72 > retrieving revision 1.73 > diff -u -d -r1.72 -r1.73 > --- Man.pm 7 Jan 2005 22:50:52 -0000 1.72 > +++ Man.pm 9 Jan 2005 18:04:07 -0000 1.73 > @@ -290,7 +290,7 @@ > $line =~ s/\\\././g; > > chomp $line; > - while ($line =~ /^\..*\\$/ || $line =~ /^(\.[BI])\s*$/) { > + while ($line =~ /^.*\\$/ || $line =~ /^(\.[BI])\s*$/) { > my ($l2,$r2)=$self->SUPER::shiftline(); > chomp($l2); > if ($line =~ /^(\.[BI])\s*$/) { > > > _______________________________________________ > Po4a-commits mailing list > Po4a-commits(a)lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/po4a-commits

19 years, 2 months

2
2
0 / 0

[Po4a-devel]Re: [Po4a-commits] po4a/lib/Locale/Po4a Man.pm,1.76,1.77 Xml.pm,1.24,1.25

by Nicolas François

On Tue, Feb 15, 2005 at 03:47:37PM +0000, Jordi Vilalta wrote: > Modified Files: > Man.pm Xml.pm > Log Message: > Change "warn + exit 0" for "die" (exit 0 means "all ok" in the shell) Hello Jordi, Regarding the Man module, it was used in the check script to make a difference between errors and other warning "under control". As dying is probably more user friendly (no translation is performed), I will use another error code and change the check script. I'm thinking about using: eval(254) || die "..." -- Nekral

19 years, 2 months

1
0
0 / 0

[Po4a-devel]From Debian BTS: Bug#291831: po4a: some errors with with d-i manual's xml files

by Martin Quinson

Hello, I just received this from the Debian BTS. Jordi, it looks like your first bug report ;) I'd say that something is going wrong with the comment containing tags in the Xml module. Could you please look at it (or tell us what we can do to help you -- don't want to step on your feet) ? I would also rewrite the code around 471 to: unless (defined($name) && $name eq $tag) { die "po4a::xml: ". sprintf(dgettext("po4a","Unexpected closing tag </%s> found in %s...."; } it would avoid the use of uninitialized value the bug report speaks about. Thanks for your time, Mt. ----- Forwarded message from "Carlos Z.F. Liu" <carlosliu(a)users.sourceforge.net> ----- Subject: Bug#291831: po4a: some errors with with d-i manual's xmlw files X-Debian-PR-Package: po4a From: "Carlos Z.F. Liu" <carlosliu(a)users.sourceforge.net> To: Debian Bug Tracking System <submit(a)bugs.debian.org> X-Mailer: reportbug 3.6 Date: Mon, 24 Jan 2005 04:06:24 +1300 Package: po4a Version: 0.19-1 Severity: normal Here are 2 problems with xml files in d-i manual (both sarge and trunk branch in SVN). 1. Can't generate .po file from en/boot-installer/i386.xml, po4a reported following msg: Use of uninitialized value in string ne at /usr/share/perl5/Locale/Po4a/Xml.pm line 471. po4a::xml: Unexpected closing tag </para> found in en/boot-installer/i386.xml:231. The main document may be wrong. After a careful recheck, I think the file is 100% valid, and I can generate HTML from it without any problem. The tricky thing is that many </para><para> pairs were commented by  in the document. Perhaps, po4a didn't handle then correctly. (I guess ;-) 2. Another two files, en/using-d-i/modules/baseconfig.xml and en/using-d-i/modules/os-prober.xml. po4a can produce pot file from xml, but it will ignore the last paragraph after a  comment. Then, after I translated po files and convert them back to xml, those generated xml files are invalid. Please look at attachments to know what I mean. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.9 Locale: LANG=en_NZ.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) Versions of packages po4a depends on: ii gettext 0.14.1-8 GNU Internationalization utilities ii liblocale-gettext-perl 1.01-17 Using libc functions for internati ii libsgmls-perl 1.03ii-31 Perl modules for processing SGML p ii perl [perl5] 5.8.4-5 Larry Wall's Practical Extraction ii perl-modules 5.8.4-5 Core Perl modules ii sp 1.3.4-1.2.1-43 James Clark's SGML parsing tools -- no debconf information    <sect2 arch="i386"><title>Booting from a CD-ROM</title> &boot-installer-intro-cd.xml;   </sect2>  <sect2 arch="i386" id="boot-initrd"> <title>Booting from linux using <command>LILO</command> or <command>GRUB</command></title> <para> To boot the installer from hard disk, you must first download and place the needed files as described in <xref linkend="boot-drive-files"/>. </para> <para> If you intend to use the hard drive only for booting and then download everything over the network, you should download the <filename>netboot/debian-installer/i386/initrd.gz</filename> file and its corresponding kernel. This will allow you to repartition the hard disk from which you boot the installer, although you should do so with care. </para> <para> Alternatively, if you intend to keep an existing partition on the hard drive unchanged during the install, you can download the <filename>hd-media/initrd.gz</filename> file and its kernel, as well as copy a CD iso to the drive (make sure the file is named ending in ".iso". The installer can then boot from the drive and install from the CD image, without needing the network. </para> <para> For <command>LILO</command>, you will need to configure two essential things in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to load the <filename>initrd.gz</filename> installer at boot time; </para></listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is a <filename>/etc/lilo.conf</filename> example: </para><para> <informalexample><screen> image=/boot/newinstall/vmlinuz label=newinstall initrd=/boot/newinstall/initrd.gz root=/dev/ram0 append="devfs=mount,dall ramdisk_size=17000" </screen></informalexample> For more details, refer to the <citerefentry><refentrytitle>initrd</refentrytitle> <manvolnum>4</manvolnum></citerefentry> and <citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and reboot. </para><para> The procedure for <command>GRUB</command> is quite similar. Locate your <filename>menu.lst</filename> in the <filename>/boot/grub/</filename> directory (sometimes in the <filename>/boot/boot/grub/</filename>), add the following lines: <informalexample><screen> title New Install kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 devfs=mount,dall ramdisk_size=17000 initrd (hd0,0)/boot/newinstall/initrd.gz </screen></informalexample> and reboot. Note that the value of the <userinput>ramdisksize</userinput> may need to be adjusted for the size of the initrd image. >From now on, there should be no difference between <command>GRUB</command> or <command>LILO</command>. </para> </sect2> <sect2 arch="i386" id="usb-boot"> <title>Booting from USB memory stick</title> <para> Lets assume you have prepared everything from <xref linkend="boot-dev-select"/> and <xref linkend="boot-usb-files"/>. Now just plug your USB stick into some free USB connector and reboot the computer. The system should boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;. </para><para> In case your computer doesn't support booting from USB memory devices, you can still use a single floppy to do the initial boot and then switch to USB. Boot your system as described in <xref linkend="floppy-boot"/>; the kernel on the boot floppy should detect your USB stick automatically. When it asks for the root floppy, simply press &enterkey;. You should see &d-i; starting. </para> </sect2> <sect2 arch="i386" id="floppy-boot"> <title>Booting from Floppies</title> <para> You will have already downloaded the floppy images you needed and created floppies from the images in <xref linkend="create-floppy"/>.  </para><para> To boot from the installer boot floppy, place it in the primary floppy drive, shut down the system as you normally would, then turn it back on. </para><para> For installing from a LS-120 drive (ATAPI version) with a set of floppies, you need to specify the virtual location for the floppy device. This is done with the <emphasis>root=</emphasis> boot argument, giving the device that the ide-floppy driver maps the device to. For example, if your LS-120 drive is connected as the first IDE device (master) on the second cable, you enter <userinput>linux root=/dev/hdc</userinput> at the boot prompt. Installation from LS-120 is only supported by 2.4 and later kernels. </para><para> Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> does not properly reset the machine, so a ``hard'' reboot is recommended. If you are installing from an existing operating system (e.g., from a DOS box) you don't have a choice. Otherwise, please do a hard reboot when booting. </para><para> The floppy disk will be accessed, and you should then see a screen that introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt. </para><para> Once you press &enterkey;, you should see the message <computeroutput>Loading...</computeroutput>, followed by <computeroutput>Uncompressing Linux...</computeroutput>, and then a screenfull or so of information about the hardware in your system. More information on this phase of the boot process can be found below in <xref linkend="kernel-msgs"/>. </para><para> After booting from the boot floppy, the root floppy is requested. Insert the root floppy and press &enterkey;, and the contents are loaded into memory. The installer program <command>debian-installer</command> is automatically launched. </para> </sect2> <sect2 arch="i386" id="boot-tftp"><title>Booting with TFTP</title> &boot-installer-intro-net.xml; <para> There are various ways to do a TFTP boot on i386. </para> <sect3><title>NIC or Motherboard that support PXE</title> <para> It could be that your Network Interface Card or Motherboard provides PXE boot functionality. This is a <trademark class="trade">Intel</trademark> re-implemention of TFTP boot. If so you may be able to configure your BIOS to boot from the network. </para> </sect3> <sect3><title>NIC with network bootROM</title> <para> It could be that your Network Interface Card provides TFTP boot functionality. </para><para condition="FIXME"> Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. Please refer to this document. </para> </sect3> <sect3><title>Etherboot</title> <para> The <ulink url="http://www.etherboot.org">etherboot project</ulink> provides bootdiskettes and even bootroms that do a TFTPboot. </para> </sect3> </sect2> <sect2 arch="i386"><title>i386 Boot Parameters</title> <para> When the installer boots, you will be presented with the boot prompt, <prompt>boot:</prompt>. You can do two things at the <prompt>boot:</prompt> prompt. You can press the function keys <keycap>F1</keycap> through <keycap>F10</keycap> to view a few pages of helpful information, or you can press <keycap>Enter</keycap> to boot the system. </para><para> Information on boot parameters which might be useful can be found by pressing <keycap>F3</keycap> through <keycap>F7</keycap>. If you add any parameters to the boot command line, be sure to type the boot method (the default is <userinput>linux</userinput>) and a space before the first parameter (e.g., <userinput>linux floppy=thinkpad</userinput>). If you simply press &enterkey;, that's the same as typing <userinput>linux</userinput> without any special parameters. </para><para> Some systems have floppies with ``inverted DCLs''. If you receive errors reading from the floppy, even when you know the floppy is good, try the parameter <userinput>floppy=thinkpad</userinput>. </para><para> On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk drivers), the IDE drive may not be properly recognized. Again, try it first without the parameters and see if the IDE drive is recognized properly. If not, determine your drive geometry (cylinders, heads, and sectors), and use the parameter <userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>. </para><para> If you have a very old machine, and the kernel hangs after saying <computeroutput>Checking 'hlt' instruction...</computeroutput>, then you should try the <userinput>no-hlt</userinput> boot argument, which disables this test. </para><para> If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>debian-installer/framebuffer=false</userinput> or <userinput>video=vga16:off</userinput> to disable the framebuffer console. Only the English language will be available during the installation due to limited console features. See <xref linkend="boot-parms"/> for details. </para> </sect2> <sect2 arch="i386"> <title>System freeze during the PCMCIA configuration phase</title> <para> Some laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems. </para><para> Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url="http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer. </para> </sect2> <sect2 arch="i386"> <title>System freeze while loading the USB modules</title> <para> The kernel normally tries to install USB modules and the USB keyboard driver in order to support some non-standard USB keyboards. However, there are some broken USB systems where the driver hangs on loading. A possible workaround may be disabling the USB controller in your mainboard BIOS setup. Another option is passing the <userinput>debian-installer/probe/usb=false</userinput> parameter at the boot prompt, which will prevent the modules from being loaded. </para> </sect2>   <sect3 id="baseconfig"> <title>Running <command>base-config</command> From Within &d-i;</title> <para> It is possible to configure the base system within the first stage installer (before rebooting from the hard drive), by running <command>base-config</command> in a <firstterm>chroot</firstterm> environment. This is mainly useful for testing the installer and a vast majority of people should avoid it.  </para> </sect3> # Debian GNU/Linux Installation Guide # Original translator szjungle, 2004. # msgid "" msgstr "" "Project-Id-Version: d-i-manaul\n" "POT-Creation-Date: 2005-01-21 4:19+1300\n" "PO-Revision-Date: 2005-01-08 18:51+0800\n" "Last-Translator: Jungle Ji <jungle(a)soforge.com>\n" "Language-Team: debian-chinese-gb <debian-chinese-gb(a)lists.debian.org>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" # type: Content of: outside any tag (error?) #: en/using-d-i/modules/baseconfig.xml:1 #, no-wrap msgid "\n" msgstr "\n" # type: Content of: outside any tag (error?) #: en/using-d-i/modules/baseconfig.xml:2 #, no-wrap msgid "" "\n" "\n" " " msgstr "" "\n" "\n" " " # type: Content of: <sect3> #: en/using-d-i/modules/baseconfig.xml:4 #, no-wrap msgid "" "\n" " " msgstr "" "\n" " " # type: Content of: <sect3><title> #: en/using-d-i/modules/baseconfig.xml:5 #, no-wrap msgid "Running " msgstr "??? &d-i; ???????????? " # type: Content of: <sect3><para><command> #: en/using-d-i/modules/baseconfig.xml:5 #: en/using-d-i/modules/baseconfig.xml:11 #, no-wrap msgid "base-config" msgstr "base-config" # type: Content of: <sect3><title> #: en/using-d-i/modules/baseconfig.xml:5 #, no-wrap msgid " From Within &d-i;" msgstr " " # type: Content of: <sect3> #: en/using-d-i/modules/baseconfig.xml:5 #, no-wrap msgid "" "\n" "\n" msgstr "" "\n" "\n" # type: Content of: <sect3><para> #: en/using-d-i/modules/baseconfig.xml:7 #, no-wrap msgid "" "\n" "\n" "It is possible to configure the base system within the first stage\n" "installer (before rebooting from the hard drive), by running\n" msgstr "" "\n" "?????????????????????????????????????????????????????????????????? (????????????????????????)???\n" "??????\n" # type: Content of: <sect3><para> #: en/using-d-i/modules/baseconfig.xml:11 #, no-wrap msgid " in a " msgstr " ??? " # type: Content of: <sect3><para><firstterm> #: en/using-d-i/modules/baseconfig.xml:11 #, no-wrap msgid "chroot" msgstr "chroot" # type: Content of: <sect3><para> #: en/using-d-i/modules/baseconfig.xml:11 #, fuzzy, no-wrap msgid "" "\n" "environment. This is mainly useful for testing the installer and a\n" "vast majority of people should avoid it.\n" msgstr "" "\n" "???????????????????????????????????????????????????\n" "??????????????????????????????????????????\n"   <sect3 id="baseconfig"> <title>??? &d-i; ???????????? <command>base-config</command> </title> <para> ?????????????????????????????????????????????????????????????????? (????????????????????????)??? ?????? <command>base-config</command> ??? <firstterm>chroot</firstterm> environment. This is mainly useful for testing the installer and a vast majority of people should avoid it.  </para> Feel free to prove me I'm wrong --> -->   <sect3 id="os-prober"> <title>Detecting other operating systems</title> <para> Before a boot loader is installed, the installer will attempt to probe for other operating systems which are installed on the machine. If it finds a supported operating system, you will be informed of this during the boot loader installation step, and the computer will be configured to boot this other operating system in addition to Debian. </para><para> Note that multiple operating systems booting on a single machine is still something of a black art. The automatic support for detecting and setting up boot loaders to boot other operating systems varies by architecture and even by subarchitecture. If it does not work you should consult your boot manager's documentation for more information.  </para> <note><para> The installer may fail to detect other operating systems if the partitions on which they reside are mounted when the detection takes place. This may occur if you select a mountpoint (e.g. /win) for a partition containing another operating system in <command>partman</command>, or if you have mounted partitions manually from a console. </para></note> </sect3>   <sect3 id="os-prober"> <title>???????????????????????????</title> <para> ??????????????????????????????????????????????????????????????????????????????????????????????????????????????? ????????????????????????????????????????????????????????????????????????????????????????????? ??? Debian ?????????????????????????????????????????????????????????????????? </para><para> ????????????????????????????????????????????????????????????????????? ??????????????????????????????????????????????????????????????????????????????????????????????????????????????? ????????????????????????????????????????????????????????????????????????????????????  </para> <note><para> The installer may fail to detect other operating systems if the partitions on which they reside are mounted when the detection takes place. This may occur if you select a mountpoint (e.g. /win) for a partition containing another operating system in <command>partman</command>, or if you have mounted partitions manually from a console. </para></note> TODO: Maybe include some arch-dependent tables with supported OS'es here --> --> # SOME DESCRIPTIVE TITLE # Original translator szjungle, 2004. # msgid "" msgstr "" "Project-Id-Version: d-i-manual\n" "POT-Creation-Date: 2005-01-21 5:07+1300\n" "PO-Revision-Date: 2004-12-09 11:52+0800\n" "Last-Translator: Jungle Ji <jungle(a)soforge.com>\n" "Language-Team: debian-chinese-gb <debian-chinese-gb(a)lists.debian.org>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" # type: Content of: outside any tag (error?) #: en/using-d-i/modules/os-prober.xml:1 #, no-wrap msgid "\n" msgstr "\n" # type: Content of: outside any tag (error?) #: en/using-d-i/modules/os-prober.xml:2 #, no-wrap msgid "" "\n" "\n" " " msgstr "" "\n" "\n" " " # type: Content of: <sect3> #: en/using-d-i/modules/os-prober.xml:4 #, no-wrap msgid "" "\n" " " msgstr "" "\n" " " # type: Content of: <sect3><title> #: en/using-d-i/modules/os-prober.xml:5 #, no-wrap msgid "Detecting other operating systems" msgstr "???????????????????????????" # type: Content of: <sect3> #: en/using-d-i/modules/os-prober.xml:5 #, no-wrap msgid "" "\n" "\n" msgstr "" "\n" "\n" # type: Content of: <sect3><para> #: en/using-d-i/modules/os-prober.xml:7 #, no-wrap msgid "" "\n" "\n" "Before a boot loader is installed, the installer will attempt to probe for\n" "other operating systems which are installed on the machine. If it finds a\n" "supported operating system, you will be informed of this during the boot\n" "loader installation step, and the computer will be configured to boot this\n" "other operating system in addition to Debian.\n" "\n" msgstr "" "\n" "???????????????????????????????????????????????????????????????????????????????????????????????????????????????\n" "?????????????????????????????????????????????????????????????????????????????????????????????\n" "??? Debian ??????????????????????????????????????????????????????????????????\n" # type: Content of: <sect3><para> #: en/using-d-i/modules/os-prober.xml:15 #, no-wrap msgid "" "\n" "\n" "Note that multiple operating systems booting on a single machine is still\n" "something of a black art. The automatic support for detecting and setting\n" "up boot loaders to boot other operating systems varies by architecture and\n" "even by subarchitecture. If it does not work you should consult your\n" "boot manager's documentation for more information.\n" "\n" msgstr "" "\n" "\n" "?????????????????????????????????????????????????????????????????????\n" "???????????????????????????????????????????????????????????????????????????????????????????????????????????????\n" "????????????????????????????????????????????????????????????????????????????????????\n" "\n" # type: Content of: <sect3><note><para> #~ msgid "" #~ "\n" #~ "\n" #~ "The installer may fail to detect other operating systems if the " #~ "partitions on\n" #~ "which they reside are mounted when the detection takes place. This may " #~ "occur if\n" #~ "you select a mountpoint (e.g. /win) for a partition containing another " #~ "operating\n" #~ "system in " #~ msgstr "" #~ "\n" #~ "????????????????????????????????????????????????????????????????????????????????????????????????\n" #~ "??????????????????????????? " # type: Content of: <sect3><note><para><command> #~ msgid "partman" #~ msgstr "partman" # type: Content of: <sect3><note><para> #~ msgid "" #~ ", or if you have mounted partitions manually\n" #~ "from a console.\n" #~ "\n" #~ msgstr "" #~ " ??????????????????(??? /win)???????????????????????????????????????????????????????????????????????????\n" ----- End forwarded message -----

19 years, 2 months

2
3
0 / 0

[Po4a-devel]Enhancing po4a config files

by Jordi Vilalta

Hi, some days ago I sent a request for enhancement to the alioth tracker (http://alioth.debian.org/tracker/index.php?func=detail&aid=301133&group_i...), but today I had the time to do it myself. I attach the related patch. It's just a proposal, but I think this simplifies the po4a config files, and makes them a lot more scalable. Waiting to hear your opinions :) Regards, Jordi Vilalta

19 years, 2 months

2
2
0 / 0

[Po4a-devel]Re: [Po4a-commits] po4a/lib/Locale/Po4a TeX.pm,1.5,1.6

by Martin Quinson

Waa, that's impressive! What are your plan for the future? Did you reach a releasable state, or do you what to improve furter your code? We're on your order on this one ;) Could you please update the changelog? As usual, I'm really impressed here. Thanks for your time, Mt. On Sat, Jan 08, 2005 at 10:44:30AM +0000, Nicolas FRAN??OIS wrote: > Update of /cvsroot/po4a/po4a/lib/Locale/Po4a > In directory haydn:/tmp/cvs-serv9174/lib/Locale/Po4a > > Modified Files: > TeX.pm > Log Message: > Some cleanups and comments. > New functionnalities: > * Better handling of the spaces surrounding commands. They are now kept as close to the original as possible. > * Start using "% po4a: " line for parser personalisation. > * It is now possible to build a derivated parser. > * Handle file inclusion (based on Transtractor's read).

19 years, 2 months

2
2
0 / 0

[Po4a-devel][asgeirf@redhat.com: [Translation-i18n] ANNOUNCE: XLIFF Tools project]

by Martin Quinson

FYI ----- Forwarded message from Asgeir Frimannsson <asgeirf(a)redhat.com> ----- From: Asgeir Frimannsson <asgeirf(a)redhat.com> User-Agent: KMail/1.7.1 To: xdg(a)freedesktop.org, fedora-trans-list(a)redhat.com, kde-i18n-doc(a)kde.org, gnome-i18n(a)gnome.org, translation-i18n(a)lists.sourceforge.net, kbabel(a)kde.org, gtranslator-list(a)gnome.org, loc-dev(a)lists.localisationdev.org, translate-devel(a)lists.sourceforge.net Subject: [Translation-i18n] ANNOUNCE: XLIFF Tools project Date: Tue, 1 Feb 2005 07:40:59 +1000 Announcing Freedesktop.org's XLIFF Tools Project. ================================================= XLIFF (XML Localisation Interchange File Format) [1] is an open XML standard for exchange of localisable data. XLIFF has many features that other localisation formats (such as Gettext PO) is lacking, including support for binary data formats, workflow support and inclusion of translation suggestions from e.g. TMX [2] based translation memories. The XLIFF Tools project aims to implement support for XLIFF in open source localisation workflows. Specifically, this project aims to: - Develop XLIFF filters for common open source file formats (e.g. Gettext PO, Docbook, .desktop files, Glade/Qt UI dialogs) - Implement and improve XLIFF support in open source localisation tools - Implement tools to support XLIFF-based localisation in open source development processes. The first phase of this project will be focusing on the Gettext PO file format. As a first step, guidelines will be defined on how to represent PO in XLIFF. This guide will be submitted to the XLIFF Technical Committee for review and possible inclusion as the XLIFF 1.1 PO File Representation Guide [3]. The first set of tools being developed are filters to convert between PO and XLIFF, based on the XLIFF PO representation guide: - po2xliff: Convert a PO file to XLIFF - xliff2po: Convert a XLIFF file back to PO - xliffinit: Initialize a XLIFF file for a specific locale - xliffmerge: Merge translated XLIFF file with newly created XLIFF template (similar to msgmerge for PO) For more information and to get involved, visit the project web-site [http://xliff-tools.freedesktop.org] and subscribe to the mailing list [http://lists.freedesktop.org/mailman/listinfo/xliff-tools]. References: [1] http://www.xliff.org/ [2] http://www.lisa.org/tmx/ [3] http://lists.oasis-open.org/archives/xliff/200410/msg00009.html cheers, Asgeir Frimannsson <asgeirf(a)redhat.com> ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Translation-i18n mailing list Translation-i18n(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translation-i18n ----- End forwarded message -----

19 years, 2 months

1
0
0 / 0

[Po4a-devel]Error while commiting

by Jordi Vilalta

Hi, yesterday I sent the following mail, but it got a delivery failure. It seems that Alioth's mail server is somewhat unstable. ---------- Forwarded message ---------- Date: Wed, 2 Feb 2005 13:21:22 +0100 (CET) From: Jordi Vilalta <jvprat(a)wanadoo.es> To: po4a-devel(a)lists.alioth.debian.org Subject: Error while commiting Hi, today I've commited a change in the Xml module changing the default behaviour to strip the extracted strings (be careful, this can fuzzy all your strings, use -o nostrip to avoid it), and at the end of the commit I got this error message: Traceback (most recent call last): File "/cvsroot/po4a/CVSROOT/syncmail", line 437, in ? main() File "/cvsroot/po4a/CVSROOT/syncmail", line 430, in main contextlines, fromhost, replyto) File "/cvsroot/po4a/CVSROOT/syncmail", line 222, in blast_mail conn.connect(MAILHOST, MAILPORT) File "/usr/lib/python2.1/smtplib.py", line 222, in connect self.sock.connect((host, port)) socket.error: (111, 'Connection refused') Traceback (most recent call last): File "/cvsroot/po4a/CVSROOT/syncmail", line 437, in ? main() File "/cvsroot/po4a/CVSROOT/syncmail", line 430, in main contextlines, fromhost, replyto) File "/cvsroot/po4a/CVSROOT/syncmail", line 222, in blast_mail conn.connect(MAILHOST, MAILPORT) File "/usr/lib/python2.1/smtplib.py", line 222, in connect self.sock.connect((host, port)) socket.error: (111, 'Connection refused') The change has been commited, but it seems it couldn't send the commit mail. I don't know where the error comes from (maybe the alioth mail server was down for a while), but it can be annoying to work without knowing what others have done. If you get the same error, I recommend sending a manual mail to the list to inform what you've done (thanks in advance). I hope it gets solved soon. Regards, Jordi Vilalta

19 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Devel February 2005