Re: Problems commiting damned-lies package

[Fòram na Gàidhlig]

I think WebLate would be a good pick. It has a glossary function too,
which teams will find handy to help with terminology consistency. And
you can download the files to translate too, in a long list of formats
of your choice. And it has some QA checks too, like punctuation, printf
placeholders etc.

I only tried to translate a project once on Zanata and found the
experience frustrating enough that I decided to go off and translate
something else.

And while I have become pretty skilled in using Git for programming work
and I love how powerful it is, I don't want to use Git directly while
translating.

IMO the optimum workflow would be to pull weblate translations with a
scheduled GitLab CI job and let the CI commit them into a branch when
they're green. The master branch should be protected and nobody should
be allowed to push there directly. Even skilled and experienced project
maintainers will make mistakes, because nobody is perfect.



Sgrìobh Carlos Soriano na leanas 22/06/2020 aig 13:47:
> Hey Daniel,
> 
> First of all, I want to say that I see your POV, and you cannot change
> the whole thing by yourself and I'm glad you are pushing to address
> these translators' pain points in your time. I do agree on the technical
> side with Emannuelle, but I also understand it's not something that will
> happen unless some developer with the right skillset invests the time to
> do it, and that might be harder to find on the gnome-i18n group.
> 
> I believe the issue is limited to certain groups, since you have access
> already for the GNOME group right? If so, it's a bit tricky, as those
> projects are not necessarily fully tied to GNOME. We don't support them
> in the same way we support the GNOME group, that is by design and as a
> result of having a more open infrastructure than we had before - now
> everyone can create their own personal project in GNOME's GitLab, even
> if they don't have commit rights to GNOME projects.
> 
> Now, I don't see why we wouldn't make it easy for translators of GNOME
> to provide translations in other projects in our infra if desired, as
> long as we make the difference between GNOME projects and the rest clear
> in DL. We also have to acknowledge that certain projects might want to
> handle their permissions and workflow differently - they might block the
> master branch to anyone but maintainers. It's a reality that MR + CI is
> becoming the de facto approach, and the longer we take to transition to
> something else, the more painful is going to be for gnome-i18n.
> 
> For a possible short term solution, could you file a GitLab ticket
> at https://gitlab.gnome.org/Infrastructure/GitLab detailing which groups
> or projects you would like to have access to, and the requirements and
> use cases that the gnome-i18n has for having commit right access? That
> way, it is not blocked on me or our own private communication.
> 
> As a long term solution, did gnome-i18n investigate if there are other
> tools available (Zanata, WebLate, etc.) that would fit what we need
> here? I understand DL was created with certain features and workflows
> that fit well GNOME, but I have the feeling times are changing faster
> than we can adapt and we cannot find the developer resources to do so.
> Adopting one of those external tools might open new possibilities
> too, and bring a new type of contributors.
> 
> Let me know if you have any other comments.
> 
> On Mon, 22 Jun 2020 at 13:29, Daniel Mustieles García
> mailto:daniel.mustie...@gmail.com>> wrote:
> 
> Again this is David against Goliat, and I'm tired of fighting...
> 
> I have no skills to improve DL, I only developed a script and made
> it available to everyone who wants use/read/whatever with it. If if
> can be a start point to improve DL great! but I'm not going to keep
> fighting against something that I cannot change.
> 
> I don't know which features Gitlab offers, sorry if I still think
> like in 2009. Maybe someone with better knowledge than me could show
> us the proper way or even help with a tool or a patch for DL. I made
> a bash script  because I don't know Python. I'm a translator, not a
> developer, sorry.
> 
> I'm leaving here the discussion/thread, but thanks for your comments
> and your point of view.
> 
> Regards
> 
> El lun., 22 jun. 2020 a las 13:13, Emmanuele Bassi
> (mailto:eba...@gmail.com>>) escribió:
> 
> On Mon, 22 Jun 2020 at 11:44, Daniel Mustieles García
> mailto:daniel.mustie...@gmail.com>>
> wrote:
> 
> Hi Emmanuele,
> 
> Just a quick question: which is the difference between
> commiting directly into Git and commiting through DL?
> 
> 
> DL can, at least, centralise the place where tests are executed
> to ensure that things don't utterly break. Of course, it's not
> really a solution: now that we use GitLab, we already have a
> centralised place to run builds

Re: Pitivi Import Dialog Redesign

[Fòram na Gàidhlig]

Sgrìobh Yatin Maan via gnome-i18n na leanas 22/07/2018 aig 18:45:
> Hey,
> I should have been more clear, we are not as concerned about strings as
> we are about the layout. Particularly stuff like (in Option B) the
> sentence being somewhat split between a label and a combo-box (ie "Use
> optimised media for - Unsupported Assets").
> 
> You can find the current dialog + new mockups here
> - https://imgur.com/a/MXgtibA 


Word order problems in that particular phrase can be circumvented by
translating as "Use optimised media for the following assets:" +
combobox. Just make sure to add good translators' comments to the po
files, so that translators will understand which strings belong together.

I can't judge how this affects languages with RTL scripts like e.g.
Arabic or Devanagari though.
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Is any translator team using glossaries?

[Fòram na Gàidhlig]

Sgrìobh Sveinn í Felli na leanas 30/04/2018 aig 09:19:
> Þann sun 29.apr 2018 20:32, skrifaði Rudolfs Mazurs:
>> Hi all,
>> I was looking around for a glossary for the GNOME project. The only one I
>> could find was made 14 years ago [1]. Perhaps there is a more up-to-date
>> version somewhere?
>>
> 
> You can roll your own using gettext [1], which calls them 'compendium'
> [2]. Beware, at first you may get a file with *all* existing strings in
> the project - what you really want is a selection of short definitions
> and words that are of help for translators.
> It can take several passes of gettext commands to filter out the
> relevant strings into a combined PO-file or a CVS (better for structuring).
> To use the glossary with a CAT-application like Lokalize, you would
> probably like to convert your glossary to a TBX-format (industry
> standard glossary exchange format); there are multiple tools available
> to help with glossary creation, but curiously most of them are
> Windows-only (Glossary Converter, Okapi-Rainbow, Heartsome-TMX...).
> Some of those run fine in Wine on Linux.
> 
> OT: But you may also ask yourself *why* glossaries should be based on
> specific software-projects; for my (tiny) language, a coordinated effort
> has been made to publish sector/discipline-based glossaries [3]; one for
> each of astronomy, economics, engineering, electronics, etc. (total of
> 43 glossaries + a combined one I made myself). I even got separate
> glossaries for networking/encryption/certificates, for
> computers/software and for computers/hardware.
> Similar glossaries may exist for your language.

You have a great setup there :)

The optimum solution is to have a cross-project glossary that everybody
who localized into your language agrees on. This avoids ending up with
different words for the same thing. For example, Germans get confused
about the difference between "Kennwort" and "Password" - well, it's just
different translations for "password". This is where being short on
translators can actually turn into an advantage - it's easier to
coordinate and swap glossaries and TMs!
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Unable to submit to repository

[Fòram na Gàidhlig]

Sgrìobh Claude Paroz na leanas 24/04/2018 aig 07:48:
> Le 23. 04. 18 à 10:03, Fòram na Gàidhlig a écrit :
>>> Don't you have a message beside your name in the author menu that your
>>> account is missing full name?
>>> Is it a problem for you to fill first and last name for your account?
>>
>> Well, it was never an issue before. And yes, I don't post my real name
>> on the internet, ever. I like my privacy.
> 
> Isn't posting here ruining your privacy already?
> https://mail.gnome.org/archives/gnome-i18n/2018-April/msg00038.html

If people Google my real name, this won't come up, so I'm fine with it.


> And if it's not you real name either, then you can just put this name in
> the first name/last name fields of your DL account.
> 
> Claude


Cool, done! Submit went through :)
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Unable to submit to repository

[Fòram na Gàidhlig]

> Don't you have a message beside your name in the author menu that your
> account is missing full name?
> Is it a problem for you to fill first and last name for your account?

Well, it was never an issue before. And yes, I don't post my real name
on the internet, ever. I like my privacy.
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Unable to submit to repository

[Fòram na Gàidhlig]

Hi,

I am trying to use "Submit to Repository" like I have done for the past
few years, now, but I'm getting an error message:

"Committing a file requires a commit author."

I am not allowed to select myself as commit author, and nobody else is
in the dropdown list.

https://l10n.gnome.org/vertimus/229322/275

Any idea what the problem is?
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Updated month name translations needed in GLib

[Fòram na Gàidhlig]

Sgrìobh Rafal Luzynski na leanas 26/03/2018 aig 21:39:
> 26.03.2018 13:43 Fòram na Gàidhlig  wrote:
>>
>>
>>>> Reminder for *every* translation team: you should update strings from
>>>> glib/gdatetime.c in GLib to avoid a chance of English dates in the
>>>> next GNOME release. Languages which won’t get an update soon will get
>>>> a commit from https://gitlab.gnome.org/GNOME/glib/commits/wip/piotrdr
>>>> ag/missing-months
>>>> merged.
>>>
>>> I have merged that branch to GLib master, so it will be in the 2.56.0
>>> release. There is still time for translation teams to update the
>>> strings there before the release, if you spot any problems with them.
>>>
>>> (Please CC me in any replies as I am not subscribed to gnome-i18n.)
>>
>> I tried to look at Piotr's commit to try to find our what I need to do,
>> but the link is dead now.
> 
> Piotr already provided the updated commit link but for the record and
> for other languages this link may be helpful, at least now, as we are
> shortly after these changes:
> 
> https://gitlab.gnome.org/GNOME/glib/commits/master/po
> 
>> Any chance to have an idiot's guide on which file to edit, and which one
>> will be the stand-alone form?
> 
> You should edit (or actually: review if it is edited correctly) your
> translation for glib project in Damned Lies. As Piotr said, the stand-alone
> form is the one with the old "full month name" and "abbreviated month name"
> context. I find it ambiguous and wanted to introduce "full month name
> standalone" and "abbreviated month name standalone" but the glib
> maintainer said that this drops existing translations and does not
> provide any additional value.
> 
> Also I think that the translators comment before "January"/"Jan"
> is a sufficient "idiot's guide" (sorry, that's not my opinion.) :-)
> If not then please explain how to fix it.
> 
> While at this, the translators comments mention that you should refer
> to the latest glibc and some command line utilities and see how they
> handle the month names. But this is not true for Scottish Gaelic
> (as well as for some other languages). The reason is that I did not
> have any feedback from you recently (but of course I really appreciate
> your feedback I received about a year ago) and I did not want to
> introduce changes to the locales without the final ack from the
> actual translation teams; also I did not have time to ping each
> translation team individually. As a result there are some languages
> where the nominative/genitive month names are (probably) needed but
> they are not yet supported.

I guess what confused me is the talk of direct git commits - so I
thought that I had to do soething special here. Thanks to the link to
the commit, I have now found them in the current development branch on
Damned Lies. The comments are indeed sufficient :)
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Updated month name translations needed in GLib

[Fòram na Gàidhlig]

>> Reminder for *every* translation team: you should update strings from
>> glib/gdatetime.c in GLib to avoid a chance of English dates in the
>> next GNOME release. Languages which won’t get an update soon will get
>> a commit from https://gitlab.gnome.org/GNOME/glib/commits/wip/piotrdr
>> ag/missing-months
>> merged.
> 
> I have merged that branch to GLib master, so it will be in the 2.56.0
> release. There is still time for translation teams to update the
> strings there before the release, if you spot any problems with them.
> 
> (Please CC me in any replies as I am not subscribed to gnome-i18n.)

I tried to look at Piotr's commit to try to find our what I need to do,
but the link is dead now.

Any chance to have an idiot's guide on which file to edit, and which one
will be the stand-alone form?




signature.asc
Description: OpenPGP digital signature
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: [dconf-editor] cleaning of translations, 2nd approach

[Fòram na Gàidhlig]

Sgrìobh Arnaud Bonatti na leanas 06/03/2018 aig 22:51:
>
> For every problem, there’s a code solution.

Actually, there's not. Adding a comments e.g. to tell translators
whether "View" means a verb or a noun would be a lot more useful - and
there's a case right here that can't have correct machine translation
guarenteed. QED.

