- openSUSE Translation

[opensuse-translation] Outdated .pot file
by Luigi Baldoni 29 Sep '15

29 Sep '15

trunk/lcn/50-pot/scout.pot is outdated. Since the only difference from https://github.com/openSUSE/scout/blob/master/i18n/scout/scout.pot is a typo correction (retreive->retrieve) and since the newer svn translations would have to be merged back to github, I was wondering if it would be possible to correct it on the fly without having to involve the translator for every locale. Regards -- View this message in context: http://opensuse.14.x6.nabble.com/Outdated-pot-file-tp5047798.html Sent from the opensuse-translation mailing list archive at Nabble.com. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-translation+owner(a)opensuse.org

5 7

[opensuse-translation] svn account request
by Mariusz Fik 20 Sep '15

20 Sep '15

Hello! I'm taking over a coordination of Polish localization team, so please create svn.opensuse.org account for me. -- Greetings, Mariusz Fik -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-translation+owner(a)opensuse.org

2 2

[opensuse-translation] Process for Translating for landing page (the old one / current one)
by Manu Gupta 17 Sep '15

17 Sep '15

Hi I am one of the volunteers for the openSUSE.Asia team, and we are trying to get some text on the landing page about openSUSE.Asia Summit to spread the word. I have no experience related to translation, so can anyone help me in walking through the process of translation for the landing page. We have the original string in English, so where can we request the strings to be translated. Thank you for your patience!!!! -- Regards Manu Gupta -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-translation+owner(a)opensuse.org

6 14

Re: [opensuse-translation] Steps for creating Spanish variants?
by Carlos E. R. 11 Sep '15

11 Sep '15

On 2015-09-11 00:38, Gabriel [SGT] wrote: > -Carlos, sorry if I cc'd you, but I believe the list will reject this > mail and I don't have another client at hand. I you could forward it, > that would be great, thanks! Done! > ----- > Javier, as I said in the spanish list, if the propose is to create an > es-ES variant, we already agreed it's ok, but the default 'es' should be > kept as is. Users looking for a Spain spanish version will know what to > choose, and for those without an specific version, we must provide a > neutral/standard/international version, and that will be 'es' as nowadays. It appears that technically, there is a locale available named 'es' which is for "neutral Spanish". Thus, the current branch should be renamed 'es', and a new one added for 'es_ES'. Of course, YaST must also know how to label the variants. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-translation+owner(a)opensuse.org

1 0

[opensuse-translation] Steps for creating Spanish variants?
by Javier Llorente 10 Sep '15

10 Sep '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, The Spanish translation team has decided* to split the translations into two variants: - - Castilian Spanish: es_ES (decided). I think we could start with this one. - - Latin American Spanish: es_LAT or a specific one, such es_AR (to be decided by them). What are the next steps? Greetings, - -- Javier Llorente *Thread: http://lists.opensuse.org/opensuse-translation-es/2015-08/msg00000.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlXp+DsACgkQdV3zWWOPFxTvLQCcDUN0o1kDxKtx232ykUvLj1yn WDQAmgMLVZUun6UOggY6nSQmz9DTVz5y =W+NR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-translation+owner(a)opensuse.org

7 19

R: Re: [opensuse-translation] Steps for creating Spanish variants?
by emiliano.m＠inwind.it 10 Sep '15

10 Sep '15

Dear Javier mayve had a misunderstonding Venetian language is used in Veneto, the area arount Venice this is the detail of the language http://www-01.sil.org/iso639-3/documentation.asp?id=vec) I thin that is not easy to do a version where the frame different are more than 80% ciao Emiliano >----Messaggio originale---- >Da: javier(a)opensuse.org >Data: 10/09/2015 22.58 >A: <opensuse-translation(a)opensuse.org> >Ogg: Re: [opensuse-translation] Steps for creating Spanish variants? > >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >On 10/09/15 22:44, Javier Llorente wrote: >> On 09/09/15 19:39, Carlos E. R. wrote: >>> On 2015-09-09 19:01, Karl Ove Hufthammer wrote: >>>> Den 07. sep. 2015 19:10, Carlos E. R. skreiv: >> >> >>>>> Because the variant they want to create is es-ES, which till >>>>> now was the generic one, and now would be the specific for >>>>> Spain. >> >>>> Am I correct in assuming that the current translation is in >>>> what’s sometimes called ‘neutral Spanish’ or ‘Standard >>>> Spanish’? See >> >>>> http://blog.globalizationpartners.com/what-is-neutral-spanish.aspx >>>> >>>> >> >>>> >https://en.wikipedia.org/wiki/Standard_Spanish >> >>> I was not aware of the definition, but yes, indeed, that was our >>> goal when we started several years ago. >> >>>> For example, if it actively tries to avoid using words and >>>> expression only used in certain Spanish-speaking countries >>>> (e.g. Spain), plain ‘es’ is certainly the right language code, >>>> and the translation would be appropriate for many es_* >>>> locales. >> >>> Well, yes. The current translation should be 'es', and the new >>> branch would be "es_ES". >> >> I think it's a good option; "es" for those who want to keep using >> the same translation style and "es_ES" for those who want to >> translate it into Castilian Spanish. We would need to use an extra >> word on menus; Spanish (neutral), Spanish (Spain) or Neutral >> Spanish, Castilian Spanish, for example. > >That said, I think that "es" is going to end up being "neutral" Latin >American Spanish, since I don't think that many European Spanish >translators would translate the distribution into "neutral Spanish" >having their own variant, Castilian Spanish. >"International Spanish" is a better choice for "es", isn't it? > >Greetings, >- -- >Javier Llorente >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v2 > >iEYEARECAAYFAlXx7tsACgkQdV3zWWOPFxThbwCghPUNgXwhc2ros4vD23z7XlRz >I+sAnArOoqypovIR7rd2OZLptUkHhjru >=X8GT >-----END PGP SIGNATURE----- >-- >To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org >To contact the owner, e-mail: opensuse-translation+owner(a)opensuse.org > > -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-translation+owner(a)opensuse.org

