Re: OCRFeeder project in GNOME
Hi Claude, Regarding your email chained below, I think I have done (some of?) the changes to have a good integration with intltool. I removed the .mo and .pot files and added the POTFILES.in, together with the usage of intltool-* commands when the project is built using the make file. Please let me know if this meets the needs you have for easy i18n. Thank you, -- Joaquim Rocha Claude Paroz wrote: Le dimanche 24 janvier 2010 à 22:34 +0100, Joaquim Rocha a écrit : Hi Joaquim, We'll be pleased to add your program to the l10n.gnome.org platform, as soon as some basic steps are completed. Please take care that ocrfeeder be compatible with intltool. Adding a po/POTFILES.in file containing source files should be the first thing to do. A po/LINGUAS file is also good practice, even if it is not always required depending on your build toolchain. See http://bazaar.launchpad.net/%7Eintltool/intltool/trunk/annotate/head %3A/README for further details. po/ocrfeeder.pot can then be removed from Git, as it is dynamically created by intltool. You should also remove the locale directory from the repository, as mo files should be dynamically created at build/install time (some additional code may be required in setup.py). It would also be welcomed to have a GNOME bugzilla product for ocrfeeder. Cheers, Claude signature.asc Description: OpenPGP digital signature ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
dasher string change
The canonical website for dasher now sells car insurance - I really would like to change the URL (and update a few non-translatable bits) in the help documentation to avoid unpleasant surprises. (for the 2.30 release) There was also a request to make Copyright a translatable string. May I apply the enclosed patch? (I have successfully read the help in French and German, so don't think that it breaks anything.) (It contains the string changes, not the modified git-version-gen which still needs a little testing which would obviously be applied when the time comes.) Cheers, Patrick diff --git a/.gitignore b/.gitignore index 800dac6..67acd0e 100644 --- a/.gitignore +++ b/.gitignore @@ -5,6 +5,7 @@ *.mo *.o *.omf +.tarball-version Makefile Makefile.in dasher.xml diff --git a/Data/Help/Gnome/C/dasher.xml b/Data/Help/Gnome/C/dasher.xml index 9c0c295..7ea2e38 100644 --- a/Data/Help/Gnome/C/dasher.xml +++ b/Data/Help/Gnome/C/dasher.xml @@ -5,7 +5,7 @@ titleDasher Manual/title corpauthor role=maintainerThe Dasher Project/corpauthor copyright - year2006/year + year2010/year holderThe Dasher Project/holder /copyright legalnotice @@ -159,7 +159,7 @@ load up an example file, then write away!/para para It's quite hard to convey in words what Dasher looks like, so please visit ulink - url=http://www.dasher.org.uk/; type=httpwww.dasher.org.uk/ulink to see movies./para + url=http://www.inference.phy.cam.ac.uk/dasher/; type=httphttp://www.inference.phy.cam.ac.uk/dasher//ulink to see movies./para /sect2 sect2 @@ -266,8 +266,7 @@ /figure para If you find Dasher hard to imagine based on these static pictures, please take a look -at the movies on ulink url=http://www.dasher.org.uk/; type=http -www.dasher.org.uk/ulink./para +at the movies on ulink url=http://www.inference.phy.cam.ac.uk/dasher/; type=httphttp://www.inference.phy.cam.ac.uk/dasher//ulink./para !--% When you try Dasher for the first time, please read the tips for novices.-- @@ -980,8 +979,7 @@ USB mouse on any computer.) Can you waggle one finger or one foot? These head-mice can be used to track fingers and feet as well as heads. For a detailed comparison of SmartNav3 with Headmouse Extreme, please see ulink - url=http://www.inference.phy.cam.ac.uk/dasher/Headmouse.html; type=http - http://www.inference.phy.cam.ac.uk/dasher/Headmouse.html/ulink./para + url=http://www.inference.phy.cam.ac.uk/dasher/Headmouse.html; type=httphttp://www.inference.phy.cam.ac.uk/dasher/Headmouse.html/ulink./para paraIf you are severely paralysed, the best option may be a gaze tracker. Do you have control of where your eyes are looking? With a gaze tracker we can write at 25 words per @@ -1296,15 +1294,15 @@ titleAuthors/title para applicationDasher/application was written by the members of The Dasher Project -(emaildas...@mrao.cam.ac.uk/email). To find more information about it, please visit +(emaildas...@inf.phy.cam.ac.uk/email). To find more information about it, please visit applicationDasher's/application ulink url=http://www.inference.phy.cam.ac.uk/dasher/; type=http Web page/ulink. Please - send all comments, suggestions, and bug reports to the ulink url=http://bugs.gnome.org; + send all comments, suggestions, and bug reports to the ulink url=http://bugzilla.gnome.org/enter_bug.cgi?product=dasher; type=httpGNOME bug tracking database/ulink. Instructions for submitting bug reports can be found on-line at ulink url=http://bugs.gnome.org/Reporting.html; type=http http://bugs.gnome.org/Reporting.html/ulink. If you are using GNOME 1.1 or later, you can also use command commandbug-buddy/command for submitting bug reports. /para -para This manual was written by The Dasher Project (emaildas...@mrao.cam.ac.uk/email). +para This manual was written by The Dasher Project (emaildas...@inf.phy.cam.ac.uk/email). Please send all comments and suggestions regarding the manual to the GNOME Documentation Project at emaild...@gnome.org/email. You can also add your comments online by using ulink type=http url=http://www.gnome.org/gdp/doctable/;GNOME Documentation Status diff --git a/Data/Help/Gnome/ca/ca.po b/Data/Help/Gnome/ca/ca.po index 746ab42..61cf988 100644 --- a/Data/Help/Gnome/ca/ca.po +++ b/Data/Help/Gnome/ca/ca.po @@ -79,8 +79,8 @@ msgid The Dasher Project msgstr El project del Dasher #: C/dasher.xml:8(year) -msgid 2006 -msgstr 2006 +msgid 2010 +msgstr 2010 #: C/dasher.xml:12(para) msgid @@ -429,12 +429,12 @@ msgstr #: C/dasher.xml:161(para) msgid It's quite hard to convey in words what Dasher looks like, so please visit -ulink url=\http://www.dasher.org.uk/\; type=\http\www.dasher.org.uk/ +ulink
Re: dasher string change
Le lundi 08 mars 2010 à 19:31 +, Patrick Welche a écrit : The canonical website for dasher now sells car insurance - I really would like to change the URL (and update a few non-translatable bits) in the help documentation to avoid unpleasant surprises. (for the 2.30 release) Hi Patrick, As far as documentation is concerned, feel free to make the changes, as it is not submitted to any freeze. There was also a request to make Copyright a translatable string. That's nice, but not critical at all. Please do it after dasher will have branched for 2.30. I cannot comment on other more technical changes. Claude May I apply the enclosed patch? (I have successfully read the help in French and German, so don't think that it breaks anything.) (It contains the string changes, not the modified git-version-gen which still needs a little testing which would obviously be applied when the time comes.) Cheers, Patrick ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: OCRFeeder project in GNOME
Le lundi 08 mars 2010 à 18:20 +0100, Joaquim Rocha a écrit : Hi Claude, Regarding your email chained below, I think I have done (some of?) the changes to have a good integration with intltool. I removed the .mo and .pot files and added the POTFILES.in, together with the usage of intltool-* commands when the project is built using the make file. Please let me know if this meets the needs you have for easy i18n. We're quite there. Please include the po/LINGUAS file. http://l10n.gnome.org/module/ocrfeeder/ It would also be nice to be able to translate the desktop file. Thanks for your efforts. Claude Claude Paroz wrote: Le dimanche 24 janvier 2010 à 22:34 +0100, Joaquim Rocha a écrit : Hi Joaquim, We'll be pleased to add your program to the l10n.gnome.org platform, as soon as some basic steps are completed. Please take care that ocrfeeder be compatible with intltool. Adding a po/POTFILES.in file containing source files should be the first thing to do. A po/LINGUAS file is also good practice, even if it is not always required depending on your build toolchain. See http://bazaar.launchpad.net/%7Eintltool/intltool/trunk/annotate/head %3A/README for further details. po/ocrfeeder.pot can then be removed from Git, as it is dynamically created by intltool. You should also remove the locale directory from the repository, as mo files should be dynamically created at build/install time (some additional code may be required in setup.py). It would also be welcomed to have a GNOME bugzilla product for ocrfeeder. Cheers, Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: OCRFeeder project in GNOME
Hi Claude, Am Montag, den 08.03.2010, 21:02 +0100 schrieb Claude Paroz: http://l10n.gnome.org/module/ocrfeeder/ Please dont't forget to assign it to a release set. Otherwise, I'm afraid of that no translator will recognize it. Cheers, Mario ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
String additions to 'gnome-control-center.master'
This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'gnome-control-center.master': + %d %s by %d %s Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'gnome-control-center.master'
GNOME Status Pages írta: There have been following string additions to module 'gnome-control-center.master': This was me, and a forgotten string: https://bugzilla.gnome.org/review?bug=612015 Regards Gabor Kelemen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