My particular locale will throw a lot of false positive errors for
standard pofilter checks, just because its typography is different. I do
use those checks and vet them manually. Automation by a project
maintainer can't be done here, it's impossible. Just to give you an example:

"Please press the ‘Close’ button."
"Am brùth thu air a’ phutan “Dùin”?"

pofilter will barf here on endpunc and on the quotes.

Automatic generation of content can be very tricky, and the bug fixes to
your algorithm for every locale under the sun would probably take longer
than translators manually fixing their stuff. Even worse is he case
where translators won't even know you've changed their translation. Not
everything is as easy as removing double spaces, and you sometimes need
an actual mismatch there too - command line help texts come to mind here.

So, if you really want to help translators out, soend your time to pay
attention to adding comments, and make sure to always use ngettext when
your string contains a number, and don't hard-code word order. This will
make your localizers very happy :)
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Unauthorized translation changes in dconf-editor

[Fòram na Gàidhlig]

Sgrìobh Alexandre Franke na leanas 06/03/2018 aig 12:55:

> That’s a perfect example of why you shouldn’t have made your changes in
> the first place and reached out to translators instead. We switched to
> typographic apostrophe for 3.26. All new strings should already be using
> them and we fix them in old strings as we go when working on new strings
> in a module. We actually have a translation for dconf-editor currently
> on Damned lies which we blocked mid-process because of your changes.

Agreed. I get is why you wanted to help out with cleaning up, but any
change needs to always be vetted by an actual translator. There is no
way that you could know what each team's style guide or actual current
state of the translations is. Also, things that look like a typo to you
might be actually correct. Just to give an example, in my locale,
changing ’s to ‘s will introduce a serious typography error. Not
speaking my language, there is no way that you could possibly know that.

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Wikidata pull of ISO-3166-1 regions in many languages

[Fòram na Gàidhlig]

I think this is a great project. I know that CLDR do a JSON export that
you could use to get at their data:

https://github.com/unicode-cldr/cldr-json

It wouls also be really neat to have them in a format that translation
software can read, like XLiff or gettext .po - we could use that to feed
our translation memories and all avoid a serious case of RSI from all
the copy/paste :)


Sgrìobh Chris Leonard na leanas 25/12/2017 aig 20:00:
> I had mentioned my playing around with wikidata queries looking at
> ways of looking up simple, proper name translations of things like
> country names, language names, script names or other such simple, but
> often difficult or laborious translation tasks.
> 
> This has approximately 240-odd regions by 300 odd languages.
> 
> I'm sharing it with anyone who is interested in this idea, still
> looking to compare against the CLDR territories entries and Debian
> Alioth isocodes project.  My scripting-fu is not as strong as it could
> be and so it will take longer.
> 
> I'm quite pleased with the results so far, and will be looking into
> other domains beyond ISO-3166-1 in time.
> 
> cjl
> 
> 
> 
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-i18n
> 

-- 
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v2.0.22 (MingW32)

mQINBFNbSyEBEADh+uhohycnZgPPnyMs5pZQG6pKyLzFZoIKbVjY31ZoPZ2SdltB
elrwn6kFZkQiDx4K6nkZFHsPh8RMvWoFWg1rGiWkdsZessLFawraC8YEZDwtlaU5
SFXbE4+QnMfbPhe9tmC8Nbhec3dfV9zcXAhxc+zkIUsKFhSkpJ2Syvo9FCA/5adW
UZgWWKFwlSg4+/lrhJ6QJnldPlXfWcuEasKF7fjdafDIdS5hdKu8Lv+CiPQWvgsi
J2BDlZLzEZf3PD+NMujUbJa0nilD2ltu3/qRvR2f86YV6wRwt4E2OD8JJQOau4X2
Pg7vqkIbnB9rMiQ6T17rQ4rc80eesGCxQ6XOba9oa1eRRZDwY7HJtYwvPdw9HZaN
Lq2RRbGDGO0q7fxrzbp1WuNN+UXOA/pmVzWWczPfPHVcNIehGf3wQI+Vgh/qa+IZ
jLJ25I1Tv85cDzvv5gdtI8PR4JTfK6Db+gUJmsuIg2fmsljxA7OmeTgSPR7nEVq5
VlHYfx1T0uKlthWw/eDwlS44vTgm6HZzIdYqdPMPa/PU1U+WVuDejyDJTn/1TY78
oJMT/IixFR+N+smohhKASprewcsO2ClWGptSG0sRTiCrVHFD3Mt6SCVaxsQLHvek
KuNAUXhR2KSvYuqGT0Nv3bplN6svCp4CuAGZ3lyOIt/Sb7OFUwzcx2sOdwARAQAB
tC5Gw7JyYW0gbmEgR8OgaWRobGlnIDxmaW9zQGZvcmFtbmFnYWlkaGxpZy5uZXQ+
iQI5BBMBAgAjBQJTW0shAhsPBwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AACgkQ
UHP09XBr75NHNBAAxv2C/G13Z1kCFOSOnbPpzqcIDcMuP7RK1Mv5XfOZLfqSw4le
gdDmZggX2/EBH6xFTXFPLSE6rVUKTkHLA7IY8D43GBtDWjcIyyuLnIjtR+LhRKCP
3/Sm8MyZMQvUH1CBpUXFNnP/HCR6xjm1Mog5kXxFeCR9PMjeEiobKXIVuMfuNlBD
WzoR2Nh+oroXLjZw3VMFewiCyhu4Pe7F3sLpVldiI3PBOyPQOBZ3HEIM490D/Lrh
rl3Wwmoug8j8rqkh/Fr+kKaToRJik4PkcxsfepzhMdNfCpr7I3jE5XQHzib5Ubv8
wsSaVNBG92NTnGKoAntWXBUaiDN84St9l+Zm/BgedRk+7wdESHBuOuFXoRc0yEjF
4tLOhyO9u5bYGQWHyJiwhbw51R8G+Kh3OPq/tr4KmsuueEI2v5cLkoDzwCpYyMnu
BfU8d0mt5eULbQCWcy7LYeQs6E+CEB+tPL3Qz2zaAAvwt7N2PLMjHf5Fcqj5LqrV
mzQfcB9zQFq9Rtld/IIIDkE1y/q/SNFYsFNW/u/bxWsu+lMOYtBco++O5DJhAq6t
7rJXUBirju50hhogHfBL2v6RG1b8/uiWm0m8713ZhiSvpr4Dd+V+DU9nPli5nTmU
En6gP7TTYJKETMf7O9i873Z8yG6zd0/fBzFyruS2KRTPV2GiVT6CI37gUtw=
=fcOW
-END PGP PUBLIC KEY BLOCK-
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Contributing to Unicode annotations

[Fòram na Gàidhlig]

You will have to sign up to their Survey Tool for that. Submission
periods are usually once per year, in the Summer, and people who have
registered an account will get an e-mail when it's open for submission.

http://cldr.unicode.org/index/survey-tool

If you want your votes to have some more weight, you can try to find a
constibuting organization to sponsor you - I think Wikimedia is a member.

The bug tracker is for contributions that aren't covered by the Survey
Tool, like adding new locales or defining plural rules.


Sgrìobh Chris Leonard na leanas 02/11/2017 aig 03:20:
> 
> 
> On Tue, Oct 31, 2017 at 7:01 AM, Alexandre Franke  > wrote:
> 
> Hey,
> 
> Does anyone around here know whether it’s possible to contribute to
> Unicode annotations? We found them at
> http://www.unicode.org/repos/cldr/trunk/common/annotations/
>  with no
> instructions.
> 
> 
> CLDR doesn't seem to make it super easy to contribute.  Given SugarLabs
> focus, I work with a lot of smaller language communities and I've been
> developing some hacked together POT files (with embedded en-WP links) to
> allow for Pootle hosting as an interim step to trying to develop new
> CLDR locales.  I'm also looking at the corresponding Debian iso-code
> project files to make it a "two-fer" L10n effort (not thrilled with
> Translation Project tool-chain either).
> 
> e.g.
> 
> https://translate.sugarlabs.org/projects/CLDR_regions/
> 
> 
> https://translate.sugarlabs.org/projects/CLDR_languages/
> 
> 
> If you've got a particular language in mind, I could maybe take  a whack
> at setting up a hacky POT for the emoji annotation.  Landing it in CLDR
> is another matter.
> 
> cjl
> 
> 
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-i18n
> 

-- 
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v2.0.22 (MingW32)

mQINBFNbSyEBEADh+uhohycnZgPPnyMs5pZQG6pKyLzFZoIKbVjY31ZoPZ2SdltB
elrwn6kFZkQiDx4K6nkZFHsPh8RMvWoFWg1rGiWkdsZessLFawraC8YEZDwtlaU5
SFXbE4+QnMfbPhe9tmC8Nbhec3dfV9zcXAhxc+zkIUsKFhSkpJ2Syvo9FCA/5adW
UZgWWKFwlSg4+/lrhJ6QJnldPlXfWcuEasKF7fjdafDIdS5hdKu8Lv+CiPQWvgsi
J2BDlZLzEZf3PD+NMujUbJa0nilD2ltu3/qRvR2f86YV6wRwt4E2OD8JJQOau4X2
Pg7vqkIbnB9rMiQ6T17rQ4rc80eesGCxQ6XOba9oa1eRRZDwY7HJtYwvPdw9HZaN
Lq2RRbGDGO0q7fxrzbp1WuNN+UXOA/pmVzWWczPfPHVcNIehGf3wQI+Vgh/qa+IZ
jLJ25I1Tv85cDzvv5gdtI8PR4JTfK6Db+gUJmsuIg2fmsljxA7OmeTgSPR7nEVq5
VlHYfx1T0uKlthWw/eDwlS44vTgm6HZzIdYqdPMPa/PU1U+WVuDejyDJTn/1TY78
oJMT/IixFR+N+smohhKASprewcsO2ClWGptSG0sRTiCrVHFD3Mt6SCVaxsQLHvek
KuNAUXhR2KSvYuqGT0Nv3bplN6svCp4CuAGZ3lyOIt/Sb7OFUwzcx2sOdwARAQAB
tC5Gw7JyYW0gbmEgR8OgaWRobGlnIDxmaW9zQGZvcmFtbmFnYWlkaGxpZy5uZXQ+
iQI5BBMBAgAjBQJTW0shAhsPBwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AACgkQ
UHP09XBr75NHNBAAxv2C/G13Z1kCFOSOnbPpzqcIDcMuP7RK1Mv5XfOZLfqSw4le
gdDmZggX2/EBH6xFTXFPLSE6rVUKTkHLA7IY8D43GBtDWjcIyyuLnIjtR+LhRKCP
3/Sm8MyZMQvUH1CBpUXFNnP/HCR6xjm1Mog5kXxFeCR9PMjeEiobKXIVuMfuNlBD
WzoR2Nh+oroXLjZw3VMFewiCyhu4Pe7F3sLpVldiI3PBOyPQOBZ3HEIM490D/Lrh
rl3Wwmoug8j8rqkh/Fr+kKaToRJik4PkcxsfepzhMdNfCpr7I3jE5XQHzib5Ubv8
wsSaVNBG92NTnGKoAntWXBUaiDN84St9l+Zm/BgedRk+7wdESHBuOuFXoRc0yEjF
4tLOhyO9u5bYGQWHyJiwhbw51R8G+Kh3OPq/tr4KmsuueEI2v5cLkoDzwCpYyMnu
BfU8d0mt5eULbQCWcy7LYeQs6E+CEB+tPL3Qz2zaAAvwt7N2PLMjHf5Fcqj5LqrV
mzQfcB9zQFq9Rtld/IIIDkE1y/q/SNFYsFNW/u/bxWsu+lMOYtBco++O5DJhAq6t
7rJXUBirju50hhogHfBL2v6RG1b8/uiWm0m8713ZhiSvpr4Dd+V+DU9nPli5nTmU
En6gP7TTYJKETMf7O9i873Z8yG6zd0/fBzFyruS2KRTPV2GiVT6CI37gUtw=
=fcOW
-END PGP PUBLIC KEY BLOCK-
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Error commiting translation into user-docs [system admin guide]