1 0

[opensuse-translation] Some languages requires merge in trunk
by opensuse.lietuviu.kalba 09 Sep '15

09 Sep '15

Hi, Noticed, that some languages are not merged (e.g. Lithuanian, as seen in http://i18n.opensuse.org/stats/trunk/lt/yast/index.php ), while others are up-to-date (e.g. French, as seen in http://i18n.opensuse.org/stats/trunk/fr/yast/index.php) Can someone please update all po files? -- Regards, Mindaugas -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-translation+owner(a)opensuse.org

3 4

[opensuse-translation] Statistics of translations for SLE12-SP1
by Freek de Kruijf 28 Aug '15

28 Aug '15

Currently there are no statistics of translations for SLE12-SP1 on i18n.opensuse.org. Is it possible to add these? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-translation+owner(a)opensuse.org

2 1

[opensuse-translation] [trunk/yast] services-manager.pot outdated?
by Antoine Belvire 27 Aug '15

27 Aug '15

Hello, services-manager.pot looks outdated to me. Strings from the software are missing or are commented ("start", stop", "active", "inactive", …) Could the maintainer please take a look at it? Regards, Antoine -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-translation+owner(a)opensuse.org

6 11

[opensuse-translation] Leap roadmap for translation + integration of SLE 12 SP1 ?
by locnar＠gmx.com 17 Aug '15

17 Aug '15

Dear fellow translators and l10n team, As you are probably aware of, additional details on the development roadmap for Leap 42.1 have been released last week : https://news.opensuse.org/2015/08/11/second-milestone-expected-soon/ It is expected that : > Leap’s Beta release will follow Milestone 2 on Sept. 24, which will freeze the version and only major, critical and blocker bugfixes will be allowed. > > “If someone is missing a package or a version update, now is a good time to see what needs to be done,” Kulow said. “After mid-September, Leap is basically frozen.” > > An important date people should be aware of is Sept. 20 because that is the freeze point for items to be included in the Beta and Leap. Also : > The RC1 release will be Oct. 15 and the Goldmaster is scheduled for Oct. 30, so translations, release notes and localization of the release should be completed by Oct. 30. As far as I know, string freeze typically occurs around milestone 3 or beta (in the historical development scheme). Assuming this remains unchanged, string freeze would occur around September 24th, kicking off the work of the translation team. RC1 will be available on the 15th, and final translations should be committed by October 30th latest. Basically - assuming I am understanding properly - translation should start at the end of September, be almost finished for mid-october, and be reviewed, adjusted and eventually committed no later than October 30th. It would be very much appreciated should anyone confirm or adjust these milestones for translation. In addition, does anybody have a clue on when a new branch for Leap 42.1 is due in subversion and vertaal? The news also states the following : > “We have to sync with Factory changes and SLE 12 SP 1 changes,” Kulow said about the roadmap for Leap. “We will not be able to align with SP1 completely. We will have to release maintenance updates.” > > Most of the things SUSE does for polishing its SPs will need to be released as an online update because SLE SP1 has a different schedule than Leap, he said. > > “People can start producing maintenance updates for Leap” in the form of patches beginning Oct. 1, said Richard Brown, chairman for openSUSE. To which extent is this expected to have an impact on the translation? Should we address some packages in priority and disregard others? How translations will (or not) be taken aboard maintenance updates for SP1? Less specifically, how is it foreseen to integrate translations for components available from SLE into Leap and is this likely to require manual interventions from translators? I admit that it may be a bit early to have answers to such questions, but the translation timeframe is short and deadlines are tight. I take this opportunity to thank everyone again for her/his hard work on Leap, I can't wait to discover Leap 42.1. Best of luck to everyone and... Have a lot of fun! ;-) //Sylvain -- To unsubscribe, e-mail: opensuse-translation+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-translation+owner(a)opensuse.org

4 3