Re: How to translate with msgctxt ?
Op Wo, 2009-01-14 om 08:13 +0100 skryf Yannig MARCHEGAY: > Hello everybody, > > Gtranslator does not (yet) let us translate files with msgctxt texts. > When I want to do so, I have to do it with gedit (or lokalize). Is there > another way to do? > > Thanks, > Yannig Marchegay You can also try out Virtaal: http://translate.sourceforge.net/wiki/virtaal/index It shows msgctxt between the source and target text, right there where you are looking when translating. The 0.2 release has been out for a while, and the current development version is vastly improved. So if you are missing some features, feel free to report in our bugzilla - it is probably already done in SVN. There are packages for Debian/Ubuntu, Fedora, Mandriva, and even Windows. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/language-and-dialect-codes ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Yoruba, Hausa and Igbo (yo, ha, ig) po files
Hi Thomas, On Tue, Jan 13, 2009 at 10:57:14AM -0500, Thomas Thurman wrote: > Ysgrifennodd Marcel Telka: >> On Mon, Jan 12, 2009 at 09:43:51PM -0500, Thomas Thurman wrote: >>> Maybe in future we need to make the gettext tools enforce a rule that >>> the header block of a .po file contains licence information, instead >>> of assuming it's okay to leave it in the comments. >> >> Then we should also enforce compiler (gcc) to add license information to >> binaries... >> >> Do we really want that? > > Yes, I'd like that too. Actually, it would be really useful to warn > people linking non-GPL binaries against GPL libraries. > > But I don't think the cases are parallel. You can't point some tool at > a compiled binary and get the source code back. You can throw .mo files > at msgunfmt and get *almost* the original .po back, but lacking the You could do this with assembler source code too :-). Lack of a tool to do it with C/C++/whatever is not a reason :-). I think both cases ARE parallel. > comments; if the comments are just comments, that's fine because they're > just hints to humans, but if they contain actual useful metadata, Are we considering copyright info as an "useful metadata"? If I want I could add my own comments to a po file with another kind of "useful" metadata. In general, all comments could be considered "useful metadata". > there's no reason that metadata shouldn't live in the header block along > with the metadata we already carry, like contact email address and name > of the last translator. Good point. Do we need such data in the header? For what purposes? Do we have something similar in C/C++ (compiled, sources)? The answer is no :-). > > Honestly, the only metadata that *needs* to be in the header block is > the content encoding; everything else is for human convenience (author > name and contact details could live in comments as licence data already > does, date can be figured out from source control, project can be > figured out from the place the .po or .mo file is found, language team > can be figured out from the pathname and the project name). There's no > reason not to add another field to the mix to stop cases like this from > happening again. Exactly. There is no reason to keep such data in po file. What about get rid off of that data? To clarify: I am not voting against adding copyright data into the header, nor voting for removing some data from there. I am just showing that there could be also other possible view... ... and, I am voting for no change. :-) Have a nice day. -- +---+ | Marcel Telka e-mail: mar...@telka.sk | |homepage: http://telka.sk/ | |jabber: mar...@jabber.sk | +---+ ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: UI/string changes in gnome-control-center
Il giorno mer, 07/01/2009 alle 17.36 -0600, Federico Mena Quintero ha scritto: > Hi, translators and literati, > > I just committed some changes to gnome-control-center/capplets/display > in trunk which change the look of the UI a bit. Also, strings in the > Glade file in there may have changed a bit. Federico, is it intentional that this capplet uses display, screen, and monitor terms? ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Using Git and separating translations into their own l10n-LL repository
El dc 14 de 01 de 2009 a les 00:42 +, en/na Simos Xenitellis va escriure: > On Tue, Jan 13, 2009 at 11:31 PM, Gil Forcada wrote: > > Hi Simos, > > > > Great explanation, a couple of questions: > > > > - There would be any way to have in a single folder the code and > > translations (aka, the way is right now)? There are some translators > > (I'm counting in) that likes to have the code also. > > I am not sure which module you have in mind. Sorry, I wasn't really clear. I meant to keep like it is now with code and translations together. > I would say that the idea is, if the translation files are expected to > be managed by damned-lies/l10n.gnome.org, they should reside in the > l10n-LL submodule. > > > - The same concern about maintainers forgetting to git pull(?) > > translators is expanded, now they should git pull(?) every single git > > repository (if 160 languages, 160 git pulls(?) before each release). > > The 'git submodule update' command, when you run in from the 'l10n' > supermodule, > pulls all the l10n-LL repositories automatically by default. > There is an option to 'git submodule update' to pull individual > language repositories as well. If I understand correctly the repository will be like: l10n - l10n-LL -- evolution --- po LL.po -- eog --- po LL.po ... So if they update the whole l10n module (the top module) they will get all translations from all modules not all translations from their module. Cheers, > > Also, if the new DL will have commit functionality (maybe in half a > > year, Claude ... :) and then *all* translations will be committed this > > way, wouldn't be overkill to have all this system? > > > > I mean, if it's a temporal situation that, shouldn't be more productive > > to instead of "wasting" time doing this git submodule thing to provide > > resources and time to get commit functionality to DL that seems to be > > more desired by translators (that's my guess no data actually, just > > supposed so my arguments seems better :D). > > I would consider that separating code from localisation files would be > a fundamental improvement rather than a temporary solution. > The issue of manpower to make such changes is the main disadvantage. > > It would be easier to provide commit support to damned-lies when > we have separated l10n-LL repositories. Damned-lies would 'auto'-commit > only to designated repositories. > > I do not know the details of the SVN hooks and damned-lies. I think > that if a commit/push to a project would call a hook that would invoke > 'intltool-update -P' (create POT template file) and store it > somewhere, then damned-lies would not need to clone locally any other > GNOME modules. > > To add a few more advantages, > 1. Can add access controls for translators to the l10n-LL repositories. > 2. It allows translators to make changes across all translations (for > example, change 'widget' in all my translations of GNOME). > 3. Pootle could be adapted to perform easier GNOME translation marathons. > 4. GTranslator could work as KBabel, it would clone the l10n-LL > repository and would be able to show all translations in a huge sorted > list. This way, similar translations can be easily identified. > > > > > El dt 13 de 01 de 2009 a les 23:01 +, en/na Simos Xenitellis va > > escriure: > >> Hi All, > >> > >> This is a long-ish post regarding the migration to Git and > >> what we can do to make l10n a bit better. > >> > >> Here I suggest to use the 'git submodule' support > >> so that the translation material for each language > >> reside in a single repository. > >> Comments would be appreciated. > >> If all is fine, I'll put this, with more details, to live.gnome.org. > >> > >> When splitting the l10n files from each module, there is a choice to either > >> 1. create a companion repository for each module (for example, for > >> mousetweaks, create 'mousetweaks-l10n') > >> that will hold all localisation files for all languages, for this module. > >> If we have 1000 modules, there would be 1000 additional companion l10n > >> modules. > >> 2. create a repository for each language, and this repository will > >> contain all localisation files for all modules. > >> If we have 1000 modules, there would be just 160 additional l10n > >> repositories (it's one new repository per language). > >> > >> The right choice appears to be to create one repository per language. > >> There are many reasons which can be discussed if deemed necessary. > >> > >> The rest of the e-mail shows how the separated repositories look like. > >> I used as an example the mousetweaks and vinagre modules, for the el, > >> es, fr and sv languages. > >> Both have help/ and po/ subdirectories with l10n material. > >> You can fork the generated (six) repositories from > >> http://github.com/simos/ if you want to try them out. > >> > >> STRUCTURE (l10n-LL) > >> A language repository name is of the form 'l10n-LL', where LL is the > >> ISO 639 (-123) language code as usual
A question about string freeze.
Hi all, I need to modify (shorten actually) an already existing string in brasero so as to reuse it somewhere else and I was wondering if that was OK. Brasero may or may not be included and therefore we try to respect the freeze. Thanks for your answer Philippe ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: A question about string freeze.
Am Mittwoch, den 14.01.2009, 16:48 +0100 schrieb Philippe Rouquier: > Hi all, > > I need to modify (shorten actually) an already existing string in > brasero so as to reuse it somewhere else and I was wondering if that > was OK. Brasero may or may not be included and therefore we try to > respect the freeze. We're in String Change Announcement Period. String freeze starts on Feb 16: http://live.gnome.org/TwoPointTwentyfive andre -- mailto:ak...@gmx.net | failed http://www.iomc.de/ | http://blogs.gnome.org/aklapper ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: UI/string changes in gnome-control-center
On Wed, 2009-01-14 at 14:50 +0100, Luca Ferretti wrote:
[Display capplet]
> Federico, is it intentional that this capplet uses display, screen, and
> monitor terms?
Uh, not really. I already changed some of the terms per Vincent's
suggestion. Would you like to see some others changed?
("Detect Displays" could be "Detect Monitors"...)
Federico
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: UI/string changes in gnome-control-center
2009/1/14 Federico Mena Quintero
> On Wed, 2009-01-14 at 14:50 +0100, Luca Ferretti wrote:
>
> [Display capplet]
> > Federico, is it intentional that this capplet uses display, screen, and
> > monitor terms?
>
> Uh, not really. I already changed some of the terms per Vincent's
> suggestion. Would you like to see some others changed?
>
> ("Detect Displays" could be "Detect Monitors"...)
Monitor i definitely better than display of monitor is what it means,
because display is very ambiguous in computer english.
>
>
> Federico
>
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> http://mail.gnome.org/mailman/listinfo/gnome-i18n
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Yoruba, Hausa and Igbo (yo, ha, ig) Licensing
On Tue, Jan 13, 2009 at 3:47 PM, Thomas Thurman wrote: > Ysgrifennodd Chris Murphy: >> >> I mounted the disk image and poked around a bit. There are no .po files >> in the root filesystem, but there is a documentation folder: >> /usr/share/doc/wazobia-release-1/ which contains licensing information, >> including the GPL and a README/eula file that explain the contents of the >> "CD" being licensed under the GPL. > > Now that IS very interesting. So they explicitly put their work under the > GPL, then? Chris, would you mind attaching the file (or even the whole relevant directory?) I'd poke it myself, but besides jury duty I also have family in town. :/ Thanks- Luis ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Yoruba, Hausa and Igbo (yo, ha, ig) Licensing
On Wed, Jan 14, 2009 at 6:58 PM, Luis Villa wrote: > On Tue, Jan 13, 2009 at 3:47 PM, Thomas Thurman wrote: >> Ysgrifennodd Chris Murphy: >>> >>> I mounted the disk image and poked around a bit. There are no .po files >>> in the root filesystem, but there is a documentation folder: >>> /usr/share/doc/wazobia-release-1/ which contains licensing information, >>> including the GPL and a README/eula file that explain the contents of the >>> "CD" being licensed under the GPL. >> >> Now that IS very interesting. So they explicitly put their work under the >> GPL, then? > > Chris, would you mind attaching the file (or even the whole relevant > directory?) I'd poke it myself, but besides jury duty I also have > family in town. :/ Never mind, just saw the followup email. Luis ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Yoruba, Hausa and Igbo (yo, ha, ig) Licensing
On Tue, Jan 13, 2009 at 4:17 PM, Chris Murphy wrote: > And for good measure I grabbed the files from the translations-[ha,ig,yo] > packages and tarred them up. Everything is available from the folder: > http://chrismurf.com/nigerian-translations/, including the files I > referenced earlier. Apologies for not consolidating emails. Thanks for looking into this, Chris. Couple questions: (1) Chris, if you've got a system running, can you rpm query the LICENSE field for the locales-ng package? (I'm afraid I don't remember the exact syntax for that off the top of my head, sorry.) (2) Chris, you mentioned there is "licensing information at the top" of locales-ng.tgz, but I don't see it anywhere. Could you point out exactly where it is/was? (3) I notice that /usr/share/i18n/locales/ha_NG mentions a pa...@mandriva.com- has anyone tried to contact Paolo (and/or mandriva) to see if they know about this translation work? Or is that just copied/pasted from somewhere else? Generally, James Vasile and Aaron Williamson (of Software Freedom Law Center) and I discussed this briefly today on the phone so we're paying attention to the issue and hope we can give some more definitive advice shortly. Obviously more definitive information (like contacting the Wazobia folks directly, or finding a license file like the one Chris suggests is present) would speed that up, or even better, make it a non-issue :) Luis ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Yoruba, Hausa and Igbo (yo, ha, ig) Licensing
Thanks for the suggestion to look for a LICENSE field - not really familiar with RPMs and I didn't think to look for that. Good news! All four packages (3 translations and then locales-ng) are listed as GPL in the RPM. I've uploaded the results of: rpm -qi $packagename for each package to http://chrismurf.com/nigerian-translations/license-info.txt, but the punchline is that all of them are listed as GPL in their respective packages. Hooray for metadata. Best, Chris On Wed, Jan 14, 2009 at 7:09 PM, Luis Villa wrote: > On Tue, Jan 13, 2009 at 4:17 PM, Chris Murphy wrote: > > And for good measure I grabbed the files from the translations-[ha,ig,yo] > > packages and tarred them up. Everything is available from the folder: > > http://chrismurf.com/nigerian-translations/, including the files I > > referenced earlier. Apologies for not consolidating emails. > > Thanks for looking into this, Chris. Couple questions: > > (1) Chris, if you've got a system running, can you rpm query the > LICENSE field for the locales-ng package? (I'm afraid I don't remember > the exact syntax for that off the top of my head, sorry.) > > (2) Chris, you mentioned there is "licensing information at the top" > of locales-ng.tgz, but I don't see it anywhere. Could you point out > exactly where it is/was? > > (3) I notice that /usr/share/i18n/locales/ha_NG mentions a > pa...@mandriva.com- has anyone tried to contact Paolo (and/or > mandriva) to see if they know about this translation work? Or is that > just copied/pasted from somewhere else? > > Generally, James Vasile and Aaron Williamson (of Software Freedom Law > Center) and I discussed this briefly today on the phone so we're > paying attention to the issue and hope we can give some more > definitive advice shortly. Obviously more definitive information (like > contacting the Wazobia folks directly, or finding a license file like > the one Chris suggests is present) would speed that up, or even > better, make it a non-issue :) > > Luis > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