[Fòram na Gàidhlig]

Sgrìobh Petr Kovar na leanas 29/07/2017 aig 16:27:
> On Fri, 28 Jul 2017 14:27:01 +0200
> Daniel Mustieles García  wrote:
> 
>> H all,
>>
>> I'me getting the following error when trying to commit a System Admin Guide
>> translation update using DL:
>>
>> «[Errno 1] b"remote: translations user cannot modify
>> 'system-admin-guide/es/es.po' \nTo ssh://git.gnome.org/git/gnome-user-docs\n
>> ! [remote rejected] master -> master (pre-receive hook declined)\nerror:
>> failed to push some refs to 'ssh://git.gnome.org/git/gnome-user-docs'\n"»
>>
>> Not sure if this issue can be fixed from DL's admin panel or if it's
>> something Infrastructure Team should fix instead.
> 
> Thanks for pointing this out. It seems related to the fact that
> system-admin-guide/ is a bit of a non-standard location for storing help
> files. We've added system-admin-guide/ to DL recently so it might be that
> you are the first hitting the issue.
> 
> I guess this file might be the one that needs a fix?
> 
> https://git.gnome.org/browse/sysadmin-bin/tree/git/pre-receive-check-policy
> 
> Not sure.
> 
> Cheers,
> pk

If this is the first commit of this file, somebody with git access needs
to do it. This is true for all documentation files. Once the file exists
in git, you can submit to repository yourself, but not before.
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Events for translators

[Fòram na Gàidhlig]

>> - Do you think "translated one module per person" is doable in that time
>> and a good way to measure the success of the event? If not, what do you
>> propose as a measurement of success of the event?
> Modules aren't equal, sadly. I wouldn't measure success by the number of
> translated modules.

If we want a quantity measure, counting numbr of translated words is
much more accurate.

I'd rather go for quality though. Teach the newcomers the tools, and
also how to keep the terminology consistent, and how to keep in touch if
in doubt about something. Terminology consistency is not only a problem
for smaller locales where terminology isn't that established yet, but
also for big locales like English or German who have double terminology
in some cases (is it "sign in" or "log in"? Is a "password" a "Passwort"
or a "Kennwort"? ...)
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Date Format with month names in genitive case - your opinions?

[Fòram na Gàidhlig]

> How many times did you translate "%d %B" or "%d %B %Y" vs.
> "%B" or "%B %Y"?

I just grepped my personal translations directory for %B. Our
translation of Gnome is not complete, so there will be more.

Standalone %B:

Shotwell


%B in combination with %d or %e:

Eye of Gnome
File Roller
Gnome Calendar
Gnome Color Manager
Gnome Control Center
Gnome Photos
Gnome Shell
Gnome Software
Linux Mint Cinnamon
Linux Mint Cinnamon Screensaver
Linux Mint Nemo
Linux Mint Xviewer
Mozilla Firefox + Thunderbird
Open Street Map
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Date Format with month names in genitive case - your opinions?

[Fòram na Gàidhlig]

>>  Moreover we use ordinal and cardinal day numbers, ordinal for the first day
>> of the month, and cardinal for the others (2-31)
>>  Moreover we use singular for the first day, plural for the others...
>>  So we really need this solution.
>>   
>>  example:
>>  al 1ⁿ di mai dal 2017
>>  ai 15 di mai dal 2017
> 
> This is a different issue, independent on what I'd like to
> discuss here. But I assure you that I'm aware of it and I've
> already commented here:
> 
> https://bugzilla.gnome.org/show_bug.cgi?id=768192
> https://sourceware.org/bugzilla/show_bug.cgi?id=10547#c2

I have now also filed a ticket with the CLDR for this issue:

http://unicode.org/cldr/trac/ticket/10213
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Date Format with month names in genitive case - your opinions?

[Fòram na Gàidhlig]

>From my language's point of view. The CLDR approach is what looks the
most sensible. Displaying "of April" as a standalone date would look
very weird in my language, and having the 'genitive' form displayed as
nominative would be the lesser of two evils.

For example:

June = An t-Ògmhios
18 June = 18mh dhen Ògmhios

So, depending on how it's coded, that would give us "dhen Ògmhios" or
"mh dhen Ògmhios" if the 'genitive' was used as a standalone date.



Sgrìobh Rafal Luzynski na leanas 18/04/2017 aig 23:19:
> Hello,
> 
> I was told that GNOME i18n is the right place to discuss this issue
> because it gathers translators from more languages than any other
> place in this part of the net. The problem has been reported to GNOME
> bugzilla as bug 749206 [1] but in fact it's not a GNOME bug but glibc
> bug. [2]
> 
> What is the issue: in many languages, mostly from eastern Europe,
> including my native language, a correct grammatical form of the month
> name when used in the full date context is genitive. A literal
> translation to English applying the same rule would be "18 of April".
> Also we still need the nominative case when the month name appears
> standalone (for example sometimes we just want to say "April").
> 
> The proposed solution is to change strftime() function and anything
> that is backed by or compatible with strftime(): in glib2 the
> functions are g_date_time_format() and g_date_strftime(). These
> functions besides "%B" (full month name) should start supporting
> "%OB" (alternative month name). Also nl_langinfo() function would
> be modified: as now MON_1, MON_2, ..., MON_12 return the data to
> be used as the result of "%B" format specifiers the new set of
> constants ALTMON_1, ALTMON_2, ..., ALTMON_12 would be introduced
> to provide the data for "%OB" format specifier.
> 
> This exact solution:
> 
> - has been implemented in *BSD systems (FreeBSD, OpenBSD etc.) in
>   1990s;
> - is also supported in Apple systems (OS X and iOS) except exposing
>   ALTMON_n constants in nl_langinfo();
> - has been accepted by POSIX as the future change of the
>   specification but has not yet released it. [3]
> 
> Now the controversial part: in all those solutions nl_langinfo(MON_n)
> and strftime("%B") return the genitive case of the month name and
> the newly introduced nl_langinfo(ALTMON_n) and strftime("%OB") return
> the nominative form. It's controversial because now in Linux
> nl_langinfo(MON_n) and strftime("%B") return the nominative case
> while the other case is simply not supported. This would require
> somehow incompatible change. (Note: the backward compatibility feature
> can be introduced.)
> 
> Also it should be emphasized that "genitive and nominative" is
> a little unprecise misleading. Correctly it should be named "the
> correct form when using the month in the full date context, together
> with the day number" vs. "standalone, without the day number".
> For example, the languages which have the genitive form but don't
> use it in the full date context would use their own proper form
> instead.
> 
> Why did BSD, Apple, and POSIX choose that counterintuitive approach?
> One should make a bigger survey before answering this question but
> I believe that it's because the date formats are more often used to
> format the date with the day of the month number than to format the
> month name standalone. This change would fix all applications which
> display the dates without any change in their source code so I think
> it is good even if it would break those few applications which
> display the month names standalone. By "break" I mean "they would
> start displaying the month names in an incorrect form (similarly
> as all other applications display the month names incorrectly now)".
> 
> Note that a similar approach has been chosen by ICU and CLDR with
> their own date formats:  represents the month name in a genitive
> case while  is used when they need a nominative case explicitly.
> 
> glibc maintainers hesitate to accept this solution. I believe they
> need some feedback from the people who actually are going to use this
> feature. So far they agreed [4] to accept this solution but only if
> it is documented as the new experimental feature and if it is not
> yet documented which of "%B" and "%OB" is genitive (full date format)
> and which is nominative (standalone). The idea was that it should
> be decided by the language communities which is which. Also sometimes
> they suggest that BSD implementation is wrong and should be switched.
> 
> So, language communities, what is your opinion about it?
> 
> GNOME is a multiplatform project, it is intended to work correctly
> on Linux but also Windows, OS X, BSD and many other platforms. I think
> it will be easier for the application developers if Linux follows
> other platforms as well as the future POSIX specification.
> 
> You may be also interested in seeing my slides about the issue: [5]
> 
> Best regards,
> 
> Rafal
> 
> 
> [1] 

Re: Challenges in translating GNOME recipes

[Fòram na Gàidhlig]

>> #: src/gr-edit-page.ui:105
>> msgid "Ser_ves"
>>
>> These are prime candidate for the ngettext + placeholder treatment -
>> unless "Ser_ves" is a header.
>
> Yes, Serves is a label. Maybe a bit too colloquial. "Servings" might
> be clearer and better.

"Serves" is fine - what I was getting at is the word order. If your UI
looks like this:

Serves
2

the string is fine. If it looks like this:

Serves 2

the string needs to be "Serves %d", because some languages will put the
number first, or in between multiple words. Some languages might even
need plural forms here.
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Challenges in translating GNOME recipes

[Fòram na Gàidhlig]

