Re: [sane-devel] Code freeze and release preparations for 1.0.28 (was Re: [ITR] Intent To Release: sane-backends-1.0.28)
Hi Rolf, Rolf Bensch writes: > Hi all again, > > Today I merged my German translations into master branch. Everybody > still is invited to review my translation until July 31. Also after the > new release will be out, of course. Thanks. > Please consider that new localization files may break existing scanimage > scripts. For scripting, do yourself a favour and set LANG=C (and unset LANGUAGE) at the beginning. If you (or other people using your scripts!) have any odd-ball LC_* variables set, use LC_ALL=C. Lots more portable, lots less chance of breakage. # Only when we change strings in code, which we don't in 1.0.28. We # only add a few. Hope this helps. -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Code freeze and release preparations for 1.0.28 (was Re: [ITR] Intent To Release: sane-backends-1.0.28)
Hi all again, Today I merged my German translations into master branch. Everybody still is invited to review my translation until July 31. Also after the new release will be out, of course. Please consider that new localization files may break existing scanimage scripts. Hope this helps. Cheers, Rolf Am 27.07.19 um 13:14 schrieb Rolf Bensch: > Hi all, > > I'm just busy working on the German translations. Hope I'll be ready > until release date. > > I just pushed a new branch with the 1st bunch of my work. Everybody is > invited for helping and reviewing. > > Cheers, > Rolf > > Am 24.07.19 um 14:35 schrieb Olaf Meeuwissen: >> Hi again all, >> >> Still following the release schedule on our [1.0.28 milestone][1], our >> master branch is now (2019-07-24 12:00UTC) in code freeze. Please do >> *not* push/merge to master unless it fixes >> >> - hardware destroying bugs (no reports at present), >> - compile failures (our CI is clean so we're looking good), >> - completely unusable backends, or >> - documentation >> >> In case of doubt, ping the list or [submit an issue][2]. >> >> [1]: https://gitlab.com/sane-project/backends/-/milestones/2 >> [2]: https://gitlab.com/sane-project/backends/issues >> >> @povilas> Thanks for fixing that genesys backend calibration file bug. >> See https://gitlab.com/sane-project/backends/issues/97 >> >> I've been tinkering with our project's [Releases page][3] on GitLab.com. >> When we moved, that page didn't exist yet and I put our "releases" so >> far on the repository's [Tags][4] page for lack of a better alternative. >> GitLab.com seeded the former from the latter but that created quite a >> mess in terms of version ordering for the Releases. That has now been >> sorted out. I still want to convert the notes to Markdown, though. >> When we release 1.0.28, the Releases page will be updated automatically, >> courtesy of our CI! >> >> [3]: https://gitlab.com/sane-project/backends/-/releases >> [4]: https://gitlab.com/sane-project/backends/-/tags >> >> We now have a week to update translations as well. I just pushed a sync >> of all the po/*.po files against the latest source. I thought of Cc:ing >> the Last-Translator entries in those files, but most of those addresses >> are so old I figured I'd better not. For the recent ones, coverage is >> pretty good already. Here are some stats, sorted by percentage of the >> strings that are translated. >> >> Translated Fuzzy Untranslated >> 100.00% 0.00% 0.00%: uk.po >>99.33% 0.42% 0.25%: he.po >>99.33% 0.42% 0.25%: c...@valencia.po >>99.33% 0.42% 0.25%: ca.po >>98.24% 0.75% 1.00%: nl.po >>84.95% 6.27% 8.78%: sv.po >>75.33% 8.70% 15.97%: de.po >>74.75% 8.86% 16.39%: fr.po >>74.67% 8.95% 16.39%: pl.po >>72.07% 10.12% 17.81%: gl.po >>72.07% 10.12% 17.81%: es.po >>68.65% 11.79% 19.57%: en_GB.po >>66.47% 12.79% 20.74%: eo.po >>65.55% 13.55% 20.90%: it.po >>56.77% 16.64% 26.59%: da.po >>56.35% 9.78% 33.86%: ja.po >>52.34% 17.89% 29.77%: fi.po >>52.17% 18.14% 29.68%: bg.po >>49.41% 16.64% 33.95%: ru.po >>49.25% 19.15% 31.61%: cs.po >>21.82% 13.96% 64.21%: pt.po >>16.89% 16.14% 66.97%: nb.po >>15.64% 11.12% 73.24%: hu.po >> >> I will fix up nl.po myself but the rest is for interested parties (I may >> take a look at ja.po and en_GB.po, though). If you intend to work on >> any of these files, please let the list know so we can coordinate >> things. >> >> Hope this helps, >> -- >> Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 >> GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 >> Support Free Softwarehttps://my.fsf.org/donate >> Join the Free Software Foundation https://my.fsf.org/join >> >> -- sane-devel mailing list: sane-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Code freeze and release preparations for 1.0.28 (was Re: [ITR] Intent To Release: sane-backends-1.0.28)
Hi Olaf, It would be nice to see some tags in git, as reminder for the recent stage in our release process. This is just an idea for the discussion how to organize such things in future. Cheers, Rolf Am 24.07.19 um 14:35 schrieb Olaf Meeuwissen: > Hi again all, > > Still following the release schedule on our [1.0.28 milestone][1], our > master branch is now (2019-07-24 12:00UTC) in code freeze. Please do > *not* push/merge to master unless it fixes > > - hardware destroying bugs (no reports at present), > - compile failures (our CI is clean so we're looking good), > - completely unusable backends, or > - documentation > > In case of doubt, ping the list or [submit an issue][2]. > > [1]: https://gitlab.com/sane-project/backends/-/milestones/2 > [2]: https://gitlab.com/sane-project/backends/issues > > @povilas> Thanks for fixing that genesys backend calibration file bug. > See https://gitlab.com/sane-project/backends/issues/97 > > I've been tinkering with our project's [Releases page][3] on GitLab.com. > When we moved, that page didn't exist yet and I put our "releases" so > far on the repository's [Tags][4] page for lack of a better alternative. > GitLab.com seeded the former from the latter but that created quite a > mess in terms of version ordering for the Releases. That has now been > sorted out. I still want to convert the notes to Markdown, though. > When we release 1.0.28, the Releases page will be updated automatically, > courtesy of our CI! > > [3]: https://gitlab.com/sane-project/backends/-/releases > [4]: https://gitlab.com/sane-project/backends/-/tags > > We now have a week to update translations as well. I just pushed a sync > of all the po/*.po files against the latest source. I thought of Cc:ing > the Last-Translator entries in those files, but most of those addresses > are so old I figured I'd better not. For the recent ones, coverage is > pretty good already. Here are some stats, sorted by percentage of the > strings that are translated. > > Translated Fuzzy Untranslated > 100.00% 0.00% 0.00%: uk.po >99.33% 0.42% 0.25%: he.po >99.33% 0.42% 0.25%: c...@valencia.po >99.33% 0.42% 0.25%: ca.po >98.24% 0.75% 1.00%: nl.po >84.95% 6.27% 8.78%: sv.po >75.33% 8.70% 15.97%: de.po >74.75% 8.86% 16.39%: fr.po >74.67% 8.95% 16.39%: pl.po >72.07% 10.12% 17.81%: gl.po >72.07% 10.12% 17.81%: es.po >68.65% 11.79% 19.57%: en_GB.po >66.47% 12.79% 20.74%: eo.po >65.55% 13.55% 20.90%: it.po >56.77% 16.64% 26.59%: da.po >56.35% 9.78% 33.86%: ja.po >52.34% 17.89% 29.77%: fi.po >52.17% 18.14% 29.68%: bg.po >49.41% 16.64% 33.95%: ru.po >49.25% 19.15% 31.61%: cs.po >21.82% 13.96% 64.21%: pt.po >16.89% 16.14% 66.97%: nb.po >15.64% 11.12% 73.24%: hu.po > > I will fix up nl.po myself but the rest is for interested parties (I may > take a look at ja.po and en_GB.po, though). If you intend to work on > any of these files, please let the list know so we can coordinate > things. > > Hope this helps, > -- > Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 > GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 > Support Free Softwarehttps://my.fsf.org/donate > Join the Free Software Foundation https://my.fsf.org/join > > -- sane-devel mailing list: sane-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Code freeze and release preparations for 1.0.28 (was Re: [ITR] Intent To Release: sane-backends-1.0.28)
Hi Ralph, Ralph Little writes: > Hi Olaf,I have create a branch and submitted a merge request for the > en_GB translation. I notice that there is a "pipeline" error related > to trailing white space generated from the GitLab machinery. I'm not > sure what that signifies. I did another diff between the new and old > file, and there doesn't appear to be a difference at the bottom of the > file. There is a trailing space at the end of the "# Need->Needs? " comment on line 3152. The "trailing" refers to end of line as well as end of file. You can use the `tools/style-check.sh --fix po/en_GB.po` to fix this but I recommend using [EditorConfig][1] where possible to take care of this for you every time you save a file. Unfortunately, poedit does not seem to be supported :-/ [1]: https://editorconfig.org/ > I am new to the gitlab workflow so please feel free to let me know if > I make a mistake! No problem. BTW, you should update the Last-Translator field too. Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Code freeze and release preparations for 1.0.28 (was Re: [ITR] Intent To Release: sane-backends-1.0.28)
Hi Olaf,I have create a branch and submitted a merge request for the en_GB translation. I notice that there is a "pipeline" error related to trailing white space generated from the GitLab machinery. I'm not sure what that signifies. I did another diff between the new and old file, and there doesn't appear to be a difference at the bottom of the file. I am new to the gitlab workflow so please feel free to let me know if I make a mistake! Cheers,Ralph -- sane-devel mailing list: sane-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Code freeze and release preparations for 1.0.28 (was Re: [ITR] Intent To Release: sane-backends-1.0.28)
Hi all, Olaf Meeuwissen writes: > [...] > We now have a week to update translations as well. [...] Here are > some stats, sorted by percentage of the strings that are translated. > Translated Fuzzy Untranslated >98.24% 0.75% 1.00%: nl.po 99.67% 0.00% 0.33%: nl.po > I will fix up nl.po myself but the rest is for interested parties (I may > take a look at ja.po and en_GB.po, though). If you intend to work on > any of these files, please let the list know so we can coordinate > things. I just realized how much I don't know computer related terminology in my own mother tongue ... Worse, I found myself coming up with alternative ways to say the same thing in English rather than Dutch translations :-/ I got into computers and left my country of birth before I18N really hit the scene. I've been calling Japan home for a quarter+ century now :-? Guess we need someone else to look after po/nl.po ... @Ilia> Can you explain what those ADF trailing lines are about for the hp5590 backend? I have no idea and that makes it very difficult to translate the messages on lines 133-139. Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Code freeze and release preparations for 1.0.28 (was Re: [ITR] Intent To Release: sane-backends-1.0.28)
Hi Olaf, I guess those are marked as fuzzy. The gettext tools will preseed untranslated message strings based on "similar" translated strings. Obviously, that sometimes leads to radically wrong translations. These fuzzy strings will *not* be used at run-time. They are just there in an attempt to help the translator. I see. No worries. The "linier" comes from the kvs1025 backed and is one of the gamma profile values the user can select. Pretty sure that was meant to be "linear". Perhaps I could fix this post release then. I will "fix" the translation but leave the original. Cheers, Ralph -- sane-devel mailing list: sane-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Code freeze and release preparations for 1.0.28 (was Re: [ITR] Intent To Release: sane-backends-1.0.28)
Hi Ralph, Ralph Little writes: > Hi,I have grabbed to en_GB.po file and I have engaged the services of > poedit to work through the texts. Good. > I have a few comments: > 1) Some of the GB translations are obviously completely wrong. I > assume that the original messages have radically change from their > original intentions. I guess those are marked as fuzzy. The gettext tools will preseed untranslated message strings based on "similar" translated strings. Obviously, that sometimes leads to radically wrong translations. These fuzzy strings will *not* be used at run-time. They are just there in an attempt to help the translator. > 2) Some of the original US messages contain Britishisms (for want of a > better term!). Should we correct them in the original source (for > example, "behaviour"). Please keep that for after the 1.0.28 release. > 3) There are a few original messages which have questionable or > contorted grammar. Should we fix those also before release? See above. Just focus on creating good translations for now. BTW, I certainly welcome a thorough review of all the strings by someone with native English proficiency. > 4) I have one or two questions about some spellings which I think are > wrong but I am not sure. One such example is Linier which I think was > probably intended to be Linear but might be something else of which I > am unfamiliar. The "linier" comes from the kvs1025 backed and is one of the gamma profile values the user can select. Pretty sure that was meant to be "linear". > Longer term, does it make sense to try to reduce the number of > repetitions? Yes, but I'm not sure how feasible that is. Volunteers welcome! > Cheers,Ralph Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Code freeze and release preparations for 1.0.28 (was Re: [ITR] Intent To Release: sane-backends-1.0.28)
Hi,Related to translations, I notice that there is no en_GB for xsane.If there are no objections, I volunteer to create one and produce the necessary transactions. I have registered with GitLab and sent a request to join. I have contributed some Canon scanner changes with Rolf in the past and am keen to contribute again, in particular the network ADF issues that plague many of the Canon imageClass multi function machines. Cheers,Ralph -- sane-devel mailing list: sane-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Code freeze and release preparations for 1.0.28 (was Re: [ITR] Intent To Release: sane-backends-1.0.28)
Hi,I have grabbed to en_GB.po file and I have engaged the services of poedit to work through the texts.I have a few comments: 1) Some of the GB translations are obviously completely wrong. I assume that the original messages have radically change from their original intentions. 2) Some of the original US messages contain Britishisms (for want of a better term!). Should we correct them in the original source (for example, "behaviour"). 3) There are a few original messages which have questionable or contorted grammar. Should we fix those also before release? 4) I have one or two questions about some spellings which I think are wrong but I am not sure. One such example is Linier which I think was probably intended to be Linear but might be something else of which I am unfamiliar. Longer term, does it make sense to try to reduce the number of repetitions? Cheers,Ralph -- sane-devel mailing list: sane-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Code freeze and release preparations for 1.0.28 (was Re: [ITR] Intent To Release: sane-backends-1.0.28)
Hi,I don't mind having a look at en_GB.What is involved? Cheers,Ralph On Wednesday, July 24, 2019, 5:35:21 a.m. PDT, Olaf Meeuwissen wrote: Hi again all, Still following the release schedule on our [1.0.28 milestone][1], our master branch is now (2019-07-24 12:00UTC) in code freeze. Please do *not* push/merge to master unless it fixes - hardware destroying bugs (no reports at present), - compile failures (our CI is clean so we're looking good), - completely unusable backends, or - documentation In case of doubt, ping the list or [submit an issue][2]. [1]: https://gitlab.com/sane-project/backends/-/milestones/2 [2]: https://gitlab.com/sane-project/backends/issues @povilas> Thanks for fixing that genesys backend calibration file bug. See https://gitlab.com/sane-project/backends/issues/97 I've been tinkering with our project's [Releases page][3] on GitLab.com. When we moved, that page didn't exist yet and I put our "releases" so far on the repository's [Tags][4] page for lack of a better alternative. GitLab.com seeded the former from the latter but that created quite a mess in terms of version ordering for the Releases. That has now been sorted out. I still want to convert the notes to Markdown, though. When we release 1.0.28, the Releases page will be updated automatically, courtesy of our CI! [3]: https://gitlab.com/sane-project/backends/-/releases [4]: https://gitlab.com/sane-project/backends/-/tags We now have a week to update translations as well. I just pushed a sync of all the po/*.po files against the latest source. I thought of Cc:ing the Last-Translator entries in those files, but most of those addresses are so old I figured I'd better not. For the recent ones, coverage is pretty good already. Here are some stats, sorted by percentage of the strings that are translated. Translated Fuzzy Untranslated 100.00% 0.00% 0.00%: uk.po 99.33% 0.42% 0.25%: he.po 99.33% 0.42% 0.25%: c...@valencia.po 99.33% 0.42% 0.25%: ca.po 98.24% 0.75% 1.00%: nl.po 84.95% 6.27% 8.78%: sv.po 75.33% 8.70% 15.97%: de.po 74.75% 8.86% 16.39%: fr.po 74.67% 8.95% 16.39%: pl.po 72.07% 10.12% 17.81%: gl.po 72.07% 10.12% 17.81%: es.po 68.65% 11.79% 19.57%: en_GB.po 66.47% 12.79% 20.74%: eo.po 65.55% 13.55% 20.90%: it.po 56.77% 16.64% 26.59%: da.po 56.35% 9.78% 33.86%: ja.po 52.34% 17.89% 29.77%: fi.po 52.17% 18.14% 29.68%: bg.po 49.41% 16.64% 33.95%: ru.po 49.25% 19.15% 31.61%: cs.po 21.82% 13.96% 64.21%: pt.po 16.89% 16.14% 66.97%: nb.po 15.64% 11.12% 73.24%: hu.po I will fix up nl.po myself but the rest is for interested parties (I may take a look at ja.po and en_GB.po, though). If you intend to work on any of these files, please let the list know so we can coordinate things. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org -- sane-devel mailing list: sane-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] Code freeze and release preparations for 1.0.28 (was Re: [ITR] Intent To Release: sane-backends-1.0.28)
Hi again all, Still following the release schedule on our [1.0.28 milestone][1], our master branch is now (2019-07-24 12:00UTC) in code freeze. Please do *not* push/merge to master unless it fixes - hardware destroying bugs (no reports at present), - compile failures (our CI is clean so we're looking good), - completely unusable backends, or - documentation In case of doubt, ping the list or [submit an issue][2]. [1]: https://gitlab.com/sane-project/backends/-/milestones/2 [2]: https://gitlab.com/sane-project/backends/issues @povilas> Thanks for fixing that genesys backend calibration file bug. See https://gitlab.com/sane-project/backends/issues/97 I've been tinkering with our project's [Releases page][3] on GitLab.com. When we moved, that page didn't exist yet and I put our "releases" so far on the repository's [Tags][4] page for lack of a better alternative. GitLab.com seeded the former from the latter but that created quite a mess in terms of version ordering for the Releases. That has now been sorted out. I still want to convert the notes to Markdown, though. When we release 1.0.28, the Releases page will be updated automatically, courtesy of our CI! [3]: https://gitlab.com/sane-project/backends/-/releases [4]: https://gitlab.com/sane-project/backends/-/tags We now have a week to update translations as well. I just pushed a sync of all the po/*.po files against the latest source. I thought of Cc:ing the Last-Translator entries in those files, but most of those addresses are so old I figured I'd better not. For the recent ones, coverage is pretty good already. Here are some stats, sorted by percentage of the strings that are translated. Translated Fuzzy Untranslated 100.00% 0.00% 0.00%: uk.po 99.33% 0.42% 0.25%: he.po 99.33% 0.42% 0.25%: c...@valencia.po 99.33% 0.42% 0.25%: ca.po 98.24% 0.75% 1.00%: nl.po 84.95% 6.27% 8.78%: sv.po 75.33% 8.70% 15.97%: de.po 74.75% 8.86% 16.39%: fr.po 74.67% 8.95% 16.39%: pl.po 72.07% 10.12% 17.81%: gl.po 72.07% 10.12% 17.81%: es.po 68.65% 11.79% 19.57%: en_GB.po 66.47% 12.79% 20.74%: eo.po 65.55% 13.55% 20.90%: it.po 56.77% 16.64% 26.59%: da.po 56.35% 9.78% 33.86%: ja.po 52.34% 17.89% 29.77%: fi.po 52.17% 18.14% 29.68%: bg.po 49.41% 16.64% 33.95%: ru.po 49.25% 19.15% 31.61%: cs.po 21.82% 13.96% 64.21%: pt.po 16.89% 16.14% 66.97%: nb.po 15.64% 11.12% 73.24%: hu.po I will fix up nl.po myself but the rest is for interested parties (I may take a look at ja.po and en_GB.po, though). If you intend to work on any of these files, please let the list know so we can coordinate things. Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
