Re: seahorse plugins not updating
On 12/02/2009, at 5:47 AM, Claude Paroz wrote: Le mercredi 11 février 2009 à 14:44 +0100, Wouter Bolsterlee a écrit : 2009-02-11 klockan 14:12 skrev Clytie Siddall: I now seem to have a problem with updating our translation for seahorse-plugins. All other modules show the update on Damned Lies once I commit the translations, but seahorse-plugins doesn't. I find this peculiar, since the update shows up in the repo [1]. [...] Thanks for any suggestions as to why this is happening. :) It's because seahorse-plugins is hosted in a submodule of the seahorse SVN repository, not in a repository of its own. http://bugzilla.gnome.org/show_bug.cgi?id=563474 No wonder I couldn't find the dratted thing if it were at the same level as trunk and branches in the seahorse module! Thanks for the heads-up. :) I hope they fix this soon. from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Damned Lies login and OpenID
Hi everyone :) I've been unable to participate for several months, so sorry if I'm not caught up with the mailing lists. I did search through this list on this topic, but couldn't find what I needed to know. Damned Lies has evidently been updated extensively since I could last participate. Great work! (My only complaint would be that downloading the latest PO file a now two-step process, instead of the one-step process we used to have.) I need to login to Damned Lies, but I'm not sure if I should create an account, or whether I should have an OpenID. Is the OpenID related to any of our GNOME logins? If it's an overall login (something I've encouraged for quite some time), how do I set one up, please? Thanks for your help. :) from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: One key stroke -- two code-points
Thanks for your prompt and helpful reply, Simos. :) On 15/06/2008, at 12:55 AM, Simos Xenitellis wrote: O/H Clytie Siddall έγραψε: Just checking: so this problem does not affect languages using precomposed Unicode? Vietnamese users _should_ be using precomposed forms for our added and combined diacritics. But I wonder if we should be ready for the fact that they might not. I was using a keyboard layout for a while which was decomposed, and I didn't know it. That could happen to others, too. With precomposed characters, the compose sequences look like dead_key_No1 dead_key_No2 Letter_A --- single codepoint Producing a single codepoint is well defined, and has been available from the start. When no precomposed forms exist, then dead_key_No1 dead_key_No2 Letter_A --- codepointA, codepointB This was not used in the X.Org Compose file (the Khmer compose sequences, first such sequences, were added to X.Org just a few days back). One thing I do not know about the Vietnamese written language is, are there characters (with combined diacritics) that no corresponding precomposed forms exist? That is, do characters exist that you cannot type them using the typical dead keys? No, despite the fact that our glyphs are scattered all over the Unicode plane, there are precomposed forms for all our characters. However, if there is a need for decomposed forms anyway, it is good know about it. I don't think there's much of a need, but there are definitely still decomposed layouts and old input versions around, and especially old fonts. We quite often get bug reports because people are still using pre-Unicode fonts. For Vietnamese, it is important to look at the xkeyboard-config project and check what does default layout do, and that it is a reasonable choice. OK. I'll try to chase that up. However, Duy is probably the best person to do that, because he has been involved with input software. Duy, do you have time to check this? (The original discussion is pasted below, for reference.) from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n On 10/06/2008, at 2:35 PM, Anousak Souphavanh wrote: Thanks, Simos for your kind and time. Much appreciated to Javier for brought a good solution indeed. Lao input method is need a similar solution. Javier please post your solution (where and how to define a new table for Khmer) so I can define these code points for Lao. On Tue, Jun 10, 2008 at 1:58 AM, Simos Xenitellis [EMAIL PROTECTED] wrote: O/H Javier SOLA έγραψε: Thanks Simos !! Actually, we have had these additions for a while in X11. Hi Javier, Checking at http://gitweb.freedesktop.org/?p=xorg/lib/libX11.git;a=tree;f=nls/en_US.UTF-8 does not show these lines at the end. It is possible that these compose sequences were added as a patch to the distribution package. We will do an issue for GTK+, and use the variable meanwhile. What file is it in GTK+? I have not been able to find it. In GTK+ (HEAD), the relevant file is http://svn.gnome.org/viewvc/gtk%2B/trunk/gtk/gtkimcontextsimple.c?view=markup However, your case of compose sequences is different from the existing compose sequences, that result to a single codepoint (you require to produce two codepoints). Therefore, the type of support you are looking for is similar to compose sequences that result to letter+diacritic mark. Several languages have characters that no pre-composed letters exist, so the compose sequence produces letter+diacritic marks (more than one codepoint). Such support is missing, and there are already bug reports for them. Bug 341341 – Compose mechanism in simple input method doesn't support decomposed forms http://bugzilla.gnome.org/show_bug.cgi?id=341341 Bug 345254 – dead accents should at least produce combining characters http://bugzilla.gnome.org/show_bug.cgi?id=345254 There is a shortcut when trying to solve the above cases of compose sequences, thus the solution I expect to be different from the Khmer compose sequences. Specifically, for the Latin compose sequences, such as (it's a made up example) dead_acute t : t́ # LETTER T WITH ACUTE one could convert to something like[ dead_acute, 't', 0]. We would put 0 for the resulting codepoint because we can deduce for this category of compose sequences that the actual codepoints are 't' and 'acute' (the resulting codepoints match the body of the compose sequence). However, for the case of Khmer, the compose sequences look independent from the resulting code points. Therefore, a new table should be required. To cut the story short, I have filed a bug report for this, Bug 537457 – Support compose sequences that produce two+ codepoints http://bugzilla.gnome.org/show_bug.cgi?id=537457 Simos Thanks, Javier Simos Xenitellis wrote O/H Javier SOLA έγραψε: Hi, I am working on Khmer localization (KhmerOS project
Re: One key stroke -- two code-points
Just checking: so this problem does not affect languages using precomposed Unicode? Vietnamese users _should_ be using precomposed forms for our added and combined diacritics. But I wonder if we should be ready for the fact that they might not. I was using a keyboard layout for a while which was decomposed, and I didn't know it. That could happen to others, too. Clytie On 10/06/2008, at 2:35 PM, Anousak Souphavanh wrote: Thanks, Simos for your kind and time. Much appreciated to Javier for brought a good solution indeed. Lao input method is need a similar solution. Javier please post your solution (where and how to define a new table for Khmer) so I can define these code points for Lao. On Tue, Jun 10, 2008 at 1:58 AM, Simos Xenitellis [EMAIL PROTECTED] wrote: O/H Javier SOLA έγραψε: Thanks Simos !! Actually, we have had these additions for a while in X11. Hi Javier, Checking at http://gitweb.freedesktop.org/?p=xorg/lib/libX11.git;a=tree;f=nls/en_US.UTF-8 does not show these lines at the end. It is possible that these compose sequences were added as a patch to the distribution package. We will do an issue for GTK+, and use the variable meanwhile. What file is it in GTK+? I have not been able to find it. In GTK+ (HEAD), the relevant file is http://svn.gnome.org/viewvc/gtk%2B/trunk/gtk/gtkimcontextsimple.c?view=markup However, your case of compose sequences is different from the existing compose sequences, that result to a single codepoint (you require to produce two codepoints). Therefore, the type of support you are looking for is similar to compose sequences that result to letter+diacritic mark. Several languages have characters that no pre-composed letters exist, so the compose sequence produces letter+diacritic marks (more than one codepoint). Such support is missing, and there are already bug reports for them. Bug 341341 – Compose mechanism in simple input method doesn't support decomposed forms http://bugzilla.gnome.org/show_bug.cgi?id=341341 Bug 345254 – dead accents should at least produce combining characters http://bugzilla.gnome.org/show_bug.cgi?id=345254 There is a shortcut when trying to solve the above cases of compose sequences, thus the solution I expect to be different from the Khmer compose sequences. Specifically, for the Latin compose sequences, such as (it's a made up example) dead_acute t : t́ # LETTER T WITH ACUTE one could convert to something like[ dead_acute, 't', 0]. We would put 0 for the resulting codepoint because we can deduce for this category of compose sequences that the actual codepoints are 't' and 'acute' (the resulting codepoints match the body of the compose sequence). However, for the case of Khmer, the compose sequences look independent from the resulting code points. Therefore, a new table should be required. To cut the story short, I have filed a bug report for this, Bug 537457 – Support compose sequences that produce two+ codepoints http://bugzilla.gnome.org/show_bug.cgi?id=537457 Simos Thanks, Javier Simos Xenitellis wrote O/H Javier SOLA έγραψε: Hi, I am working on Khmer localization (KhmerOS project). In Khmer, some of the basic vowels (which we include in the keyboard) require two code-points, so one keystroke must generate two code points. It used to be that we could do the conversion in KBX by generating a fictious code-point (Pablo Saratxaga explained this to us a few years ago), which was later translated to two real code-points by puting the conversion in the en-US locale file. I did work at the time. But now this seems to have stopped working. Does anybody knows how we can fix this? These additions (pressing a single key and producing two codepoints), are located at /usr/share/X11/locale/en_US.UTF-8/Compose The specific lines appear to be # Khmer digraphs # A keystroke has to generate several characters, so they are defined # in this file U17fb: ុះ U17fc: ុំ U17fd: េះ U17fe: ោះ U17ff: ាំ GTK+ based applications duplicate the Compose file in the gtk+ library, and currently the version of the Compose file that exists in gtk + does not include those specific compose sequences. I think these are a recent addition. Technically, it is possible for gtk+ to include compose sequences that produce more than one code points (requires small change in the code), however these recent Khmer digraphs are the only compose sequences using the facility now. To cut the long story short, you can bypass for now the GTK+ version of the Compose file and use the Compose file that comes with X.Org (shown above) by setting the environment variable GTK_IM_MODULE to xim. This should not have adverse effect to the OLPC software. It is important that if other keyboard layouts as well require compose sequences that produce two or more codepoints (such as Serbian), to add them to the XOrg Compose file. In
evolution-caldev root commits failing
To: gnome-i18n, Christian Kellner __ Hi everyone :) I just added our translation (enormous, it was ;) ) to evolution- caldav. Two things made this more difficult: 1. the PO directory does not have a LINGUAS file. Christian, it is much better l10n practice to put LINGUAS in /po, rather than relying on translators filling in ALL_LINGUAS in the /configure.in file. It's quicker for us, it means we don't have to check out the whole package, and that we won't mess up your config info. So please use /po/LINGUAS. 2. I added vi to ALL_LINGUAS in /configure.in, added that info to the /ChangeLog, then tried to commit my changes in /. svn: 'pre-commit' hook failed with error output: A valid MAINTAINERS file is required. See http://live.gnome.org/MaintainersCorner#maintainers (47-1) I don't know what's wrong with MAINTAINERS (it only contains Christian's name and email), but I need to report it, because it meant I couldn't commit my changes, so vi has not been added to ALL_LINGUAS in configure.in. Christian, since I can't do that, could you please add vi for me? Otherwise, our translation will not be used. (This email is also sent to gnome-i18n in case anyone else strikes the same problem, and so they know it's already been reported.) Thankyou. from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Add translation contexts
To: GNOME-i18n
Cc: TP list
On 20/09/2007, at 3:16 PM, Sven Neumann wrote:
I want to patch Balsa to add context informations but the strings are
used in a initializer so the macro Q_ is not appropriated:
Index: libbalsa/source-viewer.c
===
--- libbalsa/source-viewer.c(révision 7714)
+++ libbalsa/source-viewer.c(copie de travail)
@@ -40,9 +40,12 @@
/* Normal items */
static GtkActionEntry entries[] = {
/* Top level */
-{FileMenu, NULL, N_(_File)},
-{EditMenu, NULL, N_(_Edit)},
-{ViewMenu, NULL, N_(_View)},
+/* This is the text that should appear on a menu title.
+ * Don't include the prefix 'menu title|' in the translation.
+ */
+{FileMenu, NULL, Q_(menu title|_File)},
+{EditMenu, NULL, Q_(menu title|_Edit)},
+{ViewMenu, NULL, Q_(menu title|_View)},
/* Items */
{Close, GTK_STOCK_CLOSE, N_(_Close), controlW,
N_(Close the window), G_CALLBACK(close_cb)},
Does anyone have a solution?
__
The solution is to add context and to use N_() in the initializer.
Then,
in the code where gettext() is currently used to translate the struct
entry, this code needs to be changed to use g_strip_context().
Here's an
example from the GIMP source code for translating a GtkActionEntry
label:
label = g_strip_context (entries[i].label, gettext (entries
[i].label));
Is this adding context in the string headers (deprecated), or using
the new msgctxt feature from gettext (recommended)?
If you're using msgctxt, it should work. If not, the gettext devs.
can advise. :)
from Clytie
Vietnamese Free Software Translation Team
http://vnoss.net/dokuwiki/doku.php?id=projects:l10n
PGP.sig
Description: This is a digitally signed message part
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: add Vinagre to GTP
On 15/09/2007, at 3:29 AM, Claude Paroz wrote: Le vendredi 14 septembre 2007 à 14:35 -0300, Jonh Wendell a écrit : Hi, folks. What needs to be done in order to get Vinagre[1] into GTP? First, you need to buy 10 huge ice creams to vuntz. Then you'll may be lucky enough to get what you want... And lots of chocolate for the GTP translators. :D from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Argh.. Novell people imports external translations again
On 16/09/2007, at 10:37 AM, Jorge González González wrote: El dom, 16-09-2007 a las 00:26 +0200, Vincent Untz escribió: I've reverted all the po files to revision 338 (ie, before this commit), except for gl, pt_BR and sv which were already reverted. At first I thought the Spanish translation was ok, now I know it is not. Besides, I don't know why he had to remove my name from the header? And obviously overwrite some of our vocabulary with other deprecated. I'm sure Jimmy didn't want to create a problem here, and probably didn't know that it shouldn't be done like this. Now he knows :-) Hi did, a big one :-p This is very similar to the Ubuntu situation, where our translations are overwritten in Rosetta on Launchpad. I don't remember if we achieved any resolution on that. Did we? If so, perhaps we can apply the same policy to all external edits of GTP files. If not, we need a policy, and we need to publicize it. Part of the policy should be that all edits go through the GTP language team concerned: of course we welcome participation, but the GTP language team is responsible for QA. QA (Quality Assurance) for i18n includes: • maintaining correct and consistent vocabulary • assigning translators to specific files • maintaining copyright statements • maintaining a correct list of previous and current translators • reviewing translations • managing bug reports Anyone is welcome to participate in translation, as long as they work within the GTP QA framework. Otherwise, perhaps they want to take on the QA responsibility, and we can all put our feet up and have icecream and chocolate. ;) from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: xkeyboard-config 1.1 is looking for updated translations
On 13/09/2007, at 3:09 AM, Sergey Udaltsov wrote: Actually, you are right. I am just not sure what would be easiest way to do so. But I'll think of it. It seems the only way is manual scripting. Also, I am not sure about legal consequences. ISO codes is LGPL as far as I can see. Could I use it with X11-licensed xklavier-config? Ask the iso-code maintainers: they're good people: [EMAIL PROTECTED] Sergey On 9/12/07, Andre Klapper [EMAIL PROTECTED] wrote: Am Dienstag, den 11.09.2007, 22:25 +0100 schrieb Sergey Udaltsov: The xkeyboard-config project is about to make a release (1.1) in two weeks time (25.09). I would be grateful for fresh translations for its pot file: http://webcvs.freedesktop.org/xlibs/xkbdesc/po/xkeyboard- config.pot?revision=1.6 http://webcvs.freedesktop.org/xlibs/xkbdesc/xkeyboard-config/po/ xkeyboard-config.pot?revision=1.6 i took a quick look at it and many language and country name strings are already covered by the iso-codes package. it would probably shrinken the pot file size and save a lot of translators' time to grab those strings from the iso-codes package instead, if possible. (and no, it's not only xkeyboard-config that could use iso-codes for this, evolution and gnome's gweather applet aren't any better in this.) andre -- mailto:[EMAIL PROTECTED] | failed http://www.iomc.de/ ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Unreadable strings in evolution
On 09/09/2007, at 10:32 PM, Kenneth Nielsen wrote: 2007/9/9, Manuel Borchers [EMAIL PROTECTED]: Hi Kenneth, Am Sonntag, den 09.09.2007, 13:47 +0200 schrieb Kenneth Nielsen: #: ../ui/evolution-mail-message.xml.h:89 msgid Search Folder from Sen_der... I think here is meant the functionality search folder. Those are the special folders below your normal folders that will find messages in (all or a selection of) your normal folders meeting special criteria and collect those in the search folders. from Sender would mean creating a new folder using the sender information (I guess it's used in a context menu when right-clicking on a message in your normal folders). Kenneth then wrote: Thanks Manuel Ah yes, I knew about the search folders but didn't find strings before now. They are used in a right-click menu saying Create rule from message and the submenu Search folder from subject. I still don't think it is good English but maybe it can be defended because it needs to be kept short for the menus. Still, based on subject isn't much longer than from subject, and is much easier to understand. What do you think? from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translating the GNOME 2.20 release notes
Can we please have the release-notes on Damned Lies, so we can monitor changes? from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translating the GNOME 2.20 release notes
Another q. about the Release Notes... Since I've translated them before, I'm not sure if the screenshots in the docbook/vi/figures directory are the old ones, or if they are ones added by default for this release. If they're old ones, I could remove them, and, hopefully, get some new ones instead. ;) (For some reason, viewcvs isn't displaying any info except filenames for me, and of course the dates on the files in the directory I've checked out today all say Today...) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GOffice and LINGUAS
On 07/09/2007, at 12:10 AM, Claude Paroz wrote: Le jeudi 06 septembre 2007 à 23:29 +0930, Clytie Siddall a écrit : Hi everyone :) I've just updated GOffice (which seems to be bits and pieces of other files), but I noticed that Damned Lies warned Entry for this language is not present in ALL_LINGUAS in configure file. So, after translating the file, I looked for ALL_LINGUAS. In configure.in (at the root level of the package), it said: ___ AC_SUBST(ALL_LINGUAS, am az bg ca cs da de el en_CA en_GB es et fi fr ga gl he hr hu it ja ko lv ml mr ms nb nl nn oc pl pt pt_BR ro ru sk sr [EMAIL PROTECTED] sv tr uk vi zh_CN zh_TW) ___ So my language (vi) _is_ there. Is Damned Lies confused, or is there something wrong with the substitution above? Hi Clytie, See http://bugzilla.gnome.org/show_bug.cgi?id=474037 Thanks, Claude. I've added my problem. So everyone should be using LINGUAS, huh? I'll add that to my running campaigns on typos (I think I've nearly eliminated occured in GNOME), filling in the Report-Msgid-Bugs-To header, and the use of the iso-codes package to avoid us retranslating LONG (and usually inaccurate) lists of languages, currencies and country names. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translating the GNOME 2.20 release notes
On 07/09/2007, at 12:12 AM, Daniel Nylander wrote: I'm also trying to remember how to check the release notes out. I think they're in gnomeweb-wml, but I can't find them via viewcvs: I seem to go around in circles in there. Here are they: svn.gnome.org/svn/gnomeweb-wml/trunk/www.gnome.org/start/2.20 Thanks, Daniel. :) Not an easy location to remember, at least for me. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
GOffice and LINGUAS
Hi everyone :) I've just updated GOffice (which seems to be bits and pieces of other files), but I noticed that Damned Lies warned Entry for this language is not present in ALL_LINGUAS in configure file. So, after translating the file, I looked for ALL_LINGUAS. In configure.in (at the root level of the package), it said: ___ AC_SUBST(ALL_LINGUAS, am az bg ca cs da de el en_CA en_GB es et fi fr ga gl he hr hu it ja ko lv ml mr ms nb nl nn oc pl pt pt_BR ro ru sk sr [EMAIL PROTECTED] sv tr uk vi zh_CN zh_TW) ___ So my language (vi) _is_ there. Is Damned Lies confused, or is there something wrong with the substitution above? Thankyou for any help you can offer with this. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translating the GNOME 2.20 release notes
On 05/09/2007, at 10:30 PM, Og Maciel wrote: On 9/5/07, Clytie Siddall [EMAIL PROTECTED] wrote: I've forgotten [1] where to find the Release Notes. Are they on Damned Lies yet? Hey Clytie, Here's the direct link: http://l10n.gnome.org/module/release-notes Have fun! :) Thanks, Og. :) I'm also trying to remember how to check the release notes out. I think they're in gnomeweb-wml, but I can't find them via viewcvs: I seem to go around in circles in there. I really don't want to have to check out the whole module if I can just grab the section for the release notes. Thanks for your help. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translating the GNOME 2.20 release notes
Hi everyone :) I've forgotten [1] where to find the Release Notes. Are they on Damned Lies yet? Thankyou for your help. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN [1] Too many projects, too little brain! PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Strange abbreviation in Dasher
On 02/09/2007, at 12:13 PM, Tirumurti Vasudevan wrote: On 9/1/07, Behdad Esfahbod [EMAIL PROTECTED] wrote: Prediction by Partial Matching. That's exactly what Dasher does. of course it does just that. i totally agree with you. Standard letter-based PPM makes sense here. It does make sense, but it's not necessarily an abbreviation we're all going to know. I wish I had known it, but I didn't. So we do need the Dasher developers to start adding contextual information. If nobody else reports this as a bug, I'll try to do so (I'm a bit short of time at the moment). from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Strange abbreviation in Dasher
On 01/09/2007, at 5:06 PM, Alexander Shopov wrote: What does PPM stand for in Dasher? http://bugzilla.gnome.org/show_bug.cgi?id=472454 It's a unit for printing speed: Pages Per Minute You'll see it on printer advertizements, although often in lower case. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Strange abbreviation in Dasher
On 01/09/2007, at 9:36 PM, Claude Paroz wrote: Le samedi 01 septembre 2007 à 16:32 +0530, Tirumurti Vasudevan a écrit : Perhaps this one: The name PPM is an acronym derived from Portable Pixel Map. http://netpbm.sourceforge.net/doc/ppm.html tv There may be a bunch of interprations: http://en.wikipedia.org/wiki/PPM :-) Yes, the PPM string I found in dasher was about printing speed, so Pages Per Minute seemed the most likely explanation. However, it's a popular acronym. ;) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Strange abbreviation in Dasher
On 01/09/2007, at 11:22 PM, Tirumurti Vasudevan wrote: On 9/1/07, Clytie Siddall [EMAIL PROTECTED] wrote: Yes, the PPM string I found in dasher was about printing speed, so Pages Per Minute seemed the most likely explanation. However, it's a popular acronym. ;) the entire dasher application seems to be rather about fonts screen display etc. i dont think it has anything to do with printing. the relevant line in the file msgid 67: #: ../Data/glade/dasher.compose.glade.h:67 #: ../Data/glade/dasher.direct.glade.h:57 #: ../Data/glade/dasher.fullscreen.glade.h:55 #: ../Data/glade/dasher.traditional.glade.h:71 #: ../Data/glade/dashermaemo.glade.h:30 #: ../Data/glade/dashermaemofullscreen.glade.h:27 msgid Standard letter-based PPM can you think of anyway pages per minute applies here? I think I was looking at a different string, but in any case, yes, that makes sense to me. Printing has a letter size, so to me, that says Print based on the standard number of pages per minute with the letter size. This certainly shows how people can interpret the same text differently. ;) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Status page: reporting errors
On 04/07/2007, at 6:08 AM, Claude Paroz wrote: Le mardi 03 juillet 2007 à 23:07 +0930, Clytie Siddall a écrit : On 03/07/2007, at 2:10 AM, Claude Paroz wrote: Le lundi 02 juillet 2007 à 14:26 +0930, Clytie Siddall a écrit : Hi everyone :) The Gnumeric module on our status page has a whole slew of alert icons for both files, about missing files in POTFILES, not being able to access the current POT file, and (relevant to the translator) the warning that our language is not present in ALL_LINGUAS for this module. However, I checked. vi _is_ present and correct in ALL_LINGUAS in the configure.in file. Do I report this error against Gnumeric, or against Damned Lies? Hi Clytie, The problem here is that Damned Lies doesn't recompute the .po file if it hasn't changed. So the errors aren't checked either. This is a current flaw in Damned Lies... contributors are welcome :-) Thanks for explaining, Claude. :) Just for Clytie :-) :)) I tried to make Damned Lies to always recompute po file when it contains errors. Let's see if tomorrow, after running the daily update script, the warnings will have disappeared. Gnumeric was a special problem, and I extended the search for the ALL_LINGUAS variable in the configure.in file (non standard). Thankyou very much! The warnings about vi not being in ALL_LINGUAS have now disappeared. The one about not being able to find the POT for gnumeric-functions is still there, but that translation didn't need updating, and in any case I don't know if there's anything I can do about that type of error. Thanks for the help, Claude. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: updated translation in Gnome_2.20_ko
On 03/07/2007, at 4:47 PM, Eun Ju Kim wrote: Dear Mr. Changwoo Ryu Hello Mr. Ryu, my name is Eun-Ju Kim and I am working as a Korean translator in Red Hat. Actually I've sent emails several times few weeks ago to participate in GNOME translation work but I couldn't get any reply from you yet. When you've got this mail please please reply me. ... I am sure you will get your reply from the Korean language team at GNOME. Best Regards, Eun-Ju Kim Technical Translator Red Hat APAC Level 2, 5 Gardner Close, Milton QLD. 4064 Australia Phone: +61 7 3514 8104 Mail: [EMAIL PROTECTED] I'm writing this to welcome another Australian to GNOME! I live in Renmark, South Australia. Oso oseyo, Eun-Ju. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Status page: reporting errors
On 03/07/2007, at 2:10 AM, Claude Paroz wrote: Le lundi 02 juillet 2007 à 14:26 +0930, Clytie Siddall a écrit : Hi everyone :) The Gnumeric module on our status page has a whole slew of alert icons for both files, about missing files in POTFILES, not being able to access the current POT file, and (relevant to the translator) the warning that our language is not present in ALL_LINGUAS for this module. However, I checked. vi _is_ present and correct in ALL_LINGUAS in the configure.in file. Do I report this error against Gnumeric, or against Damned Lies? Hi Clytie, The problem here is that Damned Lies doesn't recompute the .po file if it hasn't changed. So the errors aren't checked either. This is a current flaw in Damned Lies... contributors are welcome :-) Thanks for explaining, Claude. :) I wish I could help, but I don't have that capacity any more. Luckily, the English-Vietnamese switch still works in my head. ;) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Status pages: where are the other modules?
Hi everyone :) I've recently returned to i18n after several months unable to participate, so sorry if this is a dumb q. The new status pages are great: a major improvement in several ways. :) However, where is the status data for the other modules, the ones which aren't necessarily part of the GNOME Desktop? Empathy, mentioned recently on this list, is an example, but I remember there was quite a long list of other modules still requiring translation. Is there a correspondingly cool status page for these external modules? :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Where is DOC_LINGUAS?
Hi everyone :) I also can't remember where DOC_LINGUAS is hiding within a module. I do remember we have to add our languages to this file when we add a docs translation, but I can't find it, for example, in gnome-desktop/ desktop-docs or gnome-control-center. LINGUAS is in the /po dir. But DOC_LINGUAS isn't in the /docs or / help dirs. Where is it hiding itself? Please remind me. Thankyou. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Where is DOC_LINGUAS?
On 28/06/2007, at 10:46 PM, Claude Paroz wrote: Le jeudi 28 juin 2007 à 22:33 +0930, Clytie Siddall a écrit : Hi everyone :) I also can't remember where DOC_LINGUAS is hiding within a module. I do remember we have to add our languages to this file when we add a docs translation, but I can't find it, for example, in gnome-desktop/ desktop-docs or gnome-control-center. LINGUAS is in the /po dir. But DOC_LINGUAS isn't in the /docs or / help dirs. Where is it hiding itself? Please remind me. Thankyou. :) For docs translation, DOC_LINGUAS is a variable in the Makefile.am in the help directory. Thanks, Claude. No wonder I couldn't find a separate file! ;) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
POTFILES errors on status pages
Hi everyone :) Another status page query. ;) The warning icons on the l10n status pages about files missing or incorrect in POTFILES puzzle me. There's nothing I, as a translator, can do to fix that problem. So should those warnings be displayed on our l10n status pages at all? Is there a reason why they are shown to us? [1] Do you want us to gang up on the developers and throw rotten tomatoes at them until they fix the problem? :D from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN [1] Warning: Extremely Silly Suggestion. PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Status pages: where are the other modules?
Thanks to Claude, Jorge and Danilo for helping me with this. :) On 29/06/2007, at 12:22 AM, Danilo Šegan wrote: The new status pages are great: a major improvement in several ways. :) Thanks: by now, they have also received some important improvements by Claude Paroz as well, who's also been doing major work with keeping branch information up to date. The status pages are definitely hot. I hope other projects start using something like this. However, where is the status data for the other modules, the ones which aren't necessarily part of the GNOME Desktop? Empathy, mentioned recently on this list, is an example, but I remember there was quite a long list of other modules still requiring translation. If you start at the start page, you can follow the 'Modules' (or in Vietnamese once you translate damned-lies[1]) Ooh, we can translate the interface? Cool. :D link from there to get to http://l10n.gnome.org/module Empathy is listed there, but without stats: to see stats, check it up on http://l10n.gnome.org/module/empathy. However, most of those modules are also inside one of the releases: http://l10n.gnome.org/releases/ Empathy, for instance, is inside Gnome Extras: http://l10n.gnome.org/languages/vi/gnome-extras Is there a correspondingly cool status page for these external modules? :) Just start on l10n.gnome.org, and you can discover it all: wherever it's not clear enough, just file a bug, and lets figure out a way to make it better. Somehow, I managed to look _all around_ the main page, but still didn't find it. I think that's probably a bug in my head, not in the layout, though. ;) [1]http://l10n.gnome.org/module/damned-lies starts sharpening pencils from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Wolof team waiting for response
To: gnome-i18n CC: Christian, Danilo, MMM Hi :) Back in October/November 2006, Mouhamadou Mamoune Mbacke wrote to this list, asking to form a team for the Wolof language. I wrote an email supporting this aim, since I know him from the Debian i18n project. Please see a copy of that mail below. [1] Unfortunately, nobody replied to his or my mail. Mamoune Mbacke still wants to form a Wolof team, and plans to write again to the list. Please respond to his email. Thankyou. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ [1] Hello everyone :) I'd like to introduce Mouhamadou Mamoune Mbacke, who has created the Wolof locale and a complete translation of the Debian Installer for Wolof. This is the first continental African translation we have had in Debian, and since the resources available to African translators are notoriously low, it testifies to Mouhamadou Mamoune's sustained effort and ability. Now he's worked his way through the Debian Installer, which desktop does this ground-breaking localizer choose for his community? GNOME, of course. ;) I've given him the basic info about the project, the link to the GTP wiki page, mailing list etc., and he will be appearing here soon. No doubt he will have more questions. ;) Congratulations to GNOME on this new language, and welcome (Salam alaikum) to Mouhamadou Mamoune! from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Where is DOC_LINGUAS ?
On 07/01/2007, at 6:23 AM, Danilo Šegan wrote: Hi Clytie, Yesterday at 5:27, Clytie Siddall wrote: The new status pages have brought to my notice the fact that our GPL and LGPL unofficial translations aren't in DOC_LINGUAS. However, I can't find this file in gnome-desktop. Where do I find it? It's not a file, it's a variable used inside Makefile.am: http://svn.gnome.org/viewcvs/gnome-desktop/branches/gnome-2-16/ desktop-docs/lgpl/Makefile.am?view=markup Thanks, Danilo. I thought we were moving to LINGUAS files. Are we doing that? from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
LGPL translation missing
Hi everyone :) I went to update the DOC_LINGUAS line in makefile.am for my GPL and LGLP unofficial translations in gnome-desktop, and the GPL one was there, but the LGPL translation is missing. No vi directory, no po file. Yet I have submitted it, and it shows up on p.g.o. Do I need to create the dir and submit the file again? from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Progress pages not updating, and when 100% isn't
Hi everyone :) I've started updating my files from SVN, and when I logged on yesterday, all my commits from the day before were showing on progress.gnome.org. Then I did a stack more updates and committed them. However, when I logged on today, none of those commits were showing on p.g.o. Is it not updating for some reason? I have a second question about p.g.o. When I checked to see which files needed updating, I was pleased to see Gnome desktop. (100% translated). But when I looked further down, it wasn't 100% at all. There were quite a lot of untranslated and fuzzy strings in different files. Are the stats wrong, or is it simply that they don't show decimal quantities? I think we really need to know when 100% isn't 100%. Otherwise, we might miss doing updates that are needed. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
SVN structure (NetworkManager)
Hi everyone :) I've started updating files via SVN, and it works really well. However, I'm a little confused over a couple of things. 1. The web interface: we don't have a ViewSVN. We still have a ViewCVS operating, strangely enough, on svn.gnome.org. Is it really viewing our old CVS, or our new SVN repo? 2. How do I check out the NetworkManager files? Going by the filename on progress.gnome.org, I tried: svn co svn+ssh://[EMAIL PROTECTED]/svn/NetworkManager-openvpn/ trunk NetworkManager-openvpn but the server didn't recognize that as a module name. ViewCVS shows NetworkManager as a parent directory, but I can't find openvpn inside it. Thankyou for any help you can offer with this. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Progress, errors and warnings
On 03/01/2007, at 10:54 PM, Erdal Ronahi wrote: On 1/3/07, Travis Watkins [EMAIL PROTECTED] wrote: In Epiphany the tooltips are wrapped rather nicely. I dunno if this is something epiphany does or something that has already been changed. In Internet Explorer it is fine, too ;) So it's a firefox problem. Wraps perfectly in Omniweb [1], too. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN [1] Mac OSX-only browser PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: I did like the old progress pages better, you know...
On 05/01/2007, at 3:00 AM, Alexander Shopov wrote: Happy new year and to many new years for all those using the Gregorian calendar. For the rest - sorry - the world discriminates against you ;-) Dreadful, isn't it? ;) Anyway - the new progress pages are definitely funkier, have more information but I find them more difficult to use. Maybe it is my age showing, maybe the typographic fatigue, but still... It does take a while to adjust to changes like this. I really liked the tabular layout - without any indents to show dependencies and similar, I liked the lines around the boxes - it just makes things easier to read. I find this layout very easy to read, and I do have reading difficulties now. The basic design of the page is sound. Including the stats for the documentation is a good thing (we definitely missed that) but having the info on both docs and UI on a single page is kind of superfluous for me (in my workflow I either commit UI or docs, very seldom both). I think it's really useful having them both on one page. For one thing, it will shame me into doing some more doc translations. ;) Could we have the tabular view back please? And perhaps the font could be smaller so we can crank more info in a view? You can set the font size in your browser. You can also specify CSS to show the table with borders. There's quite a lot you can do to customize the way these new pages look in your own browser. This is not to say that your opinion is not valid, Alexander. But I do think these new pages are better, and you do have the option to change the way they display. I suppose if everybody, or most people, said they had difficulty with these pages, we would have to change them, but they do seem to work very well. The faster update after commits will alone be worth the change, IMHO. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Where is DOC_LINGUAS ?
Hi everyone :) The new status pages have brought to my notice the fact that our GPL and LGPL unofficial translations aren't in DOC_LINGUAS. However, I can't find this file in gnome-desktop. Where do I find it? Thankyou for your help with this. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Progress pages (generic server error on Releases)
Thanks for your reply, Danilo. :) On 02/01/2007, at 9:26 PM, Danilo Šegan wrote: Today at 5:03, Clytie Siddall wrote: 1. Can we have the team-leader details in UTF8? Vietnamese names have the wrong meaning without diacritics. Sure: I'll be adding some stuff to enable such changes by coordinators themselves, but for now, you can submit them to me directly. I copy-pasted stuff from your wiki page, so check that the name is correct. Perfect! Thanks very much. :)) 2. The mailing list link for our team is null. The correct address is [EMAIL PROTECTED]. Thanks, will be fixed. Thankyou. 3. Quite a few files have warning icons saying they are not UTF8. They all have headers specifying UTF8, and were all UTF8-encoded when they left my machine. How do I fix this? I'll need to fix that check: the only problem with those files is that they use 'utf-8' (lowercase) as the encoding, and msgconv -t UTF-8 normalizes that to 'utf-8'. So far, the check I am doing is simply: msgconv -t UTF-8 vi.po | diff -u - vi.po I hadn't really noticed the difference in the headers, but I think it's a difference that's likely to occur, so we need tools to handle it, if it's not a major hassle. 4. Can we add our wiki page to the team page listed? http:// live.gnome.org/GnomeVi Sure, though I plan to enable all these changes using web interface in the near future. Great! This is like the kind of project page I've suggested for Pootle: a focus page which gives you the basic info, including contact info, you need about a project. These pages are a terrific improvement: thankyou very much for all your work. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Progress pages (generic server error on Releases)
Hi Danilo, thanks for responding so promptly and helpfully. :) On 02/01/2007, at 9:48 AM, Danilo Šegan wrote: Today at 5:59, Clytie Siddall wrote: I got a generic server error when choosing Releases. Fixed: the problem was with +x being preserved with SVN, whereas the old file in CVS didn't keep the executable bit on. Now the bit is added to SVN, so there should be no problems anymore. Great. :D Display by module is very useful when you want that POV, but display by release sets is better from the overall translation status POV, so we need this to work before we can switch over effectively. Actually, I think the 'Language' views would be even better suited for translators right now: http://progress.gnome.org/languages/vi http://progress.gnome.org/languages/vi/gnome-2-18 You're quite right: I couldn't see them yesterday, so I didn't know what they were like! These pages really do simplify things for us: combining the UI and doc files, with quite a bit of metadata, and only two tabs to keep open instead of half a dozen! A few queries: 1. Can we have the team-leader details in UTF8? Vietnamese names have the wrong meaning without diacritics. 2. The mailing list link for our team is null. The correct address is [EMAIL PROTECTED]. 3. Quite a few files have warning icons saying they are not UTF8. They all have headers specifying UTF8, and were all UTF8-encoded when they left my machine. How do I fix this? 4. Can we add our wiki page to the team page listed? http:// live.gnome.org/GnomeVi Thanks for your help with this. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Migration to subversion
On 02/01/2007, at 10:25 AM, Wouter Bolsterlee wrote: Use ssh-agent (you're probably running it already, since most distros include it by default in your XSession) and add your SSH key to it by using ssh-add. Then type your passphrase. Subsequent ssh invocations will not ask you for a password anymore. If you want to automate some of the above, see my blog entries at [1] and [2] for more information. mvrgr, Wouter [1] http://uwstopia.nl/blog/2006/08/password-hell-gdm-ssh-gnome- keyring [2] http://uwstopia.nl/blog/2006/08/password-hell-part-ii For OSX users, as GUI frontends to ssh-add, ssh-agent and the usual CLI suspects, these can be handy: SSHAgent: http://www.phil.uu.nl/~xges/ssh/ SSHKeychain: http://www.sshkeychain.org/ SSH Tunnel Manager: http://projects.tynsoe.org/en/stm/download.php I run these in the background, and SSH checkouts etc., even those via a tunnel like OpenOffice.org, are a single command. BTW, Ross, since we all need to checkout new working copies, do you want us to space it out in some way, or is a combined mad rush on the SVN server OK? from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Error in progress pages
Hi guys :)
I really like the progress pages, and I'm happy to switch to using them.
I got an error today when I chose Languages/Vietnamese:
___
AttributeError
Python 2.4.3: /usr/bin/python
Mon Jan 1 04:54:07 2007
A problem occurred in a Python script. Here is the sequence of
function calls leading up to the error, in the order they occurred.
/var/www/damned-lies/teams.py
176 langid = test.groups()[0]
177 release = test.groups()[2]
178 (t_rel, t_ext) = os.path.splitext(release)
179 if t_ext == '.xml':
180 release = t_rel
t_rel undefined, t_ext undefined, os = module 'os' from '/usr/lib/
python2.4/os.pyc', os.path = module 'posixpath' from '/usr/lib/
python2.4/posixpath.pyc', os.path.splitext = function splitext,
release = None
/usr/lib/python2.4/posixpath.py in splitext(p=None)
90 Split the extension from a pathname. Extension is
everything from the
91 last dot to the end. Returns (root, ext), either part
may be empty.
92 i = p.rfind('.')
93 if i=p.rfind('/'):
94 return p, ''
i undefined, p = None, p.rfind undefined
AttributeError: 'NoneType' object has no attribute 'rfind'
args = ('NoneType' object has no attribute 'rfind',)
___
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm
Việt hóa phần mềm tự do)
http://groups-beta.google.com/group/vi-VN
PGP.sig
Description: This is a digitally signed message part
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Progress pages (generic server error on Releases)
Hi again :) I got a generic server error when choosing Releases. Display by module is very useful when you want that POV, but display by release sets is better from the overall translation status POV, so we need this to work before we can switch over effectively. ___ Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, [EMAIL PROTECTED] and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. ___ from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Damned Lies about desktop-docs?
On 31/12/2006, at 2:40 PM, Leonardo Fontenelle wrote: l10n-status had PO files for desktop-gpl, lgpl and fdl. I can't find them in progress-g-o, i. e. inside gnome-desktop. Where are they? BTW I'm creating a who's working on what page for the pt_BR list with links to p-g-o. I never felt so happy about knowing regular expressions :) The address is: http://live.gnome.org/GnomeBR/Traducao/TradutoresTrabalhando This is a really useful page, Leonardo. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GNOME subversion migration
On 18/12/2006, at 11:05 PM, Ross Golder wrote: Sorry, I sent this to gnome-hackers, but I should have sent this here too... I'm happy with the latest test results and would like to propose a new migration cut-off date: Friday December 29th 2006 at 23:59UTC. snip details Yay! It's finally happening! I don't mind CVS, but SVN is a much better tool. Thanks for the Christmas and New Year present, Ross! from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Verbs form in UI actions
On 18/12/2006, at 3:01 AM, Youssef Chahibi wrote: In what form (Infinitive, Noun, Imperative) are UI actions like Open, Close, Show ... translated in your language? Do you have any idea about what is intended by the verb form in English, is Imperative or infinitive? Imperative. But it really doesn't make much difference in my language. Verbs don't reflect case: in some situations, we add a temporal participle (more often a temporal adverb elsewhere in the statement), but context is best expressed in my language by the use of pronouns, for which gettext does not provide at all. If I ever get our first OOo release sorted out, Youssef, I'll be able to get on with the glossary work. How's it going from your end? from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: New Team for Tigrinya tir
On 10/12/2006, at 9:36 PM, Negacy Degefu wrote: Full Name: Negacy Degefu mail: [EMAIL PROTECTED] or [EMAIL PROTECTED] Bugzilla account : [EMAIL PROTECTED] English name: Tigrinya Native(UTF-8-coded) name: ትግር ኛ We want to create a new team for traslating Gnome into Tigrinya specifically spoken in Tigrai, Ethiopia. Anybody is welcome. Enqai dehan mesakum. :) (Welcome!) Negacy, welcome to GNOME! :) If you look at the list of GNOME language teams: http://developer.gnome.org/projects/gtp/teams.html which is linked from the GNOME Translation Project wiki page: http://live.gnome.org/TranslationProject it shows we already have a Tigrinya team. I'm sure they will be happy to hear from you. Please contact Simon Mebrahtu about contributing to GNOME. If, for some reason, you can't contact him, please tell us. We value your efforts and ideas, and welcome you to our project. Please ask any further questions here. Good luck with your work here at GNOME! :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: What happens to translations through Launchpad? (Arabic Gnome related)
On 09/12/2006, at 8:00 AM, Leonardo Fontenelle wrote: 2006/12/7, Clytie Siddall [EMAIL PROTECTED]: At least one team (Portuguese?) is working to close the gap between Rosetta and this project. Ideally, the Rosetta and upstream translators need to work together. But a lot of change yet needs to occur to achieve this. The pt_BR GNOME and Ubuntu teams made an agreement; basically, Ubuntu translators would help us translating GNOME (without Rosetta) and then would get this downstream to Rosetta. We (G+U) are probably going to assign translators to package (every package must have some responsibles), which is the Ubuntu-l10n-pt_BR way. Thanks for that info, Leonardo. :) Your decision makes sense: focus the effort at the source of the data, then shift it to distribution. Assigning translators per package isn't a bad system: it gives people responsibility and a feeling of identity with software they translate. As long as all the completed files still go through QA, it should work OK. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Glade user manual
On 09/12/2006, at 8:32 AM, Vincent Geddes wrote: We have added a GNOME user manual to Glade (cvs module: glade3), just to let you people know. Using gnome-doc-utils? :) I ask, because you're much more likely to get translations if the files are available in PO format. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: What happens to translations through Launchpad? (Arabic Gnome related)
On 02/12/2006, at 6:53 AM, Wouter Bolsterlee wrote: 2006-12-01 klockan 17:45 skrev Djihed Afifi: What happens to the translations made through launchpad? do they get merged back to Gnome? is ubuntu the only distribution that will benefit from them? will our work make it to ubuntu packages? https://launchpad.net/bugs/68014 might be worth subscribing too. It's a fairly complex situation, Djihed. :( Launchpad (including Rosetta) works for Ubuntu. Work done there will appear in Ubuntu, but so far, none of it gets sent back upstream to the project responsible for those files. You can imagine what a bad situation this can be. Conflicting files. Lack of QA. Data out-of-date. Our work here at GNOME, like any translation work in the original project, gets distributed with the product (e.g. GNOME 2.14, GNOME 2.16). So when Ubuntu integrates a version of GNOME, they get our work, too. :) Unfortunately, they can give priority to alterations made in Rosetta. This can result in us receiving bug reports for work not done by us. At least one team (Portuguese?) is working to close the gap between Rosetta and this project. Ideally, the Rosetta and upstream translators need to work together. But a lot of change yet needs to occur to achieve this. One of the biggest obstacles I can see to this being effective, is that Rosetta does not have the immediate access to our latest files that we do have here. I did some work in Rosetta quite a while ago, and ended up wasting many hours on an old version of a file. It was the latest version in Rosetta, but it was several versions old in the upstream project. So there are quite a few issues to be resolved. Possibly one of the biggest is the differing priorities: we here at GNOME are working for all our users, while Ubuntu is working for Ubuntu only. I hope that can be overcome. If we integrate the Pootle [1] online distributed translation tool, as Debian is currently doing, we can customize the tool to suit our project. It is an upstream project tool, by design. It is capable of syncing with our SVN/CVS, runs online or offline, or both, and is generally very flexible. It's gives us another translator tool, which we can choose to use, or not use, in the degree that suits each of us. Anyone can run a Pootle, and it's free software. I'd like to see Rosetta more suited to the aims of free-software upstream translation. Hopefully, through the bug that Wouter quoted, change can happen. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN [1] http://pootle.wordforge.org/ http://translate.sourceforge.net/wiki/pootle PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
gettext plurals errors (was: Re: possible bug in gtk+/po/hy.po
On 03/12/2006, at 10:22 AM, Andre Klapper wrote: Am Samstag, den 02.12.2006, 23:22 +0100 schrieb Christian Rose: On 11/28/06, David Loyall [EMAIL PROTECTED] wrote: Thanks for your report. However, in order to make sure that the correct translators can have a look at this, please also file a proper bug report in our bug tracker at http://bugzilla.gnome.org/. this issue has been reported already: http://bugzilla.gnome.org/show_bug.cgi?id=377204 it's fixed in HEAD, but not in the gnome-2-10 branch. gettext-0.15 and later reports an error when there are any empty plurals fields, or when the number of plurals fields (empty or complete) doesn't match the plurals header of the PO file. I've found this very handy in eliminating spurious plurals fields in our files, but it can also result in errors being reported where they weren't before, which can be confusing. If the plurals header is: Plural-Forms: nplurals=1; plural=0;\n (no plurals), as in my language and many others, then simply deleting any msgstr[1] fields from the PO file can eliminate this type of error. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Gnome Translation group joining
On 03/12/2006, at 6:16 AM, Herli Joaquim de Menezes wrote: Hi, I want to join in GTP. How can i do it? Im brazilian and I wish to work as volunteer in translating from english to portuguese. Herli, welcome to GNOME! Please see our wiki page [1], and read the docs there. You need to get in touch with your language-team leader (see the list of language-teams, link from wiki page), and ask for some work. There is always plenty to do! Good luck with your translations. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN [1] http://live.gnome.org/TranslationProject#preview PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Hausa Language Translation Project..
Mustapha, welcome to GNOME! :) On 01/12/2006, at 10:49 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Good morning, I am an author and also an entity relation officer working with a software company in northern Nigeria. I have seen the language i.e. HAUSA LANGUAGE that we want to contribute perfectly on, but the problem is that, we are mailing the group leader of the LANGUAGE TEAM for the past five months,a language speaking widely in west Africa, but we didn’t received any response from him, we want to contribute to humanity and time is going. We have a procedure for dealing with broken contacts, so thankyou for notifying us. Our coordinator will advise you on what will happen next. Five months is a long time: anyone who can't get in touch with their language team for more than a month (? two weeks?) should probably report it here. Communication is essential in maintaining a project like this. That's why it's often useful to nominate a backup contact- person for your language team, and include such extra contact information on your team webpage. HAUSA Language ISO 639-2 hau, ISO 639-1 ha, English lang. name hausa, French lang. name haoussa. Please add your plurals header to the Plurals page [1] in the Translate Wiki. This is a central resource for translators. We are using GNOME as our GUI and also we have read your documentation hand book and several materials that will help us through the translation work. Great work! If you haven't read all the information on our wiki page [2], please also use that as reference material. We will be very grateful we would have access to the cvs There is information on our wiki page about applying for CVS access. There is quite a waiting list at present, so please apply as soon as possible. Meanwhile, even while waiting for contact to be established with your language-team, you can probably start work on some files. I notice that your language doesn't have separate status pages [3] yet, but you can check out modules anonymously and work on the POT files, or download the files from the English pages, and start working on them, if you like. It is important to have your files reviewed before submitting them. Once you have completed, checked and reviewed files, even before you have CVS access, they can still be uploaded by volunteers here. Just upload your files to an accessible location (HTTP, FTP etc.), then email this list, include the link and ask for someone to upload your files. This mailing list will strip attachments from messages, and in any case, it is not a good idea to send attachments to mailing lists, as you would realize, since everybody has to download them! We hope our request will be given due consideration. It certainly will. Meanwhile, I hope this information gives you something to go on with. Good luck with your translations! :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN [1] http://translate.sourceforge.net/wiki/l10n/pluralforms#h [2] http://live.gnome.org/TranslationProject [3] http://l10n-status.gnome.org/index.html PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [translate-pootle] Gnome glossary project
On 29/11/2006, at 4:49 PM, Josep Puigdemont wrote: El dc 27 de 09 del 2006 a les 16:10 +0930, en/na Clytie Siddall va escriure: On 27/09/2006, at 6:50 AM, Young Joo Pintaske wrote: I think I might have lost some part of this email thread, but couldn't locate them in the archive. I saw the Gnome Glossary website: http://developer.gnome.org/projects/gtp/glossary/ and noticed an old colleague of mine who used to work in our group as the contact person. I'm not sure how this project originated back then. I'd like to pass on the glossary tool that we use at Sun Globalization: https://g11nportal.sun.com/sungloss It requires user account which you can get immediately. You can find terms (English and translated into about 9-10 languages) for Gnome there and export glossary for your language into a spreadsheet. I'd be happy to get your feedback on them and find a way to collaborate to refine the glossaries. Young Joo, at Wordforge (Pootle, Translate Toolkit etc.), we are currently working on expanding the Gnome glossary, refining both a 1000 word and a much larger terminology file, plus an acronym file. It will be integrated into the Pootle interface, but will also be available from a translation memory server, and for download. So the glossary will be used as a translation memory, then? It's important for us to know, in part because there are some verbs to translate and if this file is just a reference or a glossary, then we'd translate them as infinitives (i.e. to open instead of open), otherwise (ie. if it is a translation memory) we'd keep the imperative form as in English. Definitely as translation-memory. So we do give priority to the form most likely to be used in localization tasks (usually not the infinitive, as you say). The Wordforge end of this glossary project is progressing only in occasional leaps, when Youssef Chahibi or I find enough time to work on it. But we will get there... ;) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Sun contributed l10n documentation
On 10/11/2006, at 12:50 AM, Francisco Javier F. Serrador wrote: That sound very good notices. I will setup a pootle server as soon as possible. Maybe it is the thing we are looking for. The Pootle developers are very keen to help projects integrate their tools. You'll be very welcome on translate-pootle [1], or #pootle on Freenode. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN [1] https://lists.sourceforge.net/lists/listinfo/translate-pootle Other info: http://pootle.wordforge.org/ http://translate.sourceforge.net/wiki/pootle PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: RFC: going to add 2.18 branch
On 07/11/2006, at 9:07 PM, Gabor Kelemen wrote: Abel Cheung írta: Hi all, I have done the necessary changes to switch to 2.18 release and drop 2.14 branch data form status pages. It's ready for commit. If anyway still like 2.14 to be there, please shout aloud, otherwise I'll go ahead and commit the change (and pray). Abel This week, 2.17.2 is due to be out. Perhaps it's really time to replace 2.14 with 2.18. That's certainly the way it looks from our POV. However, I'm beginning to realize that things may be different for our users. I've just translated the release-notes for Debian Etch, the new Debian system which will be out this December. It proudly announced that it included GNOME 2.14 ! I gather Ubuntu did the same. So we're going to receive feedback and bug reports on GNOME 2.14 files from a large section of our user- base. I don't understand why the distros don't release the current GNOME version, but it means we do need to maintain and update what to so many users is the latest GNOME: GNOME 2.14. In effect, that leaves us working actively on three GNOME branches: the upcoming version (HEAD or 2.18), the latest release (2.16), and what the distros release as the latest release (2.14). :S from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
We're going to have a Wolof team!
To: gnome-i18n Cc: M. M. Mbacke, C. Perrier Hello everyone :) I'd like to introduce Mouhamadou Mamoune Mbacke, who has created the Wolof locale and a complete translation of the Debian Installer for Wolof. This is the first continental African translation we have had in Debian, and since the resources available to African translators are notoriously low, it testifies to Mouhamadou Mamoune's sustained effort and ability. Now he's worked his way through the Debian Installer, which desktop does this ground-breaking localizer choose for his community? GNOME, of course. ;) I've given him the basic info about the project, the link to the GTP wiki page, mailing list etc., and he will be appearing here soon. No doubt he will have more questions. ;) Congratulations to GNOME on this new language, and welcome (Salam alaikum) to Mouhamadou Mamoune! from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Translating Powerfolder !
Hi everyone :) Have you heard of PowerFolder? http://www.powerfolder.com/ Well, now you have. ;) This is a keen free-software project looking for translators. In particular, their Spanish translator is no longer available. ¡Mis amigos, le necesitamos! [We need YOU!] Check out their i18n page: http://www.powerfolder.com/node/i18n and bring your internationalization expertise to PowerFolder! We will now return you to your normal programming... from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Stats page and alert symbol
On 17/10/2006, at 5:36 PM, Žygimantas Beručka wrote: An, 2006 10 17 15:02 +0930, Clytie Siddall rašė: Danilo, what does the alert symbol (exclamation mark in yellow rounded triangle) mean on these pages? For example: http://progress.gnome.org/module/straw Sorry if this is something obvious: it's eluding my foggy mind right now. ;) If you would hold your mouse over it, you would see „Entry for this language is not present in ALL_LINGUAS in configure file“. :) I didn't hover it long enough. ;) I have trouble controlling the mouse, so it is shaky. Thanks for the explanation, Žygis. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Glom 1.2.0 translations
On 15/10/2006, at 7:13 PM, Murray Cumming wrote: I'll be releasing Glom 1.2.0 in the next week or so. It would be nice if people could update the translations. Thanks. By the way, how can I find out what percentage of the Glom strings are translated for each language? Murray, the l10n status pages are here, by language: http://l10n-status.gnome.org/index.html They remind me that I need to update my translation for your program. ;) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Glom 1.2.0 translations
On 16/10/2006, at 8:39 PM, Danilo Šegan wrote: Today at 9:44, Murray Cumming wrote: I don't see any page that tells me about Glom. I think I'd have to look at separate pages for each language, and find the Glom row on each one. http://progress.gnome.org/module/glom I didn't know about this facility. It's great! :D Thanks for pointing to it, Danilo. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: ubuntu translation credits
On 25/09/2006, at 5:47 AM, Toby Smithe wrote: Please make sure that any cases of removed copyrights are bug reported in Ubuntu's bug system, and please let us know the links to those bug reports. If there is no action on those bug reports, please feel free to take this matter further by reporting it to the GNOME Foundation board. Also, those on ubuntu-devel would like to know examples of offending packages, and where to find the strings, in source and at runtime. So far in this discussion, there hasn't been a single direct reference, and I think it's time for some. I didn't record the ones I saw on Rosetta: at the time I thought it must be a mistake and would automatically be fixed. :( I don't have a copy of the Ubuntu CD distributed in Hanoi, because I can't travel. I don't have time to crawl through Rosetta, examining each of our PO files. I have very limited available time, which I have to spend on translating, because we are extremely short of translators. If I get some more time to chase up all those files, I'll report each one. But I do think you can accept from our emails that this has definitely happened, and that a policy to avoid it happening again would be both prudent and friendly. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: ubuntu translation credits
On 24/09/2006, at 5:25 AM, Toby Smithe wrote: Wouter Bolsterlee wrote: 2006-09-23 klockan 21:09 skrev Toby Smithe: I do work on the Ubuntu en_GB translation, as some of you may know. I agree it is hard to merge upstream translation changes, but apart from that, Rosetta is a superb interface. Inexperienced volunteer changes are not committed, as approval into a team is required. The main problem with the Dutch (nl) translation has been solved some time ago: there where *way* to many people in the team contributing crap translations. Now that every member of the team has been removed and only added back after approval by the coordinator, this is not much of a problem anymore :) Well, I'm sorry to say this but that was rather the fault of the coordinator, as the team should have started out as being approval- only membership from the beginning. However, I still completely understand your feelings. I was a bit distressed today to be told that at Software Freedom Day in Hà Nội on the 16th, Ubuntu CDs were distributed which Ubuntu had localized in Vietnamese. I know most, if not all translations on that disk were from my team (upstream work here, at KDE, Debian and in single-program projects like Mailman, Fonforge, Inkscape etc.) It does indeed feel unfair to see Ubuntu taking credit for our work. I have seen our translator names removed from PO files in Ubuntu, and in general, I'm unhappy about this situation. Due to the continuing access-control and quality-assurance issues in Rosetta, I have advised my team not to use it. The Ubuntu Vietnamese statistics on Launchpad represent my team's work upstream. :( from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: help: could not submit my translation to zh gnome community
On 22/09/2006, at 12:50 PM, Serena wrote: Thanks Vladimer and all. Yes, I understand all your points :). I will wait until the communication problem is solved. It's important, Serena, to remember that it's not your fault if your team isn't responding. If you've tried to contact them, and you've told us about it on this list, you've done your best. :) We value your translation work, and certainly don't want to see any translator discouraged by lack of support or communication. So please do continue to ask questions here, or on the #i18n IRC channel on the irc.gnome.org server. :) It might take a while for the status of your team to be clarified. Meanwhile, you can proceed with translation and/or catch up with information about the Gnome Translation Project: http://live.gnome.org/TranslationProject That page hasn't been translated into Chinese yet, so there's plenty of work available! :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: help: could not submit my translation to zh gnome community
Hi Serena :) On 18/09/2006, at 6:43 PM, Serena wrote: I translated the new text in two gnome .po files to zh, but only find that I could not submit my translation to the community via the zh community alias: [EMAIL PROTECTED] That must be frustrating for you. :( I keep trying sending mail to the alias for one week and always get a Warning message Transcript of session follows - [EMAIL PROTECTED]... Deferred: Connection timed out with lists.linux.net.cn. Warning: message still undelivered after 4 hours And I could not access zh community's web page as shown on http://developer.gnome.org/projects/gtp/teams.html. Do any of you know the reason or know how I can submit the translation? Have you tried contacting your team coordinator (Wang Jian)? If you can't get through, his email address is on the same server as the mailing list, so that will show that there may be a problem with the server. If you do get through, you can discuss the problem with him and/or send your files to him. Either way, we will get somewhere with the problem. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: string changes in release notes
On 06/09/2006, at 3:21 PM, Brent Smith wrote: I've made a couple of string changes in the release notes: modules: gnomeweb-wml directory: /www.gnome.org/start/2.16/notes/docbook I'm not sure the deadline for these, so I hope I didn't cause anyone too much trouble. Brent, do we have the PO files for the release-notes up on the docs status page [1] yet? I can't see them there. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN [1] http://kvota.net/doc-l10n/by-modules.html ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: string changes in release notes
On 06/09/2006, at 7:50 PM, Danilo Šegan wrote: Today at 9:12, Clytie Siddall wrote: Brent, do we have the PO files for the release-notes up on the docs status page [1] yet? I can't see them there. Should be up in like 20-40 minutes (after stats finish updating). I am entirely to blame :( Thanks to both Danilo and Brent. Please don't see my enquiries as a criticism: I think we all realize how difficult it is to find voluntary time for all these activities. :) And you guys do so much. :)) I just enquired so we can get the translations going. Having them available as PO on the docs status page simplifies the task and means you will have more translations sooner. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Number of supported languages (was: Re: Malayalam is not in the supported list
On 06/09/2006, at 7:57 PM, Danilo Šegan wrote: We've got a whooping 54 languages supported in this release! Has there ever been more? Release and marketing teams, take a note of that! It really is a sign of a successful translation project, when your number of supported languages grows steadily over time. It's not an easy thing to achieve! Congratulations to everyone who has worked so hard and consistently in the GNOME Translation Project. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [Fwd: Re: GNOME 2.16 release notes]
On 03/09/2006, at 8:06 AM, Brent Smith wrote: The release notes can now be translated - they are in the gnomeweb- wml module, at www.gnome.org/start/2.16/notes/docbook They use gnome-doc-utils/xml2po for translation When will they be on the docs page? [1] It's still listing the 2.14 release notes. It would be a much easier start for us if we had the 2.14 notes merged into the 2.16 file, and the .po files available, as is usual on [1]. It does save time if we don't have to do all that manually. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN [1] http://kvota.net/doc-l10n/by-modules.html#release-notes ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Assamese translation for GNOME
On 28/08/2006, at 11:23 PM, Amitakhya Phukan wrote: Hi all, I want to join the GNOME translation project and want to work on the Assamese translation. Welcome ! :) I have contacted the coordinator of this project, Mr. Sunaram Patir, and he has welcomed me to the project team and has directed me to this link: http://developer.gnome.org/projects/gtp/join.html I want to participate actively in this project. Please do tell me what more is required from my side so that I can contribute to the maximum and how do I obtain the CVS access to it? I have already subscribed to the list at this email address of mine. The most useful way to contribute to the project is by reading the information in the wiki (especially the Howto documents), and by sharing the internationalization task with other translators in your team. This means learning from each other, helping each other with translation, and working together to create the best Assamese translation of GNOME! I am sure your team-leader will have plenty of work for you to do. :) Apart from translating files, language teams also work on developing a consistent and accurate vocabulary, reviewing translations, dealing with bug reports and testing input/display and other software issues with their language. You can also help developers understand how best to create software that will be appropriate for your culture. You can report typos in PO files, test translations and generally be a contributor to the GNOME project. Please feel free to ask further questions here, if they're not answered by our documents in the wiki. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translating plural forms with different c-formats
On 28/08/2006, at 3:34 PM, Theppitak Karoonboonyanan wrote: Hi Abel, On 8/28/06, Abel Cheung [EMAIL PROTECTED] wrote: On 8/27/06, Theppitak Karoonboonyanan [EMAIL PROTECTED] wrote: My language has no plural form. And I recently got some complaint that having more than one msgstr[] while declaring nplurals=1 blocks the build due to gettext error. So, I try to examine if there are other such errors left in any other packages. I'm afraid you are using gettext = 0.15, as it is more strict in checking plural form and mark inconsistent Plural-Forms and actually translation as error. gettext 0.15 just ignore it and wouldn't complain. It's not me who find the complaints. It's just from others. I have encountered the same problems with those files. These errors may be caught by gettext-0.15's useful capacity to point out spurious plural forms, but they are about string format. For the real fix, you can remove any entry containing msgstr[1], leaving only msgstr[0]. Yes, I know that, as I said I had tried to do so to all PO's under my maintenance. However, my question is for certain cases where c-format string with plural form is shared with some non-c-format. And there is actually _no_way_ to cover both with a single msgstr[0] entry without messing one of the two. Please read my first post for the details. Exactly. If we kludge it and create a msgstr[0] which includes the placeholder, we still have the conflict between the two different types of strings. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: How to translate new string in gnome-applets
On 24/08/2006, at 10:07 AM, Thomas Thurman wrote: On 23/08/06, Daniel Nylander [EMAIL PROTECTED] wrote: Hi all, How should I translate the new string Tomboy (ne Stickynotes) in gnome-applets? ne is what? Not equal? Traditionally, in the UK and US, women have taken their husband's name on marriage. When you want to tell people a woman's name and have both her old and new names listed, you would write it like this: Lucy Hall nee Auger where nee is the French word for born, because that was the name she was born with. This is an example of the same idea: they are saying that what is now Tomboy was once Stickynotes. However, they appear to think that Tomboy is male, so are using the masculine form of nee, ne. (This is rather amusing, since in English a tomboy must necessarily be female.) If the same concept doesn't exist in your language, you could treat it as something like Tomboy, formerly Stickynotes. This issue actually came up in a previous l10n bug in Bugzilla. When consulted, the French translator didn't recognize ne without its accent, either. The question of software gender further complicated matters. It would really be better to avoid uncommon usage in original strings. formerly or previously both sound good to me. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gnome-applets-locations
On 22/08/2006, at 9:50 AM, Danilo Šegan wrote: Hi Matic, Yesterday at 23:55, Matic Žgur wrote: I would just like to ask, if anyone knows what happened to gnome-applets-locations. Yesterday (or maybe a day before), it had over 6000 strings but the last time I looked at it (which was a few minutes ago), it lost about a half of them. I didn't notice any message here on the mailing list, that's why I'm asking. See http://davyd.livejournal.com/190070.html Btw, translators have started complaining that they have too few messages to translate? :) No, we're just worried we might have to translate them again! :D (Matic, your PO compendium and msgmerge are your friends. :) ) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Joke
On 17/08/2006, at 9:26 PM, Арангел Ангов wrote: A joke for all of those that are into Chuck Norris jokes. I was laughing at one of those jokes when I came up with this: Chuck Norris single-handedly translated GNOME into 60 different languages during the string freeze period. but while showing off his translation muscles, he accidentally punched out cvs.gnome.org. You can see the scene in slow-motion from five different camera-angles. ;) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: SVN anytime soon?
On 16/08/2006, at 8:26 PM, Ross Golder wrote: On Tue, 2006-08-15 at 23:11 +0930, Clytie Siddall wrote: Hi all :) The SVN migration page in the wiki [1] looks a bit sad. :( I hope we're still going ahead with it. Does anyone have some more up- to-date information? I haven't forgotten about it! I'm currently in the process of moving house/country, so am a bit short of spare time at the moment. I hope to bring some more cheerful news in the next few weeks, once I've settled back in the UK. You mean, after moving house and country, you're going to move the repo as well?!! Any one of those three is a big task, let alone all three together. Good luck! :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Question regarding entering translation bugs in Bugzilla
On 14/08/2006, at 2:11 PM, Changwoo Ryu wrote (in conclusion): But when a bug is not obvious and when it goes to the long discussion, sometimes on translation policies, I guess the discussion is going to be in our mailing list, not in the bugzilla. Well, the bugzilla is another language barrier to most Korean users and contributors. And to users and contributors in my community. :( Having Bug-Buddy translated should help (can one report l10n bugs via Bug-Buddy?), but I have also wondered about translating Bugzilla itself. I haven't seen any i18n features in a Bugzilla, or in any other tracker. Has anyone translated a bug/patch tracker? Would it be worth- while to do so? from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Question regarding entering translation bugs in Bugzilla
On 08/08/2006, at 7:09 AM, Young Song wrote: My question is, whether it will be acceptable to the communities if we enter translation bugs in Bugzilla. We would like to contribute to the l10n community by providing our QA while we don't have individuals who can discuss the bugs for all the languages we test in the respective language communities at this time. We in the Vietnamese translation team also use Gnome Bugzilla for Gnome files. You are welcome to report bugs against our translations (and even more welcome to join the team ;) ). from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Feel that localization love!
On 11/08/2006, at 6:47 PM, Sini Ruohomaa wrote: Also, this week there's 34 languages with over 90% messages translated in 2.16 and 45 languages over the supported line. Feel that localization love! :D It's great to see. Congatulations, especially, to teams representing languages which will be supported for the first time in this release! :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: New team coordinator and web site for pt_BR team.
On 14/07/2006, at 11:04 PM, Christian Rose wrote: On 7/14/06, Clytie Siddall [EMAIL PROTECTED] wrote: Guilherme, bem vindo! Welcome to GNOME! I'm happy to see you here. :) Actually, Guilherme is an old timer in the GNOME community (as you can probably see from his e-mail address, and information about him can also be found at http://live.gnome.org/GuilhermePastore and http://blogs.gnome.org/gpastore ). But I suspect he still appreciated your welcoming. :-) That was the idea. ;) I knew he wasn't new, but thought he should have a fanfare anyway, having done so much good work in l10n. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: GPL: disclaimer and format
On 12/07/2006, at 12:11 AM, Jason D. Clinton wrote: If I recall correctly -- while GPL translations are helpful -- the GNU does not allow them to be considered official. Therefore, the only document with any legal weight is the official English version. You are correct. GNU stipulate on their page for unofficial translations [1] that they will support unofficial translations of their licences, by listing them and linking to them, providing their supplied disclaimer is prefaced to each translation. The disclaimer prevents any reader of a translated licence from assuming that the translation is a legal document. Readers of other languages may not otherwise be aware that only the English version has been assessed and certified as a legal document (the costs of doing this for other languages are not practical: professional translators + liability insurance + legal services). So, my question remains: could we please include the supplied GNU disclaimer in our translated versions of the published GNU licences in gnome-desktop/desktop-docs, as Debian does? I am uncomfortable with providing translations for these licences _without_ the GNU disclaimer. I believe doing so leaves us open to users assuming our translationed licences are also legal documents. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN [1] http://www.gnu.org/licenses/translations.html PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: New team coordinator and web site for pt_BR team.
On 11/07/2006, at 12:22 AM, Gustavo Maciel Dias Vieira wrote: I'm the current team coordinator for the Brazilian Portuguese team and I would like to introduce the new team coordinator. Guilherme de S. Pastore gpastore at gnome dot org will coordinate the team from now on. I believe some of you already know him, and I'm sure he will do a great job. Abraços, Gustavo Gustavo, thankyou for all you have done for GNOME, for free software, and for your community. Your work lives on after you. :) Guilherme, bem vindo! Welcome to GNOME! I'm happy to see you here. :) To both of you, good luck with everything! :‚ from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: burmese - non-responsive coordinator
On 11/07/2006, at 11:07 PM, Victor San Kho Lin wrote: Well, it's all nice and all the tools are ready. Bro Lin Htun, pls add me for the team. I would much initiate to contrib the effort. I hope, Bro Zaw Win Aung is also still stick here for contribution. Pls update for me. Thanks. --Victor SKL Victor, mingalaba ! (Sorry I don't know how to write that properly. Welcome!) Good luck with your team-effort at GNOME. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Malayalam GNOME Translation
On 11/07/2006, at 10:17 PM, Ani Peter wrote: Hi Christian, Thanks a lot for making me the new Malayalam Coordinator in GNOME. Have checked the links you have sent me. All ok. I have downloaded the gnome files and already started working on them so that they can be submitted asap. Thanks again Best regards Ani Ani, swagatam ! (Sorry I don't know how to write that properly. Welcome!) Good luck with your translation effort here at GNOME. I hope things go well for you and your team. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Unification of free software disclaimers
On 12/07/2006, at 3:27 AM, Yavor Doganov wrote: However, I think that it's important to have translated licences since a lot of people don't speak English at all and these people are part of our common target group, provided: * These translations include the official translation disclaimer both in English and translated; Yes, please! GNOME is the only place I have found these licences translated without the GNU disclaimer. See my other email on this topic. * Ideally, the original English licence is included or, better, a link or something else pointing to it; * This refers to the docs module as well, not only to the About boxes; * We're talking only about the FSF licences. GNOME is part of the GNU Project and uses the copyleft licences that FSF has created. The other less common ones just don't matter. I think the OFL [1] is worth considering, especially if we include fonts with our distro. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN [1] Open Font Licence: http://scripts.sil.org/cms/scripts/page.php? site_id=nrsiid=OFL ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
GPL: disclaimer and format
Hi everyone :) It's taking me a while to catch up with things, so sorry if I come an go a bit. That will probably continue. I recently translated the GNU General Public Licence. It had not previously been translated into our language. My translation has been reviewed by another member of our overall team, and has been sent to GNU as an unofficial translation following their guidelines, also posted in vi.Wikisource. [1 Having translated the GPL, I used my translation to complete the gpl.po which is part of the Debian Installer User Manual [2], and the gpl.po which is in gnome-desktop/desktop-docs. I have two concerns with the GNOME version: 1. It does not include the disclaimer which GNU insist _must_ be included. [3] I imagine there are heavy legal consequences for not including it, and in any case, my translation is definitely an unofficial one: I am not a professional translator with insurance to cover legal issues, and I have not consulted lawyers about the content. How do I add the required disclaimer to the gpl.po file? The Debian PO file does include the disclaimer, but the GNOME file doesn't have it at all. 2. The text in the GNOME gpl.po does not always follow the order of the original GPL (or of the Debian gpl.po). This would be confusing if one were translating the GNOME version first. I strongly recommend the paragraphs and headers be placed in order in this file. The original text does have an ordered and logical message, so disrupting the order of paragraphs or sentences also disrupts the meaning, and makes it more difficult for the translator to understand. I do remember point 1 being raised here before. I think it's important that we resolve it ASAP. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN [1] http://vi.wikisource.org/wiki/GPL [2] http://people.debian.org/~seppy/d-i/manual/POT/ [3] http://www.gnu.org/licenses/translations.html ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Markup in messages
On 11/07/2006, at 7:58 AM, Christian Rose wrote: Does anyone consider this to be a problem, or are you just happy the way it is? I support you. Not only is it a problem, one more thing that can break, but it's one more difference preventing exact matches using msgmerge. I spend way too much time changing fuzzy strings like this: ,fuzzy msgid bPreferences/b msgstr Tùy thích to msgid bPreferences/b msgstr bTùy thích/b simply adding, modifying or removing formatting to match the original string. The actual text is fine. I really don't see it as our job to adjust formatting. I would indeed prefer to concentrate on the actual translation. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: New Urdu Team
On 21/06/2006, at 2:14 AM, Christian Rose wrote: So you probably see why I am frustrated and suspicious about the situation. To ease my mind, could you please give me a reference (preferrably an URL) that points to past Urdu translations that you have produced? It would be a lot of help in determining that this time it's for real, before we make a decision about the new coordinatorship for Urdu. Also, Muhammad, when you have any problems with the task, please ask questions here. :) We all had to start at the beginning, and we have all met with difficulties of one kind or another. We help each other, within our teams, and here on the mailing list. We all have times when we are confused, can't find the appropriate information, need help with one thing or another. We run out of time, we have trouble communicating, we have technical problems. This is the same for all of us. So please don't give up. When you need help, please ask. We do this job together. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: new Czech GNOME translation team leader
On 16/06/2006, at 8:56 PM, Stanislav Brabec wrote: Because I am no longer working on GNOME translations, I want to pass my function to a new person - Jakub Friedl [EMAIL PROTECTED]. It is sad to see you go, Stanislav: thankyou very much for all your work! You know that its effects continue, with every person who uses GNOME in Czech. :) Vítejte Jakub! (Welcome!) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Conflicting ChangeLogs
On 04/06/2006, at 3:03 AM, Åsmund Skjæveland wrote: On Sat, Jun 03, 2006 at 04:16:24PM +0930, Clytie Siddall wrote: Speaking of ChangeLogs, I've come across quite a few recently which have needed reconciling: I update the ChangeLog, and CVS tells me it's tried to merge the differences, but is giving up with a headache, so it passes the headache on to me. ;) I don't mind doing this occasionally, but I've had to do it too many times recently. It can take a while, with large differences. I think it's nearly always (or always) been Gnome-2-14 modules' ChangeLogs. Is there any reason why so many ChangeLogs would have major conflicts? If so, is there anything we can do to avoid it? do a cvs update ChangeLog before you add your entry. Don't add your entry until just before you commit your updated PO file. It's a lot less likely that somebody else will update the ChangeLog in the minute it takes you to update the ChangeLog, add your entry, and commit the new ChangeLog and PO files. Åsmund, I _do_ cvs update the ChangeLog just before I need to edit it. The conflict is apparently between my current copy of the ChangeLog and that on the server. It usually occurs when I have checked out the Gnome-2-14 module, then want to update it for the first time. I have no idea why the copy on server become so different in that time, nor why cvs can't integrate those differences. I'll keep a copy next time it happens. Maybe that will help me sort out what is happening. Thanks for your help. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translations for LSR project
Yagor, thanks very much for your reply. :) On 06/06/2006, at 5:51 AM, Yavor Doganov wrote: Clytie Siddall wrote: I have a sigh licensing question. How does such a statement affect those of us who have already assigned our translation copyright to the FSF (for example, translators who contribute to The Translation Project)? This is not a problem, IMHO. The copyright assignment papers that we've signed to FSF refer to the translations which we are willing to assign copyright to the FSF. For me, this is every single translation I make, For me, too. but it totally depends on you. Also note that the Disclaimer of the TP is *not* actually a copyright assignment, e.g. the FSF does not act as assignee. For that you need to write to [EMAIL PROTECTED] I'm considering this is a good idea, because imagine the following scenario, which in fact actually happens sometimes: The copyright holders of Foobar decide to relicense the program from GPL to BSD-like license. Someone takes the BSD code and makes a derived proprietary version. In order to include my translation, they'll have to ask approval from the FSF, which won't be given (in fact it won't be given to relisence it to BSD at first instance). So, it better protects our work and ensures that it will never enhance non-free software. Unfortunately, people sometimes change their mind about freedom. Thankyou very much for clarifying that for me. I really don't understand the legal aspects, and just want my translations to be free. I'm very glad I signed the FSF disclaimer. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translation of GPL/LGPL
On 01/06/2006, at 12:01 PM, Danilo Šegan wrote: Yesterday at 22:49, Daniel Nylander wrote: I noticed that the template for GPL/LGPL does not include a disclaimer from FSF regarding the legal issues with the translated text. I am aware of the issue, but I don't have plans on working on that anytime soon (at least some of support should be added to gnome-doc-utils/xml2po). Feel free to report it as a bug against xml2po (so it doesn't get lost or forgotten): http://bugzilla.gnome.org/enter_bug.cgi?product=xml2po Meanwhile, can we simply add the disclaimer at the top? I've done a draft (unofficial) translation of the GPL for my language, which is being reviewed. I was doing it for the GNU website, so there was at least one translation available for our lamguage, not realizing the GPL was also a GNOME template. When it's been finalized, I'd like to offer the translation here, too. But I'd certainly feel uneasy about using it without the disclaimer. :S from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Conflicting ChangeLogs (was: Re: Documentation: Editing the ChangeLog file with emacs
Speaking of ChangeLogs, I've come across quite a few recently which have needed reconciling: I update the ChangeLog, and CVS tells me it's tried to merge the differences, but is giving up with a headache, so it passes the headache on to me. ;) I don't mind doing this occasionally, but I've had to do it too many times recently. It can take a while, with large differences. I think it's nearly always (or always) been Gnome-2-14 modules' ChangeLogs. Is there any reason why so many ChangeLogs would have major conflicts? If so, is there anything we can do to avoid it? from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Gnome 2.14 status pages mostly yellow
Hi everyone :) Is this just my (vi) pages, or is it happening to everyone? The files on Gnome 2.14 desktop and developer-libs pages have mostly yellow bars, no data. :( They weren't like that yesterday. http://l10n-status.gnome.org/gnome-2.14/vi/desktop/index.html http://l10n-status.gnome.org/gnome-2.14/vi/developer-libs/index.html from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: How do strings get to newer versions?
Hello Raivis :) On 18/05/2006, at 4:54 AM, Raivis Dejus wrote: I have heared that you use msgmerge to get strings from older versions to the newer ones, but how often does that happen? We are lucky that the Gnome servers msgmerge any available translations from existing files into our PO files (not POT files, however: we have to do that). This means that when new strings are added to a PO file you've already translated, the Gnome server will search through existing translations in your language to try and match the new strings. That's why you may already be seeing new strings marked fuzzy, with a suggested translation. and if i have translated something for gnome 2.14 should i comit that file to gnome 2.16? can this cause any problems? and what about commiting/getting gnome 2.16 translations to 2.14 2.14-2.16 If you have translated the 2.14 file, the Gnome server will msgmerge that into the 2.16 file, so when you download the 2.16 file, all the strings that _can_ be matched from available translations, have been matched. e.g. if you have translated epiphany.2.14.lv.po, the Gnome server will: 1. msgmerge all those strings into the epiphany.2.16.pot file 2. try to match any of the new strings (it might create some exact and some fuzzy matches, with some remaining unmatched [empty] strings) 3. create the file epiphany.2.16.lv.po for you to download, update and commit. You can then apply msgmerge from your own compendium, to match any remaining empty strings, if you like. It won't overwrite any exact matches (or, I think, fuzzy matches). Any 2.16 files you _haven't_ translated for 2.14 will be empty (POT) files. 2.16-2.14. I don't know. Possibly the server msgmerges in reverse this way, but if it doesn't, you can do that yourself. (I don't think this situation would happen often enough to justify a change in procedure, but you could suggest it, if it doesn't already exist.) What you _don't_ do, is commit 2.16 files to 2.14 or vice versa. The original strings will be different. This is tantamount to changing the original strings in a file, which we must never do, since that can break the build of the application, when our PO files are reintegrated with the source. Always make sure you have the correct PO file for each version, before translating it, or committing it. as some parts of gnome are being translated also in launchpad.net, can I commit/get those translations to gnome upstream? Rosetta (in Launchpad) still has serious security and quality-control issues. It also does not show the current versions of many files. :( I don't know the best way of using any of those translations, but I would strongly recommend encouraging translators working there to work directly through Gnome (as I do for my language). We have an effective infrastructure here, we have quality-assurance and access- control procedures, and we're working with the current files. Until Rosetta can address its current access and quality issues, and work more closely with projects like Gnome, I don't see it as a valid alternative. Pootle does have these features, but doesn't yet have the project integration we need, although this is planned. Once it has been established, Pootle will be a valid and useful translation tool. Rosetta just needs to follow their example, which, since it's already using some of the Pootle technology, shouldn't be that difficult. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: New team for Dhivehi (dv)
On 12/05/2006, at 8:26 PM, Sofwathullah Mohamed wrote: coordinator: Sofwathullah Mohamed email: [EMAIL PROTECTED] bugzilla account: [EMAIL PROTECTED] language name: Dhivehi ISO 639 code: dv Web page: as of now none. Marhaba Sofwathullah. :) (Welcome!) Good luck with your translation effort. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: FSF Postal address on GPL
On 09/05/2006, at 7:54 AM, Francisco Javier F. Serrador wrote: I have noticed that applications that are currently incorporating GPL license are using the old FSF's snail address (Temple Place...) The current address is: 51 Franklin Street, Fifth Floor Boston, MA 02110-1301 USA It's worse than that: you get one address in one application, and the other address in a different app.! If the address has indeed changed, we need the PO files updated _consistently_, to show that. from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: New Team Leader for Macedonian
On 06/05/2006, at 8:29 AM, Арангел Ангов wrote: I ll be around, will be maintaining a small number of modules and helping out on the list as much as I can. I'm glad you're not disappearing entirely! :) It was really fun working with all of you nice people. ;) Thanks very much for all the work you've done. That makes a lasting difference. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: ALL_LINGUAS in HEAD version of .po files
On 27/04/2006, at 8:21 AM, Danilo Šegan wrote: Nope, add them to po/LINGUAS files, in one language per line format. Is having po/LINGUAS a practice which will increase now? When I was adding a lot of translations, I only had one module which used po/ LINGUAS. I'm very strongly in support of keeping the add-language behaviour in the /po directory, as it reduces the size of the working copy for translators who don't need the whole source. It also makes it obvious where the language needs to be added, which is useful for newer translators. It certainly would have helped me. ;) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Getting started
On 24/04/2006, at 8:00 PM, John C Barstow wrote: If he is, for some reason, unable to continue, and you are happy to become the new team leader, please ask John to email this list and advise that he is handing over to you. You could have at least given me a decent amount of time to respond. ;) I'm still here, just overwhelmed by the amount of work. :) Sorry, I was responding to Michael saying: I came across an old translation effort for the Maori language on Gnome. I have emailed around my LUGs and have found little or no interest in continuing the effort. I didn't realize there was current activity. blush Glad to hear it, though. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Getting started
On 23/04/2006, at 8:59 AM, Michael J Knox wrote: My name is Michael Knox, I live in Hamilton, New Zealand. Hello Michael! waves across the Tasman Sea (and some land) I am a Fedora Core user and support, plus a contributer to Fedora Extras. :) I came across an old translation effort for the Maori language on Gnome. I have emailed around my LUGs and have found little or no interest in continuing the effort. So my question is, how do I get started? Have this doc: http://developer.gnome.org/projects/gtp/l10n-guide/ How do I submit changes? Any advise on starting out? Firstly, welcome to the Gnome Translation Project! Please see our wiki page [1], which is more up-to-date than some of the website pages. On that page, you can see several Howtos, and the list of translation teams. Please contact the current co-ordinator for the Maori team (John Barstow). If he is still active, he will tell you how you can best help in that translation effort. If he is, for some reason, unable to continue, and you are happy to become the new team leader, please ask John to email this list and advise that he is handing over to you. Please read the Howtos, as they give you a lot of the Getting Started info you will need. After you've done that, you're welcome to ask further questions here. :) The GTP wiki page also gives you links to the current status pages, where you can see the progress of the Maori team. You could also start looking at some of the files, to see what state they're in, what vocabulary is being used etc. Please also register with Gnome Bugzilla. You might also want to look at the Translate WIki [2], especially the Localization Guide, which contains a lot of general information on the translation process, comparisons of editors and other tools, and some useful tips. :) And again, Haere mai! (Welcome) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN [1] http://live.gnome.org/TranslationProject#preview [2] http://translate.sourceforge.net/wiki/ PGP.sig Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Comparing methods
On 22/04/2006, at 1:17 AM, Danilo Šegan wrote: On April 15th, Christian Rose wrote: However, concerning new features, the translation status pages have basically been unmaintained for several years now. There are lies, damned lies and statistics. That is changing. Look forward to reading more about Damned Lies (damned-lies in CVS, preview on http://l10n-status.pemas.net/) in the following days. Anyone, feel free to start a page on live.gnome.org to request things you find useful and discuss them. This looks good! :) Danilo, the one thing I've seen on the KDE status pages [1] that would really help me at Gnome is the embedded nature of the webpages. I don't have to leave the status pages to find links to other i18n information like the Howto, team list, language list etc. The side-bar, search bar, integral program crumb trial and drop-down language-list are real time-savers, and keep the whole thing in front of you, which actually saves brain cycles. Can we do something like that? (I'll put a wiki page up tomorrow, if someone else doesn't do it first.) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN [1] e.g. http://l10n.kde.org/stats/gui/trunk/vi/ (and no rude comments about our stats, we started from zero only recently ;) ) ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