Sgrìobh Enrico na leanas 08/12/2016 aig 16:43:
> Hello everyone
> 
> Matthias, I think the translations for the ingredients in a separated
> domain is a good idea to keep them organized and practical to translate
> 
> About your mention to "My current approach is to provide separate
> translations for
> singular and plural, but I guess this way of doing this will never be
> entirely ngettext-ly correct.", have you considered using the gettext
> pluiral-forms
> (https://www.gnu.org/software/gettext/manual/html_node/Plural-forms.html) ?
> 
> Best regards,
> GNOME's pt_BR translation team

I agree with both points. For example, in Gaelic

1 cup = 1 chupa
2 cups = 2 chupa
3 cups = 3 cupannan
20 cups = 20 cupa

So, ngettext is definitely your ticket here.

You should also note that some languages change the order of words and
numbers according to plural forms, so you should always provide printf
placehodlers wherever possible. Code should look something like:

sprintf(ngettext("%d cup", "%d cups", cups), cups)

In general, don't use partial sentences without placeholders.

I went through a part of your PO file - some thoughts:

#: data/org.gnome.Recipes.desktop.in:6
msgid "org.gnome.Recipes"
msgstr ""

Looks like the app id, should that be translatable at all? I don't think so.


#: src/gr-details-page.ui:33
msgid ""
"Ingredients\n"
"gathered"

Provide a translator's comment for those - how much space is there
available on screen? How should the translator handle the line breaks if
there are more than 2 words? My translation would be something like
"Grìtheidean a chaidh a chuingeachadh" or "Grìtheidean air an
cuingeachadh", depending on context. Lose the \n and resolve it by
software if you can.

#: src/gr-details-page.ui:278
msgid "Cooked 5 times"

#: src/gr-edit-page.ui:105
msgid "Ser_ves"

These are prime candidate for the ngettext + placeholder treatment -
unless "Ser_ves" is a header.
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Unicode typography in translations

[Fòram na Gàidhlig]

Sgrìobh Piotr Drąg na leanas 15/11/2016 aig 12:33:
> 2016-11-15 13:14 GMT+01:00  :
>> I am talking about recent Ubuntu and Mint.
>>
> 
> I'm really surprised. I believe they are using UTF-8 like everything
> else in 2016. I can't find any information about it. Could you please
> elaborate on the issue?
> 
> Best regards,
> 

I just gave it a quick test - Unicode ellipsis prints to the default
Ubuntu terminal just fine from a C++ application.
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Gnome Lao Translation Committer

[Fòram na Gàidhlig]

Set to "Ready for Submission", then choose "Submit to Repository" and
enter a comment.


Sgrìobh Saikeo Kavhanxay na leanas 12/09/2016 aig 03:29:
> Hello Aiy Anousak,
> 
>  
> 
> Please look around my translated file here
> https://l10n.gnome.org/vertimus/caribou/master/po/lo and do you have any
> guideline for my new role?
> 
>  
> 
> Thank you.
> 
> Best regards,
> 
> Saikeo
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: String freeze exception

[Fòram na Gàidhlig]

Sounds reasonable to me.


Sgrìobh Alexandru Pandelea na leanas 08/09/2016 aig 11:38:
> Hello,
> 
> I would like to request a string freeze exception for the batch rename
> dialog title in Nautilus (Bug 770974
> ).
> 
> The title of the dialog should reflect if all files are folders, as this
> is also done in other places in Nautilus.
> 
> Thanks,
> Alexandru Pandelea
> 
> 
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-i18n
> 

-- 
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v2.0.22 (MingW32)

mQINBFNbSyEBEADh+uhohycnZgPPnyMs5pZQG6pKyLzFZoIKbVjY31ZoPZ2SdltB
elrwn6kFZkQiDx4K6nkZFHsPh8RMvWoFWg1rGiWkdsZessLFawraC8YEZDwtlaU5
SFXbE4+QnMfbPhe9tmC8Nbhec3dfV9zcXAhxc+zkIUsKFhSkpJ2Syvo9FCA/5adW
UZgWWKFwlSg4+/lrhJ6QJnldPlXfWcuEasKF7fjdafDIdS5hdKu8Lv+CiPQWvgsi
J2BDlZLzEZf3PD+NMujUbJa0nilD2ltu3/qRvR2f86YV6wRwt4E2OD8JJQOau4X2
Pg7vqkIbnB9rMiQ6T17rQ4rc80eesGCxQ6XOba9oa1eRRZDwY7HJtYwvPdw9HZaN
Lq2RRbGDGO0q7fxrzbp1WuNN+UXOA/pmVzWWczPfPHVcNIehGf3wQI+Vgh/qa+IZ
jLJ25I1Tv85cDzvv5gdtI8PR4JTfK6Db+gUJmsuIg2fmsljxA7OmeTgSPR7nEVq5
VlHYfx1T0uKlthWw/eDwlS44vTgm6HZzIdYqdPMPa/PU1U+WVuDejyDJTn/1TY78
oJMT/IixFR+N+smohhKASprewcsO2ClWGptSG0sRTiCrVHFD3Mt6SCVaxsQLHvek
KuNAUXhR2KSvYuqGT0Nv3bplN6svCp4CuAGZ3lyOIt/Sb7OFUwzcx2sOdwARAQAB
tC5Gw7JyYW0gbmEgR8OgaWRobGlnIDxmaW9zQGZvcmFtbmFnYWlkaGxpZy5uZXQ+
iQI5BBMBAgAjBQJTW0shAhsPBwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AACgkQ
UHP09XBr75NHNBAAxv2C/G13Z1kCFOSOnbPpzqcIDcMuP7RK1Mv5XfOZLfqSw4le
gdDmZggX2/EBH6xFTXFPLSE6rVUKTkHLA7IY8D43GBtDWjcIyyuLnIjtR+LhRKCP
3/Sm8MyZMQvUH1CBpUXFNnP/HCR6xjm1Mog5kXxFeCR9PMjeEiobKXIVuMfuNlBD
WzoR2Nh+oroXLjZw3VMFewiCyhu4Pe7F3sLpVldiI3PBOyPQOBZ3HEIM490D/Lrh
rl3Wwmoug8j8rqkh/Fr+kKaToRJik4PkcxsfepzhMdNfCpr7I3jE5XQHzib5Ubv8
wsSaVNBG92NTnGKoAntWXBUaiDN84St9l+Zm/BgedRk+7wdESHBuOuFXoRc0yEjF
4tLOhyO9u5bYGQWHyJiwhbw51R8G+Kh3OPq/tr4KmsuueEI2v5cLkoDzwCpYyMnu
BfU8d0mt5eULbQCWcy7LYeQs6E+CEB+tPL3Qz2zaAAvwt7N2PLMjHf5Fcqj5LqrV
mzQfcB9zQFq9Rtld/IIIDkE1y/q/SNFYsFNW/u/bxWsu+lMOYtBco++O5DJhAq6t
7rJXUBirju50hhogHfBL2v6RG1b8/uiWm0m8713ZhiSvpr4Dd+V+DU9nPli5nTmU
En6gP7TTYJKETMf7O9i873Z8yG6zd0/fBzFyruS2KRTPV2GiVT6CI37gUtw=
=fcOW
-END PGP PUBLIC KEY BLOCK-
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: GNOME Shell integration for Chrome v7 to be released on Sep 5, 2016

[Fòram na Gàidhlig]

Thanks for letting me know - i already suspected as much. the
translation didn't take me that long though, so no worries :)


Sgrìobh Piotr Drąg na leanas 01/09/2016 aig 19:19:
> 2016-09-01 20:04 GMT+02:00 Yuri Konotopov :
>> Hi, GunChleoc.
>>
>> Thanks for your translation, unfortunately Google Chrome currently do not
>> support Scottish Gaelic language.
>> Translation was posted in Chromium bugtracker some time ago, but does not
>> accepted for now. I hope it will be included soon.
>>
>> It was my fault and I'm sorry that I do not explicitly noted this in my 1st
>> e-mail (it's documented in wiki and source tree).
>>
>> Here is full list of currently supported (by Chrome) locales:
>>
>> ar, am, bg, bn, ca, cs, da, de, el, en_GB, en_US, es, es_419, et, fa, fi,
>> fil,
>> fr, gu, he, hi, hr, hu, id, it, ja, kn, ko, lt, lv, ml, mr, ms, nl, no, pl,
>> pt_BR, pt_PT, ro, ru, sk, sl, sr, sv, sw, ta, te, th, tr, uk, vi, zh_CN,
>> zh_TW
>>
> 
> I added a note about supported locales to
> https://l10n.gnome.org/module/chrome-gnome-shell/
> 
> Best regards,
> 

-- 
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v2.0.22 (MingW32)

mQINBFNbSyEBEADh+uhohycnZgPPnyMs5pZQG6pKyLzFZoIKbVjY31ZoPZ2SdltB
elrwn6kFZkQiDx4K6nkZFHsPh8RMvWoFWg1rGiWkdsZessLFawraC8YEZDwtlaU5
SFXbE4+QnMfbPhe9tmC8Nbhec3dfV9zcXAhxc+zkIUsKFhSkpJ2Syvo9FCA/5adW
UZgWWKFwlSg4+/lrhJ6QJnldPlXfWcuEasKF7fjdafDIdS5hdKu8Lv+CiPQWvgsi
J2BDlZLzEZf3PD+NMujUbJa0nilD2ltu3/qRvR2f86YV6wRwt4E2OD8JJQOau4X2
Pg7vqkIbnB9rMiQ6T17rQ4rc80eesGCxQ6XOba9oa1eRRZDwY7HJtYwvPdw9HZaN
Lq2RRbGDGO0q7fxrzbp1WuNN+UXOA/pmVzWWczPfPHVcNIehGf3wQI+Vgh/qa+IZ
jLJ25I1Tv85cDzvv5gdtI8PR4JTfK6Db+gUJmsuIg2fmsljxA7OmeTgSPR7nEVq5
VlHYfx1T0uKlthWw/eDwlS44vTgm6HZzIdYqdPMPa/PU1U+WVuDejyDJTn/1TY78
oJMT/IixFR+N+smohhKASprewcsO2ClWGptSG0sRTiCrVHFD3Mt6SCVaxsQLHvek
KuNAUXhR2KSvYuqGT0Nv3bplN6svCp4CuAGZ3lyOIt/Sb7OFUwzcx2sOdwARAQAB
tC5Gw7JyYW0gbmEgR8OgaWRobGlnIDxmaW9zQGZvcmFtbmFnYWlkaGxpZy5uZXQ+
iQI5BBMBAgAjBQJTW0shAhsPBwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AACgkQ
UHP09XBr75NHNBAAxv2C/G13Z1kCFOSOnbPpzqcIDcMuP7RK1Mv5XfOZLfqSw4le
gdDmZggX2/EBH6xFTXFPLSE6rVUKTkHLA7IY8D43GBtDWjcIyyuLnIjtR+LhRKCP
3/Sm8MyZMQvUH1CBpUXFNnP/HCR6xjm1Mog5kXxFeCR9PMjeEiobKXIVuMfuNlBD
WzoR2Nh+oroXLjZw3VMFewiCyhu4Pe7F3sLpVldiI3PBOyPQOBZ3HEIM490D/Lrh
rl3Wwmoug8j8rqkh/Fr+kKaToRJik4PkcxsfepzhMdNfCpr7I3jE5XQHzib5Ubv8
wsSaVNBG92NTnGKoAntWXBUaiDN84St9l+Zm/BgedRk+7wdESHBuOuFXoRc0yEjF
4tLOhyO9u5bYGQWHyJiwhbw51R8G+Kh3OPq/tr4KmsuueEI2v5cLkoDzwCpYyMnu
BfU8d0mt5eULbQCWcy7LYeQs6E+CEB+tPL3Qz2zaAAvwt7N2PLMjHf5Fcqj5LqrV
mzQfcB9zQFq9Rtld/IIIDkE1y/q/SNFYsFNW/u/bxWsu+lMOYtBco++O5DJhAq6t
7rJXUBirju50hhogHfBL2v6RG1b8/uiWm0m8713ZhiSvpr4Dd+V+DU9nPli5nTmU
En6gP7TTYJKETMf7O9i873Z8yG6zd0/fBzFyruS2KRTPV2GiVT6CI37gUtw=
=fcOW
-END PGP PUBLIC KEY BLOCK-
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: [evolution-data-server] Some translatable strings changed

[Fòram na Gàidhlig]

Sgrìobh Milan Crha na leanas 19/08/2016 aig 09:26:
> On Thu, 2016-08-18 at 11:26 +0200, Rafal Luzynski wrote:
>> If I may put my 2 cents here, wouldn't you guys consider a notation
>> without spaces, like "%s:%s" (inspired by an old MacOS) or "%s::%s"
>> (inspired by C++ namespace notation)?
> 
>   Hi,
> I like the way it had been done some time ago (possibly years ago),
> thus I'll keep it '%s : %s'.
> 
>> It may be already too late to change the notation so maybe use
>> nonbreaking spaces (Unicode character 160 dec or A0 hex)? What if a
>> line gets wrapped at this point?
> 
> The account name (the first %s) and/or even the folder name (the second
> %s) can also contain spaces, thus the nonbreaking space might not give
> much value. But good idea otherwise, I didn't think of it earlier.
> 
>>> maybe replace %s : %s with a single %s using some C magic. :)
> 
> Right. The evolution code uses a "C magic", which may or may not be
> good (would RTL languages prefer to switch the order or not). I thought
> it'll be better done in place in eds, also to avoid one more string
> allocation and immediate free of it. Maybe I'll change my mind in the
> future.

If in doubt, best leave control over this with the translators. So, +1
for keeping this as it is.



>> +1 for suggesting that a translators comment would be helpful here
>> explaining that spaces are intentional and should be preserved
>> as well as explaining what are those %s's.
> 
> Okay, I added translator comments above those strings. There were above
> some already, but not above all. I made them the same or quite similar:
> https://git.gnome.org/browse/evolution-data-server/commit/?id=01b088cc3

Looking good, thanks!

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Team report at GUADEC

[Fòram na Gàidhlig]

Sgrìobh Rafael Fontenelle na leanas 10/08/2016 aig 18:50:
> 
> 2016-08-06 17:45 GMT-03:00 Alexandre Franke  >:
> 
> Hi,
> 
> GUADEC is coming soon and as usual we'll have the team reports there.
> Is anyone volunteering to present? If nobody else wants to do it, I'll
> do it. In any case, let me know of any highligh and interesting
> development you can think of for the past year, so that we can share
> them with the rest of the community!
> 
> 
> How about a online string search in GNOME localization? I often have to
> update my local collection of GNOME Git repository of of translate-able
> modules in order to run my personal grep-based script to look for what
> term my team is using for a give term, and in what context. Such online
> string search feature, filtering by a team and/or branch, could be used
> eliminate problem of diverging translations for languages. If possible,
> generate a Translation Memory as well.
> 
> I'm not a developer, just sharing with the community one idea that came
> to my mind.

Yes, these are good ideas. A glossary function comes to mind as well.

The functions you are describing do remind me of what Pootle can do

http://pootle.translatehouse.org/

I also work with Transifex a lot, but running our own Pottle server
would give us more control, since it's a GPL'ed project.
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Question about Deam Lies

[Fòram na Gàidhlig]

Sgrìobh Rafael Fontenelle na leanas 10/08/2016 aig 17:55:
> (CCing to gnome-i18n mail list)
> 
> 2016-08-10 12:17 GMT-03:00 lawrence aberba  >:
> 
> So when you are away from your PC, then No work?
> 
> 
> Me? Yeah, I tend to do other stuff, as my work and localization (i18n)
> tend to take too much of my time already. I tried to translate via
> mobile phone once, but I've gave up due to bad ergonomics, lack of good
> software, battery consumption etc.
> 
> Anyway, one can always do a quick translation from another computer by
> installing a PO editor, or even using portable version of Notepad++ with
> you're on a WC (Windows computer).

Notepad++ doesn't come with a translation memory with fuzzy matches, so
I don't think that's the best idea.

Something like a Pootle server would be nice, but I have no idea how
much work it would take to integrate that into the Damned Lies workflow.
It would allow both online and offline translation.
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Team report at GUADEC

[Fòram na Gàidhlig]

Sgrìobh Daniel Mustieles García na leanas 08/08/2016 aig 14:33:
> 
> 
> 2016-08-08 14:19 GMT+02:00 Petr Kovar  >:
> 
> On Mon, 8 Aug 2016 12:15:16 +0200
> Daniel Mustieles García  > wrote:
> 
> > We could put on the board (again...) the need of a translation tool. 
> Yes,
> > it's me again talking about the same topic, but note we still don't have
> > it...
> 
> By translation tool you mean an offline PO editor like gtranslator?
> 
>  
> Yes :) We need a tool to translate PO files, able to handle translation
> memories and spell checking at least

