Re: RFE: Vertimus and assigned translator
Il giorno mar, 20/01/2009 alle 11.32 +0100, Marcel Telka ha scritto: In all cases, when a translation is locked for too long time some administrative intervention is needed. Comment for Vertimus authors: Today it is not possible for me (as a coordinator) to unlock such stuck translator and make it available to someone else. Well, here is a backdoor now: committer accounts always have a Inform of submission available. This resets the status ;) IMHO, trying to merge the current l10n.g.o behavior and the assigned workflow, could be better add a assigned-to property to modules. This property could act as follow: * on l10n.g.o each module can be assigned to an account I agree. * this account will receive email alerts for each action performed on him/her assigned modules (comments could be useful to notify typos/errors/proposal/memos/other) I agree. Good. Do you have yet opened a bug on bugzilla? * if the assigned account don't accept/reject the request within a week, accounts with review (or commit? dunno, but something below coordinator in order to make it faster) privileges can do this Can do what? Accept the request? Yes, it was just a safe escape from any inability to have network access something like: the assigner was arrested while traveling in another country and now languish with hunger in a remote prison... :) But now we have the inform of submission backdoor, so it's no longer needed :D ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFE: Vertimus and assigned translator
On Tue, Jan 27, 2009 at 10:53:16AM +0100, Luca Ferretti wrote: Il giorno mar, 20/01/2009 alle 11.32 +0100, Marcel Telka ha scritto: In all cases, when a translation is locked for too long time some administrative intervention is needed. Comment for Vertimus authors: Today it is not possible for me (as a coordinator) to unlock such stuck translator and make it available to someone else. Well, here is a backdoor now: committer accounts always have a Inform of submission available. This resets the status ;) Yes. I found it several days ago and it is working :-). Thanks. IMHO, trying to merge the current l10n.g.o behavior and the assigned workflow, could be better add a assigned-to property to modules. This property could act as follow: * on l10n.g.o each module can be assigned to an account I agree. * this account will receive email alerts for each action performed on him/her assigned modules (comments could be useful to notify typos/errors/proposal/memos/other) I agree. Good. Do you have yet opened a bug on bugzilla? For assigned translator feature: http://bugzilla.gnome.org/show_bug.cgi?id=568770 For emails, not yet. Feel free to file it yourself :-). -- +---+ | 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
Small gnome-user-share UI changes
Heya, One little change in the gnome-user-share UI, I removed the mentions of Paired and only used Bonded. The differences for our usage were minimal, and removing Paired from the UI means we only need to explain Bonded without getting into too much technical details for the end user. For the record, the difference between the 2 terms, nicked from the Internet: Typically, devices must authenticate with each other every time they connect to each other. This process is called pairing. However, the devices can bond instead. Bonding is similar to pairing except that both devices remember the link key for the connection. If the two devices ever want to connect to each other again, they don't need to repeat the pairing process. Information about paired and bonded devices is stored in a device database on the local device. If a remote device has bonded with the local device, its record remains in the database until it is explicitly deleted. If the remote device has paired with the local device but not bonded with it, the record is removed when the connection to the remote device terminates. Remote devices that have bonded with the local device are also called trusted devices. Cheers ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Small gnome-user-share UI changes
2009-01-27 klockan 16:32 skrev Bastien Nocera: One little change in the gnome-user-share UI, I removed the mentions of Paired and only used Bonded. The differences for our usage were minimal, and removing Paired from the UI means we only need to explain Bonded without getting into too much technical details for the end user. Note that this refers to Bluetooth/OBEX-related functionality in g-u-s. Since Bastien didn't mention this explicitly in his message, some readers might wonder what it is all about. :) — Wouter signature.asc Description: Digital signature ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Small gnome-user-share UI changes
Le mardi 27 janvier 2009 à 15:32 +, Bastien Nocera a écrit : Heya, One little change in the gnome-user-share UI, I removed the mentions of Paired and only used Bonded. The differences for our usage were minimal, and removing Paired from the UI means we only need to explain Bonded without getting into too much technical details for the end user. For the record, the difference between the 2 terms, nicked from the Internet: Typically, devices must authenticate with each other every time they connect to each other. This process is called pairing. However, the devices can bond instead. Bonding is similar to pairing except that both devices remember the link key for the connection. If the two devices ever want to connect to each other again, they don't need to repeat the pairing process. Information about paired and bonded devices is stored in a device database on the local device. If a remote device has bonded with the local device, its record remains in the database until it is explicitly deleted. If the remote device has paired with the local device but not bonded with it, the record is removed when the connection to the remote device terminates. Remote devices that have bonded with the local device are also called trusted devices. Thanks for the explanation. It would be great to add the first paragraph as a translator comment for the first occurrence of the term to translate in file-share-properties.c Regards, Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Small gnome-user-share UI changes
On Tue, 2009-01-27 at 16:48 +0100, Claude Paroz wrote: snip Thanks for the explanation. It would be great to add the first paragraph as a translator comment for the first occurrence of the term to translate in file-share-properties.c It's already documented in the module docs, and I'd rather not try to explain it for translation. It's a Bluetooth term, which has probably already been translated by mobile phone makers and the likes. Feel free to add such a comment yourself if you feel it's necessary. Cheers ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Bug 569118 - Use C_() instead of Q_() with context (orca)
[: Willie Walker :] The current Orca code does the equivalent of this: In MO files contexts are separated by U+0004 from the message proper, so I used something equivalent to this in a code I work on: def C_ (c, s): s = _(c + \x04 + s) p = s.find(\x04) if p = 0: # satisfied only if no translation found s = s[p + 1:] return s -- Chusslove Illich (Часлав Илић) pgp5eM7keb1WI.pgp Description: PGP signature ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [vertimus] Merge uploaded file?
Le dimanche 25 janvier 2009 à 21:23 +0100, Luca Ferretti a écrit : Il giorno mar, 20/01/2009 alle 16.17 +0100, Claude Paroz ha scritto: Le mardi 20 janvier 2009 à 11:17 +0100, Luca Ferretti a écrit : Then you could: A. add a Update button near warning message - translator can click on it to force the merge B. provide two links, one for original uploaded file, one for the merged one C. other? any idea? Thanks Luca for your ideas. I finally choose B (as Vincent also suggested), even if this is a little heavy in my opinion. We can always improve it later. Just to make this more heavy, what about add tooltips[1] with translation status for uploaded and merged (translated, fuzzy, untranslated)? This could be helpful to immediately visually check if you have to translate new stuff. Yes, good suggestion. http://bugzilla.gnome.org/show_bug.cgi?id=569377 A tooltip to explain the diff with previous link could be good too. BTW this message don't appear in damned-lies PO file :( This has been changed today while introducing multi-diff support. Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Automated translation into en_GB
Le mardi 27 janvier 2009 à 00:42 +0100, Kenneth Nielsen a écrit : 2009/1/26 Claude Paroz cla...@2xlibre.net: Le lundi 26 janvier 2009 à 12:42 +0100, Kenneth Nielsen a écrit : I don't have much fate in anything autotranslated. One time that I proofread a translation that was autoupdated from a compendium and then supposedly read through by the translater I think I used more time on the proofreading than he did doing the translation. I suspect this is similar for most other languages and therefore I don't think it is a good idea to add functionality for it, that will just encurage bad translation practices. Any english looking language is a special case and should be treated as such. I suppose each language coordinator is experienced enough to judge this himself :-) Sure, let me refraise it in a way so that I don't speak for anyone else. I personally don't think automated translations in any shape, way or form, have any justification in free software for any other languages than the english derivatives. One could of course argue, that it will always be possible to people that don't give a damn to commit broken (possible automated) translations i.e. an automate pretranslations script in DL won't change that, however I do think there is a _availability_ argument in there also. In any case, my sole concerns with the previous e-mail was that before you (being one of the DL gurus) consider using any time on this (no matter how little) I think there should be maybe a couple of positive feedbacks first? Other than from the english family of languages, which can't cover more than 4 of our 118 languages. I think some of all the other stuff you guys are talking about doing with DL is way more important. I understand your concern about automated translation, which is bad in most cases. But apart english derivatives, this might be useful for other language derivatives, or for transliteration (e.g. latin - cyrillic conversion). That's why the functionality shouldn't be put aside without consideration. Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Bug 569118 - Use C_() instead of Q_() with context (orca)
Hey All:
We've had some good discussion at
http://bugzilla.gnome.org/show_bug.cgi?id=569118 for how to handle
Python files.
http://bugzilla.gnome.org/show_bug.cgi?id=569118#c9 provides the Python
equivalent for C_.
http://bugzilla.gnome.org/show_bug.cgi?id=569118#c17 provides a script
that hammers through the *.po files to change them from Q_ form to C_ form.
I've attached two patches to the bug for Orca - one for the source code
and another for the *.po files. It all seems to work fine in my testing
between the C locale and the en_GB locale -- I made some temporary mods
to the en_GB.po file to make sure I was getting the right string for the
right context.
In the past, I was slapped seriously by the l10n team for touching *.po
files. So, I'm requesting permission here before I check in the *.po
changes. Is this OK with you all?
Will
Willie Walker wrote:
Hi All:
I'm looking at http://bugzilla.gnome.org/show_bug.cgi?id=569118, which
is a request to migrate to C_ from Q_. Doing this in the C programming
language seems pretty straightforward, but I'm puzzled about how to do
it in Python.
The current Orca code does the equivalent of this:
def Q_(s):
s = _(s)
s = s[s.find('|')+1:]
return s
This was easy to do since we controlled the whole string. Now that a
context is explicitly called out with the C_ method, it seems like we
might need to make a different gettext method call. I'm not quite sure
what to do.
Is there a Python precedence that exists that I can take a look at?
Will
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Automated translation into en_GB
2009-01-27 klockan 20:06 skrev Claude Paroz: I understand your concern about automated translation, which is bad in most cases. But apart english derivatives, this might be useful for other language derivatives, or for transliteration (e.g. latin - cyrillic conversion). For what it's worth, in Dutch there are two slightly different spellings as well. While we haven't run into any serious issues yet (the differences are really small and most people won't notice anyway), automated conversion scripts could be a way to let us have both (simple word replacements would be enough for the conversion). It should be noted, however, that right now we don't care at all about these spelling variatons, and it's quite likely we never will. :) — Wouter [1] Named green and white spelling, inspired by the cover color of the book defining that particular spelling variation. signature.asc Description: Digital signature ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Bug 569118 - Use C_() instead of Q_() with context (orca)
2009-01-27 klockan 20:09 skrev Willie Walker: In the past, I was slapped seriously by the l10n team for touching *.po files. So, I'm requesting permission here before I check in the *.po changes. Is this OK with you all? Hi Willie, Thanks for working on making translators' lifes easier. Could you, as a proof of concept, attach a diff of the nl.po file (before and after the conversion) to that bug report, so that I can review it? Thanks. — Wouter signature.asc Description: Digital signature ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Bug 569118 - Use C_() instead of Q_() with context (orca)
Em Ter, 2009-01-27 às 14:09 -0500, Willie Walker escreveu: In the past, I was slapped seriously by the l10n team for touching *.po files. So, I'm requesting permission here before I check in the *.po changes. Is this OK with you all? This might be more to the point: for file in po/*.po; do sed -i s+msgid \\([^|]*\)|+msgctxt \\1\\nmsgid \+ $file done But yes, let's see what happens to nl.po before doing it for every file :) -- Leonardo Fontenelle http://leonardof.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Bug 569118 - Use C_() instead of Q_() with context (orca)
Leonardo F. Fontenelle wrote: Em Ter, 2009-01-27 às 14:09 -0500, Willie Walker escreveu: In the past, I was slapped seriously by the l10n team for touching *.po files. So, I'm requesting permission here before I check in the *.po changes. Is this OK with you all? This might be more to the point: for file in po/*.po; do sed -i s+msgid \\([^|]*\)|+msgctxt \\1\\nmsgid \+ $file done Heh. But yes, let's see what happens to nl.po before doing it for every file :) Comment #23 from the bug (http://bugzilla.gnome.org/show_bug.cgi?id=569118#c23) Thanks, Willie. This approach to update PO files seems to work quite well. The nl.po patch looks good, please commit nl.po for me. Thanks again :) I also separated the *.po diffs into individual files here: http://master.gnome.org/~wwalker/569118/ This change touches a number of files, so I'd like to get it in sooner than later so as to avoid needing to keep up with a moving target. So, I'll hold off until tomorrow afternoon (US Eastern). If there are great cries of NO! NO! NO!, I won't check it in. Otherwise, I'll check it in. Will ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Bug 569118 - Use C_() instead of Q_() with context (orca)
Willie Walker írta: This change touches a number of files, so I'd like to get it in sooner than later so as to avoid needing to keep up with a moving target. Looks ok for hu.po. Only a side note: the lines like #. ONLY TRANSLATE THE PART AFTER THE PIPE CHARACTER | are now unnecessary, please throw them out of the source files. Regards Gabor Kelemen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Bug 569118 - Use C_() instead of Q_() with context (orca)
Gabor Kelemen wrote: Willie Walker írta: This change touches a number of files, so I'd like to get it in sooner than later so as to avoid needing to keep up with a moving target. Looks ok for hu.po. Thanks! Only a side note: the lines like #. ONLY TRANSLATE THE PART AFTER THE PIPE CHARACTER | are now unnecessary, please throw them out of the source files. The patch at http://bugzilla.gnome.org/attachment.cgi?id=127348 tosses them already. Thanks! Will ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Bug 569118 - Use C_() instead of Q_() with context (orca)
2009/1/27 Willie Walker william.wal...@sun.com: Leonardo F. Fontenelle wrote: Em Ter, 2009-01-27 às 14:09 -0500, Willie Walker escreveu: In the past, I was slapped seriously by the l10n team for touching *.po files. So, I'm requesting permission here before I check in the *.po changes. Is this OK with you all? This might be more to the point: for file in po/*.po; do sed -i s+msgid \\([^|]*\)|+msgctxt \\1\\nmsgid \+ $file done Heh. But yes, let's see what happens to nl.po before doing it for every file :) Comment #23 from the bug (http://bugzilla.gnome.org/show_bug.cgi?id=569118#c23) Thanks, Willie. This approach to update PO files seems to work quite well. The nl.po patch looks good, please commit nl.po for me. Thanks again :) I also separated the *.po diffs into individual files here: http://master.gnome.org/~wwalker/569118/ This change touches a number of files, so I'd like to get it in sooner than later so as to avoid needing to keep up with a moving target. So, I'll hold off until tomorrow afternoon (US Eastern). If there are great cries of NO! NO! NO!, I won't check it in. Otherwise, I'll check it in. Will ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n The Danish one looks fine. Thanks. Regards Kenneth Nielsen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
gnome-keyring string and UI additions
There have been some UI and string additions in gnome-keyring: * POTFILES.in: Added egg/egg-asn1.c gcr/gcr-certificate-basics-widget.c gcr/gcr-certificate-basics-widget.glade gcr/gcr-certificate-details-widget.c These are new dialogs for viewing certificates. Many of the strings and some of the UI came over from seahorse. Cheers, Stef Walter ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
