Re: BoF item 11/14: improvements to D-L
I talked with Ana Rey at GUADEC-ES about some small improvements I'd like to do in DL (progressbar in translators profile, link to show/hide completed modules in this profile) and she is working on it. These are small patches that she could upload to bugzilla. The progressbar is nealr finished, and I opened a bug about it some time ago, so I hope it will be close soon. Cheers 2012/8/3 Fran Dieguez lis...@openhost.es Hi!, I'been working in D-L, mostly learning Django for helping more in the future. I wrote the wiki page https://live.gnome.org/**DamnedLies/NewThemehttps://live.gnome.org/DamnedLies/NewThemefor contacting with the Design theme and try to get them involved in the design. You can checkout the code from the D-L repository in the branch newtheme: http://git.gnome.org/browse/**damned-lies/log/?h=newthemehttp://git.gnome.org/browse/damned-lies/log/?h=newtheme Next week I have some spare time and I will work more in D-L. Cheers. On Xov 02 Ago 2012 22:05:48 CEST, Gil Forcada wrote: Hi all, As I said in previous mails, let this mail be a kickstart for giving feedback about the items that are defined on https://live.gnome.org/**TranslationProject/Events/**GTPBoFGUADEC2012https://live.gnome.org/TranslationProject/Events/GTPBoFGUADEC2012 In this mail please give feedback about the improvements on D-L item. Cheers, -- Fran Diéguez http://www.mabishu.com GPG: 43DD 1B00 035F A764 4986 E695 98BB 6626 A2A4 F9B8 __**_ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/**mailman/listinfo/gnome-i18nhttps://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: BoF item 4/14: Splitting modules
The main problem I see in OLPC moduleset is that it has some external modules (hosted in Transifex, etc). This may be a problem for some coordinators, who doesn't have an account in this platform, and don't know to work with it (at the beginning, it may be a bit tricky...). Also, this kind of modules can be problematic, since you see the module completed at 80% in DL, but at 100% in Transifex, so you can get confused. 2012/8/3 Chris Leonard cjlhomeaddr...@gmail.com On Fri, Aug 3, 2012 at 1:46 PM, Johannes Schmid j...@jsschmid.de wrote: Hi! See https://live.gnome.org/TranslationProject/SplittingModules Overall we wanted to base the Supported language status on having translated at least 80% of Core, Core Apps, Extra Apps and Accessibility. Furthermore, we *might* want to create a Basic Support status for having translated Core and Core Apps to give more motiviation to small teams. We still need feedback if there are any UI strings in the Libraries section that are shown to the user. (Excluding cryptic error messages and properties displayed in glade). Johannes, One of the main reasons I've mentioned the OLPC Release Set http://l10n.gnome.org/releases/olpc/ as a potential starting point for localizers is that it represents the Gnome packages that are pulled down by OLPC (typically via Fedora RPM repos) to create the Gnome side of the Sugar/Gnome dual-boot OS image, as well as a few Gnome core infrastructure modules that lay a little deeper in the stack of what is a fairly minimalist GNU/Linux Fedora spin. It's value as a point of comparison is not so much that it is want is needed for an OLPC XO laptop, but rather that it is a module collection that has been culled down by intense size pressures (one GB total storage on an XO-1) and therefore is one specific example of a minimal set. I've done my best to keep the packages displayed in the OLPC Release Set current by going through the packages.txt file in OLPC releases as they become available, a pending major release by OLPC is complicating this a little at the moment. I should explain that at the present, time while there is an ongoing transition from GTK2 to GTK3 in the Sugar / OLPC OS stack, I have chosen to only point to the GTK3 master branch versions of packages. This release set is intended to be more forward-looking in terms of L10n needs/wants and not necessarily about back-filling translations on existing releases, although the reality of the situation is that an OLPC release will likely be one or more release cycles back from Gnome master when it goes out the door given that it largely draws from Fedora RPM repos and lags the Fedora release cycle. Taking a look at the libraries (or other packages) included in the OLPC release set might give you some ideas about what it might be worth including in a priority L10n target set. You will need to take into account that given it's focus on children in the educational setting, the inclusion of things like gcompris are driven because they are educational games and not because they are needed to make a minimal Gnome desktop sign and dance. Just a thought for your consideration. Consider it one downstream's very-specific POV as measured by the packages pulled from Gnome. cjl ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'gnome-user-share.master'
Hi Philip! Your last commit to gnome-user-share broke string freeze for gnome 3.4. I know it was just fixing up the english string but still it would be nice if you could ask the maintainer to create a gnome-3-4 branch before that commit. Thanks, Johannes Am Freitag, den 03.08.2012, 20:07 + schrieb GNOME Status Pages: This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'gnome-user-share.master': + If this is true, Bluetooth devices can send files to the user's Downloads directory when the user is logged in. + If this is true, the Public directory in the user's home directory will be shared over Bluetooth when the user is logged in. + If this is true, the Public directory in the user's home directory will be shared over the network when the user is logged in. + Unable to launch the Personal File Sharing Preferences Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. http://git.gnome.org/browse/gnome-user-share/log/?h=master ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n signature.asc Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Best way to format a name string in Folks
Hello, I'm currently adding a new display-name property in FolksIndividual as discussed in bug #651672 (https://bugzilla.gnome.org/show_bug.cgi?id=651672). One of the possible values we'd like to set this value to would use the given_name and the family_name of the contact. Currently, I'm simply doing var name = structured_name.given_name + + structured_name.family_name; which outputs a string containing exactly $given_name $family_name. Is this the best way of doing this or should, for example, the string format be translatable? Thanks in advance for your opinions on this. Best regards, Laurent Contzen ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Best way to format a name string in Folks
Hi Laurent 2012-08-04 10:18 keltezéssel, Contzen Laurent írta: Hello, I'm currently adding a new display-name property in FolksIndividual as discussed in bug #651672 (https://bugzilla.gnome.org/show_bug.cgi?id=651672). One of the possible values we'd like to set this value to would use the given_name and the family_name of the contact. Currently, I'm simply doing var name = structured_name.given_name + + structured_name.family_name; which outputs a string containing exactly $given_name $family_name. Is this the best way of doing this or should, for example, the string format be translatable? This should be translatable. For example, the standard name order in Hungarian is $family_name $given_name, so your solution would not work for my language and for a few more, see: http://en.wikipedia.org/wiki/Name_order#Name_order Probably %s %s with a comment about their meaning and how to switch the order is enough, like: Translators: first %s is the given name of the contact, the second %s is the family name. To change the order, use %2$s %1$s Thanks for asking! Gabor Kelemen Thanks in advance for your opinions on this. Best regards, Laurent Contzen ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'gnome-user-share.master'
2012/8/4 Johannes Schmid j...@jsschmid.de: Your last commit to gnome-user-share broke string freeze for gnome 3.4. I know it was just fixing up the english string but still it would be nice if you could ask the maintainer to create a gnome-3-4 branch before that commit. I think branch gnome-3-0 would be more appropriate in this case, as the last release of this project is 3.0.2. -- Piotr Drąg http://raven.fedorapeople.org/ ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Best way to format a name string in Folks
On Sat, Aug 4, 2012 at 9:34 AM, Gabor Kelemen kelem...@gnome.hu wrote: Hi Laurent 2012-08-04 10:18 keltezéssel, Contzen Laurent írta: Hello, I'm currently adding a new display-name property in FolksIndividual as discussed in bug #651672 (https://bugzilla.gnome.org/show_bug.cgi?id=651672). One of the possible values we'd like to set this value to would use the given_name and the family_name of the contact. Currently, I'm simply doing var name = structured_name.given_name + + structured_name.family_name; which outputs a string containing exactly $given_name $family_name. Is this the best way of doing this or should, for example, the string format be translatable? This should be translatable. For example, the standard name order in Hungarian is $family_name $given_name, so your solution would not work for my language and for a few more, see: http://en.wikipedia.org/wiki/Name_order#Name_order Probably %s %s with a comment about their meaning and how to switch the order is enough, like: Translators: first %s is the given name of the contact, the second %s is the family name. To change the order, use %2$s %1$s I think if you are going to use variable names as Gabor suggests, I would go beyond using the simplest string name token %s. With mor ethan one such token in a translatable string is less than ideal, I would suggest something like %(givenname)s %(familityname)s. Yes, it is true that this will inevitably result in some printf errors when localizers mistakenly translate what is inside the parenthesis, but these are easy to catch (pofilter printf flag) and easier to fix (just change the variable name back to English). I'm not convinced that this format will result in any more errors than using the simplest tokens and expecting localizers to add the proper numbering as suggested by Gabor. My own point of view on this is that I find it frustrating when developers to ask a localizer to do a job that the glibc locale should be capable of addressing all on it's own. Translating Day and Month names should be banned in PO files :-) There is in fact an entire section in glibc locales called LC_NAME in the glibc locale that has a field for Name format (name_fmt) as described below. My argument is that develoeprs should leverage the information content of the glibc locale to the greatest extent possible, that is after all the primary purpose of having glibc locale files. cjl Sugar Labs Translation Team Coordinator From Claude Paroz's excellent Locale Helper web-app http://lh.2xlibre.net/values/name_fmt/ LC_NAME Name format (name_fmt) Define the appropriate representation of a person’s name and title. The operand consists of a string, and can contain any combination of characters and field descriptors. In addition, the string can contain field descriptors defined below. %f Family names. %F Family names in uppercase. %g First given name. %G First given initial. %l First given name with latin letters. In some cultures, eg on Taiwan it is customary to also have a first name written with Latin letters, although the rest of the name is written in another script. %o Other shorter name, eg. Bill. %m Additional given names. %M Initials for additional given names. %p Profession. %s Salutation, such as Doctor %S Abbreviated salutation, such as Mr. or Dr. %d Salutation, using the FDCC-sets conventions, with 1 for the name_gen, 2 for name_mr, 3 for name_mrs, 4 for name_miss, 5 for name_ms. %t If the preceding field descriptor resulted in an empty string, then the empty string, else a . Each field descriptor may have an after the % to specify that the information is taken from a Romanized version string of the entity. An initial is any string, normally consisting of one letter and a punctuation mark; the Dutch IJ is an example of a two character initial. ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