Why would we need to reinvent the wheel and create a brand new offline
translation tool? Programmers' time would be better spent in
contributing to the freely available tools that we already have:

http://virtaal.translatehouse.org/
https://poedit.net/
https://www.kde.org/applications/development/lokalize/

Poedit is freemium, but the other two tools are libre.

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Portugal portuguese manual files

[Fòram na Gàidhlig]

For requesting a git account, see

https://wiki.gnome.org/AccountsTeam/NewAccounts



Sgrìobh Tiago Santos na leanas 19/06/2016 aig 18:13:
> Good afternoon Rafael,
> 
> Many thanks for your prompt reply and the submission to the repository.
> 
> I have not yet started with the remaining documentation files (not even
> downloading the Brazilian base files that I mentioned in the other
> reply), but in the meantime I tried to understand the GIT process.
> 
> The main documentation I found in addition to your guidance was the
> following link:
> 
> https://wiki.gnome.org/TranslationProject/GitHowTo
> 
> There is no mention in it about the protocol to create/request a git
> account in GNOME and I was not able to find a a register/login on
> https://git.gnome.org. Should it also be requested on i18n list?
> 
> Best regards,
> 
> Tiago Santos
> 
> Às 15:32 de 11-06-2016, Rafael Fontenelle escreveu:
>>
>>
>> 2016-06-11 11:14 GMT-03:00 Rafael Fontenelle > >:
>>
>>
>> 2016-06-11 10:38 GMT-03:00 Tiago Santos > >:
>>
>> Good afternoon,
>>
>> I am a Portuguese l10n translator/commiter and at the moment I
>> am the most active member of the team. As such, I am
>> contacting you since Duarte Loreto (team coordinator) is
>> presently time constrained and he is unavailable to solve this
>> matter.
>>
>> I am trying to commit documentation translations relating to
>> GNOME apps but in the last month I have faced the following
>> error:
>> "An error occurred during applying your action: The commit
>> failed. The error was: 'Sorry, adding new translations for
>> documentation is not yet supported.'"
>>
>> Some translations have been completed for quite a while and
>> there has been unsuccessful attempts to commit to repository
>> in the past. Has an example:
>>
>> https://l10n.gnome.org/vertimus/gnome-getting-started-docs/master/getting-started/pt
>>
>>
>> Duarte mentioned me that this may be solved uploading the base
>> files on the proper branch directly to git. I hope that can be
>> solved on your side after this contact but, if it is not
>> possible, please guide me in the proper procedures to fix this
>> issue.
>>
>> Many thanks for the given attention.
>> Best regards,
>>
>> Tiago Santos
>> ___
>> gnome-i18n mailing list
>> gnome-i18n@gnome.org 
>> https://mail.gnome.org/mailman/listinfo/gnome-i18n
>>
>>
>> Done.
>>
>> I suggestion double checking translator-credits, as it doesn't
>> contain the name and e-mail address of the last translator.
>>
>> Cheers,
>> Rafael Fontenelle
>>
>>
>> I'm sorry. I read your email so quickly that I didn't notice you were
>> asking more than just a commit of gnome-getting-started-docs. Anyway,
>> I already committed this translation for you guys.
>>
>> Indeed, Damned-Lies doesn't support sending first translation of
>> documentation at the moment, in spite of accepting updates for
>> existent translations.
>>
>> So, at the moment, you need to
>> 1) have Git account in GNOME with write permission;
>> 2) git clone the desired module;
>> 3) manually edit the help' Makefile.am file (normally inside directory
>> help/ or gnome-help/) adding your language code where appropriate;
>> 4) create your language directory (e.g. 'pt') inside the help files'
>> directory and put your translation in it with filename > code>.po (e.g. pt.po).
>> 5) commit + push translation with git
>>
>> For example:
>> https://git.gnome.org/browse/gnome-getting-started-docs/commit/?id=c704b36f6c36c2c594d11462b99ef2cbd70965b4
>>
>>
>> For information on Git usage, see
>> https://wiki.gnome.org/TranslationProject/GitHowTo
>>
>> If you don't have GNOME account with Git permission, you'll need to
>> request. I don't know what is the current policy on it, but some
>> information cane be found in:
>> https://wiki.gnome.org/AccountsTeam/NewAccounts
>>
>> Alternatively, you can ask someone in this list to commit for you.
>>
>> Regards,
>> Rafael Fontenelle
> 
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-i18n

-- 
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v2.0.22 (MingW32)

mQINBFNbSyEBEADh+uhohycnZgPPnyMs5pZQG6pKyLzFZoIKbVjY31ZoPZ2SdltB
elrwn6kFZkQiDx4K6nkZFHsPh8RMvWoFWg1rGiWkdsZessLFawraC8YEZDwtlaU5
SFXbE4+QnMfbPhe9tmC8Nbhec3dfV9zcXAhxc+zkIUsKFhSkpJ2Syvo9FCA/5adW
UZgWWKFwlSg4+/lrhJ6QJnldPlXfWcuEasKF7fjdafDIdS5hdKu8Lv+CiPQWvgsi
J2BDlZLzEZf3PD+NMujUbJa0nilD2ltu3/qRvR2f86YV6wRwt4E2OD8JJQOau4X2
Pg7vqkIbnB9rMiQ6T17rQ4rc80eesGCxQ6XOba9oa1eRRZDwY7HJtYwvPdw9HZaN
Lq2RRbGDGO0q7fxrzbp1WuNN+UXOA/pmVzWWczPfPHVcNIehGf3wQI+Vgh/qa+IZ
jLJ25I1Tv85cDzvv5gdtI8PR4JTfK6

Re: Portugal portuguese manual files

[Fòram na Gàidhlig]

Sgrìobh Rafael Fontenelle na leanas 11/06/2016 aig 15:32:
> 
> I'm sorry. I read your email so quickly that I didn't notice you were
> asking more than just a commit of gnome-getting-started-docs. Anyway, I
> already committed this translation for you guys.
> 
> Indeed, Damned-Lies doesn't support sending first translation of
> documentation at the moment, in spite of accepting updates for existent
> translations.
> 
> So, at the moment, you need to
> 1) have Git account in GNOME with write permission;
> 2) git clone the desired module;
> 3) manually edit the help' Makefile.am file (normally inside directory
> help/ or gnome-help/) adding your language code where appropriate;
> 4) create your language directory (e.g. 'pt') inside the help files'
> directory and put your translation in it with filename  code>.po (e.g. pt.po).
> 5) commit + push translation with git 
> 
> For
> example: 
> https://git.gnome.org/browse/gnome-getting-started-docs/commit/?id=c704b36f6c36c2c594d11462b99ef2cbd70965b4
> 
> For information on Git usage,
> see https://wiki.gnome.org/TranslationProject/GitHowTo
> 
> If you don't have GNOME account with Git permission, you'll need to
> request. I don't know what is the current policy on it, but some
> information cane be found
> in: https://wiki.gnome.org/AccountsTeam/NewAccounts
> 
> Alternatively, you can ask someone in this list to commit for you.
> 
> Regards,
> Rafael Fontenelle

Or ask the maintainers of the individual projects - that is the road I
took, and they were happy to help :)

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: About translating GIMP website (gimp.org)

[Fòram na Gàidhlig]

Sgrìobh Pat David na leanas 31/05/2016 aig 16:33:
> 2. Get those .pot files to the translation team (how?)  (or do we
> provide the .po files themselves?)

You should get them on Damned Lies just like the software translation,
so that all gimp-related translations are in one place. I don't know how
that works though - maybe ask in a developer's IRC channel/mailinglist?
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: About translating GIMP website (gimp.org)

[Fòram na Gàidhlig]

Sgrìobh Mario Blättermann na leanas 30/05/2016 aig 10:03:
> I expect a lot of translatable strings and accordingly a lot of work
> for translators. I urgently recommend to split the content into
> smaller chunks, preferably according to the directories in the Git
> module [1].

+1

Maybe the mdules could also get a category somehow:

1. High priority pages (e.g. frontpage, downloads). For small
translation teams that won't be able to keep up with the rest.
2. Other static content
3. Dynamic content (news,...)
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: New DL option for committers

[Fòram na Gàidhlig]

This flowchart helped me when I got started. However, the "Submit to
Repository" action wasn't available at the time, and it is still missing
from the flowchart.


Sgrìobh Sveinn í Felli na leanas 22/10/2015 aig 15:52:
> Þann fim 22.okt 2015 14:32, skrifaði Rafael Fontenelle:
> 
>> https://l10n.gnome.org/help/vertimus_workflow/
>> The above workflow image might help.
>>
> 
> Actually no;
> I did see that one, and I found also some bits and pieces on the web -
> but nothing sufficiently clear for my poor little brain to figure this
> out by myself ;-(
> 
> This flowchart reminded me on how easy it is to get confused while
> speaking to plumbers about drainage and such; they think about the
> systems from sea-level and up, while their customers think down from the
> sink... ;-)
> 
> Sveinn
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-i18n
> 
> 
> -
> E-Mail ist virenfrei.
> Von AVG überprüft - www.avg.de
> Version: 2015.0.6172 / Virendatenbank: 4450/10870 - Ausgabedatum:
> 22.10.2015

-- 
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v2.0.22 (MingW32)

mQINBFNbSyEBEADh+uhohycnZgPPnyMs5pZQG6pKyLzFZoIKbVjY31ZoPZ2SdltB
elrwn6kFZkQiDx4K6nkZFHsPh8RMvWoFWg1rGiWkdsZessLFawraC8YEZDwtlaU5
SFXbE4+QnMfbPhe9tmC8Nbhec3dfV9zcXAhxc+zkIUsKFhSkpJ2Syvo9FCA/5adW
UZgWWKFwlSg4+/lrhJ6QJnldPlXfWcuEasKF7fjdafDIdS5hdKu8Lv+CiPQWvgsi
J2BDlZLzEZf3PD+NMujUbJa0nilD2ltu3/qRvR2f86YV6wRwt4E2OD8JJQOau4X2
Pg7vqkIbnB9rMiQ6T17rQ4rc80eesGCxQ6XOba9oa1eRRZDwY7HJtYwvPdw9HZaN
Lq2RRbGDGO0q7fxrzbp1WuNN+UXOA/pmVzWWczPfPHVcNIehGf3wQI+Vgh/qa+IZ
jLJ25I1Tv85cDzvv5gdtI8PR4JTfK6Db+gUJmsuIg2fmsljxA7OmeTgSPR7nEVq5
VlHYfx1T0uKlthWw/eDwlS44vTgm6HZzIdYqdPMPa/PU1U+WVuDejyDJTn/1TY78
oJMT/IixFR+N+smohhKASprewcsO2ClWGptSG0sRTiCrVHFD3Mt6SCVaxsQLHvek
KuNAUXhR2KSvYuqGT0Nv3bplN6svCp4CuAGZ3lyOIt/Sb7OFUwzcx2sOdwARAQAB
tC5Gw7JyYW0gbmEgR8OgaWRobGlnIDxmaW9zQGZvcmFtbmFnYWlkaGxpZy5uZXQ+
iQI5BBMBAgAjBQJTW0shAhsPBwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AACgkQ
UHP09XBr75NHNBAAxv2C/G13Z1kCFOSOnbPpzqcIDcMuP7RK1Mv5XfOZLfqSw4le
gdDmZggX2/EBH6xFTXFPLSE6rVUKTkHLA7IY8D43GBtDWjcIyyuLnIjtR+LhRKCP
3/Sm8MyZMQvUH1CBpUXFNnP/HCR6xjm1Mog5kXxFeCR9PMjeEiobKXIVuMfuNlBD
WzoR2Nh+oroXLjZw3VMFewiCyhu4Pe7F3sLpVldiI3PBOyPQOBZ3HEIM490D/Lrh
rl3Wwmoug8j8rqkh/Fr+kKaToRJik4PkcxsfepzhMdNfCpr7I3jE5XQHzib5Ubv8
wsSaVNBG92NTnGKoAntWXBUaiDN84St9l+Zm/BgedRk+7wdESHBuOuFXoRc0yEjF
4tLOhyO9u5bYGQWHyJiwhbw51R8G+Kh3OPq/tr4KmsuueEI2v5cLkoDzwCpYyMnu
BfU8d0mt5eULbQCWcy7LYeQs6E+CEB+tPL3Qz2zaAAvwt7N2PLMjHf5Fcqj5LqrV
mzQfcB9zQFq9Rtld/IIIDkE1y/q/SNFYsFNW/u/bxWsu+lMOYtBco++O5DJhAq6t
7rJXUBirju50hhogHfBL2v6RG1b8/uiWm0m8713ZhiSvpr4Dd+V+DU9nPli5nTmU
En6gP7TTYJKETMf7O9i873Z8yG6zd0/fBzFyruS2KRTPV2GiVT6CI37gUtw=
=fcOW
-END PGP PUBLIC KEY BLOCK-
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Discrepancies with CLDR

[Fòram na Gàidhlig]

Is there a specific reason why locals can't participate in the CLDR? We
found an organization to sponsor us for our locale so we would get
enough votes, and we are being listened to.


Sgrìobh k...@keldix.com na leanas 27/07/2015 aig 12:30:
> Funny, I would say the opposite. Our data is reported by local people,
> where CLDR are managed centrally, somtimes against advice from locals.
> 
> Best regards
> keld
> 
> 
> On Mon, Jul 27, 2015 at 08:36:56AM +0100, Fòram na Gàidhlig wrote:
>> If in doubt, I would go with the CLDR, because that is what the CLDR is
>> for. Note that they have a new major release coming up soon, so maybe
>> best wait with any changes until that has gone through. If anybody of
>> the affected languages thinks that the CLDR data is wrong, I recommend
>> that you get involved with them, because their data will be used very
>> widely (glib, Wikipedia, Microsoft... just to name a few)
>>
>>
>>
>> Sgrìobh Shaun McCance na leanas 26/07/2015 aig 22:17:
>>> Recently, I was working on updating the plural forms used inside
>>> yelp-xsl localization stylesheets. I looked two places to make sure I
>>> got things right: the Unicode CLDR project, and the PO files in gtk+.
>>> Usually they said the same thing, and I was happy. Sometimes they
>>> didn't, and that confuses me.
>>>
>>> http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html
>>>
>>> I'm sending that list of discrepancies in case it's something that needs
>>> to be followed up on. I'm not saying anybody's wrong or there's a bug. I
>>> just think the differences are curious.
>>>
>>> am as bn gu hi kn mr pa si
>>> ==
>>> GTK+ says plurals=2; plural=(n != 1);
>>> CLDR says the singular includes 0
>>> (This is by far the most common discrepancy.)
>>>
>>> br
>>> ==
>>> GTK+ says nplurals=2; plural=n > 1; (singular+zero, and plural)
>>> CLDR says 5 forms: one, two, few, many, other
>>>
>>> cy
>>> ==
>>> GTK+ says nplurals=2; plural=(n==2) ? 1 : 0;
>>> CLDR shows 6 forms: zero, one, two, few (3), many (6), and other
>>>
>>> dz
>>> ==
>>> GTK+ says nplurals=2; plural=(n!=1);\
>>> CLDR says one form
>>>
>>> fa
>>> ==
>>> GTK+ says nplurals=1; plural=0;
>>> CLDR says two forms: singular+zero, and plural
>>>
>>> he
>>> ==
>>> GTK+ says nplurals=2; plural= (n!=1);
>>> CLDR says four forms: one, two, many, other
>>>
>>> is
>>> ==
>>> GTK+ says nplurals=2; plural=1;
>>> CLDR says two forms, but singular is n%10=1
>>>
>>> lv
>>> ==
>>> GTK+ says nplurals=3;
>>>   plural=(n%10==1 && n%100!=11 ? 0 : n != 0 ? 1 : 2);
>>> CLDR says 3 forms: zero(%10), one(%10), and other
>>>
>>> mk
>>> ==
>>> GTK+ declares one more form than it calculates:
>>> nplurals=3; plural= n==1 || n%10==1 ? 0 : 1
>>> This isn't the case in other mk.po files in GNOME, so this is probably
>>> just a type that should be corrected.
>>>
>>> ms
>>> ==
>>> GTK+ doesn't have forms, so defaults to en rules
>>> CLDR says 1 form
>>>
>>> tr
>>> ==
>>> GTK+ says nplurals=1; plural=0;
>>> CLDR says two forms: singular, and plural
>>>
>>>
>>>
>>> ___
>>> 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
> 
> 
> -
> E-Mail ist virenfrei.
> Von AVG überprüft - www.avg.de
> Version: 2015.0.6081 / Virendatenbank: 4392/10316 - Ausgabedatum: 27.07.2015 
> 
> 

-- 
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v2.0.22 (MingW32)

mQINBFNbSyEBEADh+uhohycnZgPPnyMs5pZQG6pKyLzFZoIKbVjY31ZoPZ2SdltB
elrwn6kFZkQiDx4K6nkZFHsPh8RMvWoFWg1rGiWkdsZessLFawraC8YEZDwtlaU5
SFXbE4+QnMfbPhe9tmC8Nbhec3dfV9zcXAhxc+zkIUsKFhSkpJ2Syvo9FCA/5adW
UZgWWKFwlSg4+/lrhJ6QJnldPlXfWcuEasKF7fjdafDIdS5hdKu8Lv+CiPQWvgsi
J2BDlZLzEZf3PD+NMujUbJa0nilD2ltu3/qRvR2f86YV6wRwt4E2OD8JJQOau4X2
Pg7vqkIbnB9rMiQ6T17rQ4rc80eesGCxQ6XOba9oa1eRRZDwY7HJtYwvPdw9HZaN
Lq2RRbGDGO0q7fxrzbp1WuNN+UXOA/pmVzWWczPfPHVcNIehGf3wQI+Vgh/

Re: Discrepancies with CLDR

[Fòram na Gàidhlig]

If in doubt, I would go with the CLDR, because that is what the CLDR is
for. Note that they have a new major release coming up soon, so maybe
best wait with any changes until that has gone through. If anybody of
the affected languages thinks that the CLDR data is wrong, I recommend
that you get involved with them, because their data will be used very
widely (glib, Wikipedia, Microsoft... just to name a few)



Sgrìobh Shaun McCance na leanas 26/07/2015 aig 22:17:
> Recently, I was working on updating the plural forms used inside
> yelp-xsl localization stylesheets. I looked two places to make sure I
> got things right: the Unicode CLDR project, and the PO files in gtk+.
> Usually they said the same thing, and I was happy. Sometimes they
> didn't, and that confuses me.
> 
> http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html
> 
> I'm sending that list of discrepancies in case it's something that needs
> to be followed up on. I'm not saying anybody's wrong or there's a bug. I
> just think the differences are curious.
> 
> am as bn gu hi kn mr pa si
> ==
> GTK+ says plurals=2; plural=(n != 1);
> CLDR says the singular includes 0
> (This is by far the most common discrepancy.)
> 
> br
> ==
> GTK+ says nplurals=2; plural=n > 1; (singular+zero, and plural)
> CLDR says 5 forms: one, two, few, many, other
> 
> cy
> ==
> GTK+ says nplurals=2; plural=(n==2) ? 1 : 0;
> CLDR shows 6 forms: zero, one, two, few (3), many (6), and other
> 
> dz
> ==
> GTK+ says nplurals=2; plural=(n!=1);\
> CLDR says one form
> 
> fa
> ==
> GTK+ says nplurals=1; plural=0;
> CLDR says two forms: singular+zero, and plural
> 
> he
> ==
> GTK+ says nplurals=2; plural= (n!=1);
> CLDR says four forms: one, two, many, other
> 
> is
> ==
> GTK+ says nplurals=2; plural=1;
> CLDR says two forms, but singular is n%10=1
> 
> lv
> ==
> GTK+ says nplurals=3;
>   plural=(n%10==1 && n%100!=11 ? 0 : n != 0 ? 1 : 2);
> CLDR says 3 forms: zero(%10), one(%10), and other
> 
> mk
> ==
> GTK+ declares one more form than it calculates:
> nplurals=3; plural= n==1 || n%10==1 ? 0 : 1
> This isn't the case in other mk.po files in GNOME, so this is probably
> just a type that should be corrected.
> 
> ms
> ==
> GTK+ doesn't have forms, so defaults to en rules
> CLDR says 1 form
> 
> tr
> ==
> GTK+ says nplurals=1; plural=0;
> CLDR says two forms: singular, and plural
> 
> 
> 
> ___
> 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: No commiter for Bosnian language

[Fòram na Gàidhlig]

You won't need a committer anymore, team coordinators can now submit
their translations to the repository from the Damned Lies interface.

You will still need somebody to help when creating a new translation
file for the documentation/help files, but the main software translation
can now be handled without a committer.

Welcome to GNOME :)



12/12/2014 10:01, sgrìobh ammar logicals:
> Hello I have asked about to create a  new team for Bosnian language. But
> the team coordinator contacted (samir.ri...@etf.unsa.ba)
>  me and he is still active, but by his
> message:
> 
> "Koordiniram, ali ne mogu da nađem commitera, tako da su svi prijevodi u
> translations.launchpad.net/bosnianuniversetranslations
> . Ako
> imate kakvih kontakta koji bi omogućili da se to pošalje na damnedlies
> servere, bilo bi dobro."
> 
> Yes I do coordinate, but I cannot find a commiter. so all translations
> are at (link). If you have any contacts who are able to send the files
> to damnedlies servers, that would be great.
> 
> 
> I would ask you to help us, with the commiter.
> It would be great if you could assign us a commiter, or make it one of us.
> 
> Thank you,
> 
> Ammar
> 
> 
> http://www-01.sil.org/iso639-3/documentation.asp?id=bos   (link for
> bosnian iso code)
> 
> 
> 
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-i18n
> 
> 
> 
> No virus found in this message.
> Checked by AVG - www.avg.com 
> Version: 2015.0.5577 / Virus Database: 4235/8721 - Release Date: 12/12/14
> 
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Script to convert ICU data into gettext po files

[Fòram na Gàidhlig]

I am publishing this to the list, because some translators might find it
helpful.

If you should ever happen upon a project where you have to translate a
long list of language, country or currency names etc, check out this script:

https://github.com/gunchleoc/ICU2po

It will convert ICU data into gettext po files

I wrote this for myself because I wanted to save myself from some
Repetitive Strain Injury due to excessive copy/pasting, so it comes
without warranty or support etc. The script is less than perfect and you
might need to do some more coding for your particular locale; I just
thought I'd share.
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Gimp and friends

[Fòram na Gàidhlig]

[1] should be the correct location.

You don't need git access - after setting the file to "Ready for
Submisstion", you should be able to "Submit to Repository".

For the help files, I think the file needs to be created in git first
before you can submit with Damned Lies.


14/11/2014 16:24, sgrìobh Hannie Dumoleyn:
> Hello,
> I am trying to commit Dutch translations of Gimp and friends, see [1],
> but I cannot find where to send them to. I cannot find them on [2]. I
> can clone gimp with the command git clone
> ssh://myn...@git.gnome.org/git/gimp, but git clone
> ssh://myn...@git.gnome.org/git/gimp-libgimp gives me an error [3].
> Can anyone tell me where to find the repository of Gimp and friends?
> Hannie
> 
> [1] https://l10n.gnome.org/languages/nl/gnome-gimp/ui/
> [2] https://git.gnome.org/browse/
> [3] Please make sure you have the correct access rights and the
> repository exists.
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-i18n
> 
> 
> -
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2015.0.5577 / Virus Database: 4213/8570 - Release Date: 11/14/14
> 
> 
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: where the string comes from

[Fòram na Gàidhlig]

09/11/2014 00:56, sgrìobh Jan Claeys:
> Baurzhan Muftakhidinov schreef op za 08-11-2014 om 19:20 [+0600]:
>> While using Nautilus with Kazakh l10n,
>> I notice that disk volumes are named
>> "20 GB Volume", in my case it looks like
>> "20 GB томы". So the unit (MB, GB) is not localized and
>> I couldn't find where it comes from.
>> I checked nautilus, glib, gvfs, udisks - no luck.
>>
>> So, where these units are translated?
> 
> Are you sure you want to "translate" these?  They are symbols defined by
> international standards...

... and translated in the CLDR

http://www.unicode.org/cldr/charts/26/summary/kk.html

MByte   МБайт
{0} MB  {0} MБ
{0} MB  {0} MБ

So, although I don't speak Kazakh, this is a definite "yes" :)
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: dealing with plural

[Fòram na Gàidhlig]

Looks correct to me, since your language only has 1 plural form
(msgstr[0]). You should be able to delete the line #msgstr[1] "" without
causing problems.

If PoEdit doesn't define the plural forms your your language correctly,
best contact PoEdit's author - he will fix this for future versions if
you let him know about the problem.


28/09/2014 17:26, sgrìobh Daniel Mustieles García:
> Not sure 100% if it is correct, but it seems to be. If msgfmt doesn't
> detect an error in that string, it should be ok.
> 
> 2014-09-28 8:38 GMT+02:00 Umarzuki Mochlis  >:
> 
> 2014-09-18 1:42 GMT+08:00 Daniel Mustieles García
> mailto:daniel.mustie...@gmail.com>>:
> >
> >> 2014-09-17 13:01 GMT-03:00 Daniel Mustieles García
> >> mailto:daniel.mustie...@gmail.com>>:
> >> > PoEdit usually breaks PO files headers... I'd recommend you to use
> >> > another
> >> > translation tool instead of PoEdit.
> >>
> >> By "break" you mean it breaks lines (in two, < 80 char per line), and
> >> not that it breaks (i.e. corrupts) PO files, right?  I never had such
> >> problem in POedit and I always used it without such problem.
> >
> >
> > No, I meant PoEdit sometimes corrupts files, specially with plural
> forms.
> > Maybe it happened with earlier versions and it has already been
> fixed, but I
> > started using Gtranslator and I've never used PoEdit again.
> >>
> >>
> >>
> >> Cheers,
> >> Rafael Ferreira
> >
> >
> 
> thanks
> 
> I set plural forms as
> "Plural-Forms: nplurals=1; plural=0;\n"
> 
> the I checked it with msgfmt
> 
> $ msgfmt -c
> Documents/gnome312-translating/gnome-control-center.master.ms.po
> Documents/gnome312-translating/gnome-control-center.master.ms.po:5:
> nplurals = 1...
> Documents/gnome312-translating/gnome-control-center.master.ms.po:4106:
> ...but some messages have 2 plural forms
> msgfmt: found 1 fatal error
> 
> I rectfied this by
> 
> msgid "%i day ago"
> msgid_plural "%i days ago"
> msgstr[0] ""
> #msgstr[1] ""
> 
> is this the correct way to do it?
> 
> 
> 
> 
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-i18n
> 
> 
> 
> No virus found in this message.
> Checked by AVG - www.avg.com 
> Version: 2014.0.4765 / Virus Database: 4025/8287 - Release Date: 09/28/14
> 
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Incorrect translations of gsettings schema key's localised default value

[Fòram na Gàidhlig]

> On Tue, 2014-09-23 at 20:31 +0200, Christian Persch wrote:
>> #: ../src/org.gnome.Terminal.gschema.xml.h:1
>> msgctxt "visible-name"
>> msgid "'Unnamed'"
>>
>> Here, the single-quotes around the string are essential, and *must* be
>> reproduced in the translated string
> 
> Please add a translator comment so translators could know. See
> https://wiki.gnome.org/TranslationProject/DevGuidelines/Use%20comments
> 
> andre

+1

BTW the module the string is in is:

https://l10n.gnome.org/module/gnome-terminal/
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Do we need to repeat key search terms in translation

[Fòram na Gàidhlig]

> #. Translators: those are keywords for the sound control-center panel
> #: ../panels/sound/data/gnome-sound-panel.desktop.in.in.h:4
> msgid "Card;Microphone;Volume;Fade;Balance;Bluetooth;Headset;Audio;"
> 
> Do I need to add the original English terms to the translated keywords
> in Bulgarian in order to allow the user when using Bulgarian locale to
> also be able to search using terms in English?

Yes.



> Are English originals included in search by default or do I need to add
> them by hand?

The search matches all keywords you give them in that translation above,
no matter in which language they actually are.
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Screenshot automation BoF at GUADEC

[Fòram na Gàidhlig]

14/07/2014 16:43, sgrìobh Alexandre Franke:
> Hi,
> 
> It's 2014 and translators and documentation writers still have to
> spend a lot of time to manually create screenshots. There must be a
> better way. Therefore I'm planning a half-day BoF on this topic at
> GUADEC.

There is a GSoC project @ Wikimedia on the subject - might be of
interest to you

https://www.mediawiki.org/wiki/User:Vikassy/GSoC14
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: GNOMECAT and Damned Lies Integration.

[Fòram na Gàidhlig]

I don't really get what GNOMECAT is supposed to do and what features you
are planning. Here are some thoughts from the top of my head - please
ignore naything that is not within the scope of what you are doing /
able to do in the time you have to work on this:

- Damned Lies now allows committers to submit to the repository, so the
big Git hurdle is gone. So, for me personally, Damned Lies already does
everything that I need. My language has a very small team though, so we
never have more than 1 person working on the same module, and we can
easily send eah other stuff manually. What other teams might find
beneficial though was if there were more tools for coperating. Mind that
some of these ideas might be too big for a single GSoc project.

- Some form of collaborative editor

- For each language, a global translation memory for all modules

- Fuzzy matches for the translation memory for all modules

- For each language, a global glossary that any translator can add to.

Of course, any of these features, except for the fuzzy matches could be
achieved by using the Transifex platform, which is free for Open Source
projects. I don't know if everybody would be comfortable with that
though for philsophical reasons - and pushing the data back to the
repository might be a problem.



03/05/2014 22:23, sgrìobh Gil Forcada:
> Hi Marcos,
> 
> TL;DR; go for it!
> 
> Anything that eases the translators workflow is always welcome!
> 
> As for suggestions/criticism:
> - don't try to fill the complete gap but instead go step by step[1]
> - fix problems at the right level, i.e. make GNOMECAT be able to push
> translations maybe is a bit too much, and Damned-Lies is already able to
> push them, so instead of having to do some git magic, just upload the
> file to Damned-Lies and order it to push the translation
> - make it as easier as possible to test it while you develop: i.e. your
> target audience is translators so the easier you make them to install
> and try your application, the faster you will get feedback and users
> will be more happier :)
> - I could go here and ask for ponies, but first get the basic workflow
> right and later we can improve it and add more on top of it
> - as a personal nitpick: change the name please, as the Catalan
> translation coordinator, whenever I see GNOMECAT I read "GNOME
> Catalan" :D
> 
> It's so great to have you again as a GSOC!!
> 
> Cheers,
> Gil
> 
> [1] So make small milestones that in themselves are already useful so
> that if you do not reach the final goal, all the way leading to it is
> still useful. Something like:
> - allow to enter Damned-Lies credentials
> - be able to pick a module to translate
> - be able to submit to Damned-Lies a translation
> 
> El ds 03 de 05 de 2014 a les 20:25 +0200, en/na Marcos Chavarría
> Teijeiro va escriure:
>> Hi all,
>>
>> I'm Marcos Chavarría, the creator of GNOMECAT [1][2]. This application
>> has been created during last summer as part of GSoC program and It
>> should be finished this summer (I've got selected again :D).
>>
>> I know that what I'm going to tell you here is some kind of castles in
>> the sky because the basic features of the app are not finished yet but
>> I pretend to present this idea as a project to apply as collaborating
>> student at Igalia [3].
>>
>> I realize that the workflow for translator in GNOME is kind of
>> tedious. You have to go to the Damned Lies platform view what modules
>> are assigned to you, download the po file, use an external program to
>> translate it and then the file has to be uploaded using the Damned
>> Lies platform again. If you are reviewer or a committer it's even more
>> tiresome because you also have to deal with git (in fact Fran Dieguez
>> who is the Galician team coordinator has created some tools to make
>> this easier [4]).
>>
>> My idea consists on integrate Damned Lies with GNOMECAT. So you will
>> be able to download your assigned modules directly from the program,
>> upload the files without opening damned lies website and even commit
>> the translations to the module repository easier.
>>
>> I would like to ask both translators and Damned Lies developers that
>> are subscribed to this list, their opinion about this idea. Any idea,
>> critic or question is really welcome.
>>
>> Best Regards,
>> Marcos Chavarría Teijeiro.
>>
>>
>> [1] https://github.com/chavaone/gnomecat
>> [2] http://aquelando.info/categoria/informatica/gsoc/
>> [3] 
>> http://www.igalia.com/nc/igalia-247/news/item/opportunities-for-students-at-igalia+/
>> [4] https://github.com/frandieguez/gnome-l10n-tools
> 
> 
> 
> 
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-i18n
> 
> 
> 
> -
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4570 / Virus Database: 3931/7436 - Release Date: 05/03/14
> 
___
gnome-i18n mailing list
gnome-i18n@g

GTK+ what is a popover?

[Fòram na Gàidhlig]

Hi all,

I am stuck trying to translate the word popover, because I have no idea 
what it means. I'm leaving it in English for now.


Web search only gives me definitions à la "light, hollow roll made from 
an egg batter similar to that of Yorkshire pudding, typically baked in 
muffin tins or dedicated popover pans, which have straight-walled sides 
rather than angled." *lol*


Has anybody had any inspiration for this so far, and what do the things 
look like?

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Error message while submitting to repository

[Fòram na Gàidhlig]

I just got another error in a different module:

https://l10n.gnome.org/vertimus/gcompris/master/po/gd

An error occurred during applying your action: The commit failed. The 
error was: '[Errno 1] To ssh://git.gnome.org/git/gcompris 
a774ddf..b387cbe master -> master ! [rejected] gcomprixogoo -> 
gcomprixogoo (non-fast-forward) error: failed to push some refs to 
'ssh://git.gnome.org/git/gcompris' To prevent you from losing history, 
non-fast-forward updates were rejected Merge the remote changes (e.g. 
'git pull') before pushing again. See the 'Note about fast-forwards' 
section of 'git push --help' for details. '




05/02/2014 12:02, sgrìobh Fòram na Gàidhlig:

While trying to submit this translation to the repository:

https://l10n.gnome.org/vertimus/gtk+/master/po-properties/gd

I got the following error message:

An error occurred during applying your action: The commit failed. The
error was: '[Errno 1] remote: translations user cannot modify
'po-properties/gd.po' To ssh://git.gnome.org/git/gtk+ ! [remote
rejected] master -> master (pre-receive hook declined) error: failed to
push some refs to 'ssh://git.gnome.org/git/gtk+' '

I have submitted other stuff, so I guess it has to do with project
permissions?

Which module do I report the bug on?
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n


-
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4259 / Virus Database: 3684/7062 - Release Date: 02/04/14



___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Error message while submitting to repository

[Fòram na Gàidhlig]

While trying to submit this translation to the repository:

https://l10n.gnome.org/vertimus/gtk+/master/po-properties/gd

I got the following error message:

An error occurred during applying your action: The commit failed. The 
error was: '[Errno 1] remote: translations user cannot modify 
'po-properties/gd.po' To ssh://git.gnome.org/git/gtk+ ! [remote 
rejected] master -> master (pre-receive hook declined) error: failed to 
push some refs to 'ssh://git.gnome.org/git/gtk+' '


I have submitted other stuff, so I guess it has to do with project 
permissions?


Which module do I report the bug on?
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Submitting translations through l10n.gnome.org

[Fòram na Gàidhlig]

Thank you, this ROCKS!


01/02/2014 09:57, sgrìobh Claude Paroz:

Hi dear translators,

I'd like to share a good news: it is now possible to submit translations
to GNOME Git server through the l10n.gnome.org Web interface.

Basically, when a translation file has been uploaded and has the status
of "Ready for submission", any team member with status of committer or
coordinator should see a new option "Submit to repository". This action
takes the last uploaded file and commits it to git.gnome.org.

Please report any issue either here or on GNOME bugzilla.
https://bugzilla.gnome.org/browse.cgi?product=damned-lies

As with all new features, we can expect some rough edges in the start.
Thanks to all people involved in making this happen, at last!

Cheers,

Claude


___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Scottish Gaelic translations to commit

[Fòram na Gàidhlig]

Thanks!

Maybe I should become a coordinator first, to make it easier for whoever 
then has to look at my comitter application. we would like to have 2 
coordinators on the Scottish Gaelic team, akerbeltz and me. I would then 
apply for commit access, because I'm more techy.


What do need to do to become second coordinator? Where do I apply?



22/01/2014 20:38, sgrìobh Piotr Drąg:

2014/1/22 Fòram na Gàidhlig :

I work closely with the team coordinator and we were just scratching our



heads together on how to get our work actually used. You can consider us



both as team coordinator, although only one of us can get the official title
it seems. So, yes, he agrees. I imported a bunch of translations we did for
Ubuntu together back in September, and he's currently working on Gimp.

Thanks for your help, and here's the list. Please ignore the Inactive status
on some of them, that was just us fiddling trying to get the translations
in. All these links have files to commit in them.



I've committed most of these, with the exception of gtk-engines
(obsolete module) and xdg-user-dirs (it needs to go through the
Translation Project). I'm happy to help if you have more files to
commit, but I'm sure you can get the commit access for yourself at
this point.

Best regards,


___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Scottish Gaelic translations to commit

[Fòram na Gàidhlig]

21/01/2014 17:29, sgrìobh Gil Forcada Codinachs:

Usually the best way to get your translations in git is to make your
language coordinator send an email to this list with the links to the
translations ready to commit.

If the team coordinator says so, anybody with git access can push the
translations. That's usually my only concern when pushing translations
from other languages: that the team coordinator agrees on pushing them.

Cheers,
Gil


I work closely with the team coordinator and we were just scratching our 
heads together on how to get our work actually used. You can consider us 
both as team coordinator, although only one of us can get the official 
title it seems. So, yes, he agrees. I imported a bunch of translations 
we did for Ubuntu together back in September, and he's currently working 
on Gimp.


Thanks for your help, and here's the list. Please ignore the Inactive 
status on some of them, that was just us fiddling trying to get the 
translations in. All these links have files to commit in them.


https://l10n.gnome.org/vertimus/brasero/master/po/gd
https://l10n.gnome.org/vertimus/gcompris/master/po/gd
https://l10n.gnome.org/vertimus/gimp/master/po/gd
https://l10n.gnome.org/vertimus/gnome-keyring/master/po/gd
https://l10n.gnome.org/vertimus/gnome-nettool/master/po/gd
https://l10n.gnome.org/vertimus/gnome-online-accounts/master/po/gd
https://l10n.gnome.org/vertimus/gnome-screenshot/master/po/gd
https://l10n.gnome.org/vertimus/gnome-session/master/po/gd
https://l10n.gnome.org/vertimus/gnome-system-log/master/po/gd
https://l10n.gnome.org/vertimus/gnome-system-monitor/master/po/gd
https://l10n.gnome.org/vertimus/gtk-engines/master/po/gd
https://l10n.gnome.org/vertimus/libgnome-keyring/master/po/gd
https://l10n.gnome.org/vertimus/eog/master/po/gd
https://l10n.gnome.org/vertimus/gnome-desktop/master/po/gd
https://l10n.gnome.org/vertimus/gnome-doc-utils/master/po/gd
https://l10n.gnome.org/vertimus/gnome-font-viewer/master/po/gd
https://l10n.gnome.org/vertimus/gnome-icon-theme/master/po/gd
https://l10n.gnome.org/vertimus/gnome-menus/master/po/gd
https://l10n.gnome.org/vertimus/gnome-power-manager/master/po/gd
https://l10n.gnome.org/vertimus/gnome-screensaver/master/po/gd
https://l10n.gnome.org/vertimus/gnome-session/master/po/gd
https://l10n.gnome.org/vertimus/gparted/master/po/gd
https://l10n.gnome.org/vertimus/Gtk-properties/master/po-properties/gd
https://l10n.gnome.org/vertimus/Gtk-UI/master/po/gd
https://l10n.gnome.org/vertimus/libwnck/master/po/gd
https://l10n.gnome.org/vertimus/network-manager-applet/master/po/gd
https://l10n.gnome.org/vertimus/PolicyKit-gnome/master/po/gd
https://l10n.gnome.org/vertimus/totem/master/po/gd
https://l10n.gnome.org/vertimus/totem-pl-parser/master/po/gd
https://l10n.gnome.org/vertimus/xdg-user-dirs/master/po/gd
https://l10n.gnome.org/vertimus/yelp/master/po/gd
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Could someone please commit a new Swedish translation of bijiben

[Fòram na Gàidhlig]

We actually have the same problem with Scottish Gaelic. We have a big 
number of translations just catching mold and not making it into git, 
which is very frustrating. The Irish committer used to help us, but he 
hasn't been around for a while.


I applied for commit access once and was ignored, would it be worth my 
time to try & apply again?





20/01/2014 22:04, sgrìobh Rafael Ferreira:

I will commit for you.


2014/1/20 Göran Uddeborg mailto:goe...@uddeborg.se>>

I just forwarded an updated translation of bijiben to the "to commit"
state.  But since there is noone in the Swedish team who has commit
rights, I need to ask for help to get it from there.  Could anyone do
that?
___
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



No virus found in this message.
Checked by AVG - www.avg.com 
Version: 2014.0.4259 / Virus Database: 3681/7021 - Release Date: 01/21/14


___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Importing strings from Launchpad

[Fòram na Gàidhlig]

I have the approval of the contributors, so that's not a problem.

I actually got an error message while trying to upload (don't remember 
what it was), so I did a manual msgmerge. It turned out to be the better 
option anyway, because some strings came up fuzzy and I could fix them 
before the upload.




16/09/2013 23:33, sgrìobh Kenneth Nielsen:

However, if you know all the contributors, then with most "more liberal"
licenses it should be possible to relicense, for which you just need the
approval of the contributors.


2013/9/16 Andika Triwidada mailto:and...@gmail.com>>

On Tue, Sep 17, 2013 at 2:44 AM, Claude Paroz mailto:cla...@2xlibre.net>> wrote:
 > Le dimanche 15 septembre 2013 à 08:37 +0100, Fòram na Gàidhlig a
écrit :
 >> I will have a whole bunch of packages translated soon that we did on
 >> Launchpad. Can I just upload these as they are to Damned Lies
and then
 >> take use those merges to care of the fuzzy strings (my preferred
 >> option), or do I need to grab the empty packages from Damned
Lies first
 >> and run the msgmerge myself (takes a lot longer)?
 >
 > Yes, you can™ :-)
 > Try and experiment, then please report your findings.
 >
 > Claude


If I remember correctly, LP translation might have different license
to GNOME.
GNOME's translation can go to LP but not every LP's can directly go
to GNOME?

Regards,
Andika
___
gnome-i18n mailing list
gnome-i18n@gnome.org <mailto: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


___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Importing strings from Launchpad

[Fòram na Gàidhlig]

I will have a whole bunch of packages translated soon that we did on 
Launchpad. Can I just upload these as they are to Damned Lies and then 
take use those merges to care of the fuzzy strings (my preferred 
option), or do I need to grab the empty packages from Damned Lies first 
and run the msgmerge myself (takes a lot longer)?

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Web interface for translation for GNOME

[Fòram na Gàidhlig]

I like the Transifex interface; they have come a long way. 
Workflow-wise, I have identified one serious problem though: Wile 
changing a translation I had previously approved (I am susually my own 
proofreader, because there are only 2 people on the planet who localize 
into Scottish Gaelic for OS software), the string still stayed approved 
instead of going back on the "to proofread" list. So, we'd better sick 
to DL or run our own pootle server.


And going a bit off topic, I would very much appreciate if somebody 
could approve my request to be a committer that I filed quite a few 
weeks ago. As I said, there are only 2 people on this planet for the 
job, and if I don't get access, who will commit my translations? Whom do 
I contact?




30/08/2013 16:48, sgrìobh Daniel Mustieles García:


As a co-ordinator for Gujarati language I would also want to review or
commit translations easily without having a hassle. Of course I need
handful of resources to review or assess translation quality. How would
you do that off-line? Even if I have those offline today, it might get
lost when team changes, members changes, co-ordinators changes. So,
having an online resource in-built on the web translation tools makes it
consistent.


Using DL you cann see differences between git's PO file and the uploaded
one, so review is not a problem. Translation memory can be easily and
used with Gtranslator, and glossary is something that each
translator/translation team must do itself.




Also, we have several roles: translator, proofreader and commiter.
Hiding GNOME's infraestructure to plain translators may avoid
them grow
up and acquire knowledge about how translations workflow works. If I
have a lot of translators but have no proofreaders nor commiters,
workflow will be slower, and the number and the quality of the
translations will fall down.


Workflows followed here are for technical people, but not for
translators, not for language experts or linguists who can give you the
best quality translations. If you have lot of translators you should
have proofreaders or committers.


I disagree. The workflow using in DL is really simple. Just create an
account, join a team download a PO file, translate a upload it. AFAIK,
Trasinfex is pretty similar to this workflow.

Also, note that many of the GNOME translators aren't linguists nor
language experts. They are people that use and know about GNU/Linux and
GNOME and want to collaborate with it. I always recommend to translators
the same: "first use it and then, translate it". We use a very specific
language in our software, so we need people with technical background.
Of course, they must have grammar skills, but if they don't know what a
repository, an slider or a buffer is, they will have serious problems to
translate most of the GNOME modules.

Note that reaching the role of proofreader or commiter takes a long time
(at least in the Spanish team). To be a good proofreader, you first have
to translate without fails, and it takes time. Also note that people
sometimes gets tired of translations and magically dissapear (including
proofreaders).




In the other hand, it has also benn commented above, Transifex
doesn't
work directly with the repo, so statistics are not reliable.


As long as the translations are synced by the developers you should get
the accurate stats. Not part of translators job to worry about.


No. Translators need to manage their translations, so they need to have
real-time updated statistics. Developers have to develope, and don't
worry about commiting translations. I've used Transifex in several
projects and I never know what happens with my translations. Are they
commited into the repository, are they queued, have been rejected? Same
case with projects managing translations with bugzilla. Reports can be
waiting review for months...

We are disussing about using an external tool to manage our
translations, and it has derived in a discussion about workflow, which
is something special for each team, but we are missing something I think
is really important. How should we use Transifex? I mean, is it a free
software that we can install and configure in a GNOME server or it's an
external service? How customizable is it? Personally, I would not like
to delegate our translation statistics and web interface in an external
tool...




DL is good for me, and we can also improve it if we consider it's
missing any feature, so +1 to DL.


If DL has online translation features, +1 from me as well.


Best regards


Thanks
--
Regards,
Ankit Patel
http://www.ankit644.com/
http://fuelproject.org/__gilt2013/index


_
gnome-i18n mailing list
gnome-i18n@gnome.org