http://blog.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/6018 <pre>Hi All is translation session for: http://ask.libreoffice.org still valid? I can see the files in Pootle. I think this is a great step to the new way of support, which allows all local communities to work in a better way. Ciao </pre> Valter Mura 2013-05-20T18:08:32 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/6016 <pre>I had my periodic news scour today - heatwave in Glasgow, 21°C, too hot to do any hard work ;) - including the progress of the ports to Cloud/Android/iOS. Before anyone gets excited, I have no news, just a question and no, it's not about "when is it coming" either! I was just wondering whom I should contact to make sure this doesn't fall foul of force-locale issues (especially on Android and iOS where many locales are not supported) when it does happen. It may be that it has already been considered and a manual selection planned (LO is normally very good at l10n support so I am actually hopeful) but I'd hate for this issue to be overlooked by accident. Anyone know a good contact who kind of straddles both the port projects and l10n? Michael </pre> Michael Bauer 2013-05-20T12:07:11 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/6012 <pre>Hi I removed a previous version and installed LibreOffice version 4.0.2.2 on Linux Ubuntu 10.04 from ppa:libreoffice/libreoffice-4-0. I also installed the Esperanto language pack (libreoffice-l10n-eo). The spell checker works for Esperanto. In ordinary tables the sort order (Tools &gt; Sort...) works correctly. I am editing a translation of the user guide GS4002-SettingUpLibreOffice.odt. I created an alphabetical index at the end of the document to check that I had translated all the anchors and cross-references. It sorts the entries into a wrong order. The document language is set to Esperanto and the language of the index is set to Esperanto. Here is an extract from the last part of the index. Note that ĝ should go after g, ŝ after s. Why do they, and presumably other accented letters, go between v and x? tiparo anstataŭigoj 13 aspekto 8 historio 8 tondejo 9 vortarojn instali 25 ĝenerale apriora dosiera formato ODF-formato, versio de 21 OpenDocument Format 21 Optimumigi la grandon 21 Ĉiam konservi kiel 21 Apriora dosiera formato kaj ODF-agordoj 21 AŭtomataRiparo 21 Konservi informon pri Aŭtomata Riparo post ĉiu__Minutoj 21 Konservi URL-ojn relative al dosiera sistemo / Interreto 21 Redakti dokumentajn atributojn antaŭ konservado 20 Ĉiam krei restaŭran kopion 21 Ŝargi presilajn agordaĵojn kun la dokumento 20 Ŝargi proprajn agordaĵojn kun la dokumento 20 Ŝargi/Konservi Konservi originan Basic-kodon 22 Microsoft Office-dosierokonvertado 22 Rulebla kodo 22 Tiparaj grandoj 24 VBA-atributoj, ŝargi/konservi 22 Ŝargi Basic-kodon 22 XML-dosieroj Do other languages have this problem? Is it to do with the locale definition? (If so why does it sort ordinary tables correctly?) Regards Donald Rogers </pre> Donald Rogers 2013-05-19T02:31:20 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/6005 <pre>Hi, LibreOffice 4.1 is approaching. In order to reduce the amount of translation work, I would like to smartly migrate 4.0 translations to 4.1 in Pootle. Many source code changes happened, including the transition from .src format dialogs to .ui format dialogs. Hopefully old translations can be leveraged in high proportion. That means that you'll have less to translate and you will not have to translate things that you already have done. This will happen sometimes next week. At the same time 3.6 translations will be removed from Pootle in order to save resources. 4.0 and 4.1 will be there. Best regards, Andras </pre> Andras Timar 2013-05-17T07:23:46 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/6004 <pre>Hi Someone know why file -&gt; http://dev-builds.libreoffice.org/pre-releases/deb/x86/LibreOffice_4.1.0.0.alpha1_Linux_x86_deb.tar.gzhave all languages? </pre> Konrad K. 2013-05-14T19:02:54 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/6002 <pre>I see that Azerbaijan language has only one project. Can I add another projects there and what should I do if I can? Now I cannot translate anything and I don't see the team lead. P.S. I use pootle. </pre> Paul Zercky 2013-05-13T22:22:32 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/5994 <pre>Hi folks, Is it a way to test localization from pootle files? Or do you test only release candidate versions? Instruction is needed for linux, but for windows OSes would be fine as well. Sorry if it's the silly question. </pre> Коростіль Данило 2013-05-09T14:54:16 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/5985 <pre>I suspect we (galician) have a bug in Calc If I have a list of data in a text file items as 19 Abr, 2013 21 Abr, 2013 20 Mai, 2013 6 Xuñ, 2013 8 Ago, 2013 26 Ago, 2013 26 Ago, 2013 26 Ago, 2013 22 Set, 2013 1 Xan, 2014 23 Xan, 2014 27 Xan, 2014 31 Xan, 2014 14 Feb, 2014 15 Mar, 2014 11 Mai, 2014 and I paste it on Calc, this results 19 Abr, 2013 21 Abr, 2013 20 Mai, 2013 6 Xuñ, 2013 8 Ago, 2013 26 Ago, 2013 26 Ago, 2013 26 Ago, 2013 22 Set, 2013 1 Xan, 2014 23 Xan, 2014 27 Xan, 2014 31 Xan, 2014 14/02/14 15/03/14 11 Mai, 2014 Obviously is incorrect. If somebody compares with month names in english 19 Apr, 2013 21 Apr, 2013 20 May, 2013 6 Jun, 2013 8 Aug, 2013 26 Aug, 2013 26 Aug, 2013 26 Aug, 2013 22 Sep, 2013 1 Jan, 2014 23 Jan, 2014 27 Jan, 2014 31 Jan, 2014 14 Feb, 2014 15 Mar, 2014 11 May, 2014 Results correctly 19/04/13 21/04/13 20/05/13 06/06/13 08/08/13 26/08/13 26/08/13 26/08/13 22/09/13 01/01/14 23/01/14 27/01/14 31/01/14 14/02/14 15/03/14 11/05/14 I have perfoms various test with spanish, portuguese, diferents formats (with dot, uppercase...) This problem is no related with auto fill cells in galician. In fact if I introduce xan feb and extend the autofill lists in the sheet (Tools→Options→LibreOffice Calc→ Sort lists) results xan feb Mar Abr Mai Xuñ Xul Ago Set Out Nov Dec Xan (correct) Working correctly even if the calc interface is set in english Compare Portuguese 19 Abr, 2013 21 Abr, 2013 20 Mai, 2013 6 Jun, 2013 8 Ago, 2013 26 Ago, 2013 26 Ago, 2013 26 Ago, 2013 22 Set, 2013 1 Jan, 2014 23 Jan, 2014 27 Jan, 2014 31 Jan, 2014 14 Feb, 2014 15 Mar, 2014 11 Mai, 2014 or Spanish 19 Abr, 2013 21 Abr, 2013 20 May, 2013 6 Jun, 2013 8 Ago, 2013 26 Ago, 2013 26 Ago, 2013 26 Ago, 2013 22 Sep, 2013 1 Ene, 2014 23 Ene, 2014 27 Ene, 2014 31 Ene, 2014 14 Feb, 2014 15 Mar, 2014 11 May, 2014 Results 19/04/13 21/04/13 20/05/13 06/06/13 08/08/13 26/08/13 26/08/13 26/08/13 22/09/13 01/01/14 23/01/14 27/01/14 31/01/14 14/02/14 15/03/14 11/05/14 Can somebody test and guide me for filling the bug? Thanks -- Antón Méixome - Galician Native Lang Coordination Galician community LibO &amp; AOO </pre> Anton Meixome 2013-05-07T19:57:07 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/5961 <pre>Hello, sorry for spamming all the lists, but in the light of recent events and discussions, I'd like to make all of you aware of an important mailing list, that so far has not been used as extensively as it should be, which led to some frustration and communication issues. As part of our mission to foster the project internal communication, I'd like to tell you about our so called projects mailing list, which Sophie initiated quite a while ago, and which should be used for communication amongst the various projects - e.g. design and marketing, development and marketing, UX and development, and the like. The list's intention is not to be a gossip list where everything should be thrown at, but to make all affected projects aware of important changes. Philosophy: Low traffic, but important topics. Some examples are: Change of version numbers, a new slogan, design changes, new products. In other words: Everything that has an impact on other areas of working than the one where the change originally comes from. If one team decides LibreOffice will now be called different, and has a shiny new colour, surely marketing should know in time. Well, a bit of a made up example, but you get the point... ;-) We have seen some unpleasant events in the past, that based on my experience, are mostly due to the lack of communication, or due to miscommunication. To avoid that in the future, I'd like to call out to everyone of you, if you are active in one of the subprojects, to also join this mailing list by sending an empty e-mail to projects+subscribe&lt; at &gt;global.libreoffice.org and following the instructions mailed back. At least one or two representatives from *each* project should join this list, to act as a gateway. I will soon follow up further with some details and topics that have reached me the past weeks, and how we could solve them. Again, sorry for spamming, and have a great weekend! Florian </pre> Florian Effenberger 2013-05-04T13:25:04 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/5958 <pre>N'ko is a right to left language with its own digits. For more information see : http://en.wikipedia.org/wiki/N%27Ko_alphabet Unicode range : U+07C0–U+07FF I want to start the localization of libre office in N'ko language. Unfortunately, this language is not yet supported. Some information about te language : ISO 639-2 : nqo English Name : N'ko ISO 3166-1 : not available (standard language) Microsoft ID : not available Unicode range : U+07C0–U+07FF right to left : yes own digits : yes Wiki page : http://en.wikipedia.org/wiki/N%27Ko_alphabet </pre> Kaïraba Cissé 2013-05-04T12:34:45 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/5956 <pre>Hello, at the moment, we are looking for volunteers who could help moderate this mailing list. If you are interested, the only requirement is that you are subscribed to the list yourself and read its mails in a somehow timely manner, but that's about it. Moderation means dealing with e-mails that do not automatically make it to the list, which you then manually forward, or reject. This happens either when an e-mail comes from an unknown sender, e.g. when a project member uses a different address for posting. It also occurs when someone unexperienced writes to the list, thinking it's a private account, but in fact it's a public list. You'll receive the message to be moderated via e-mail, which you then can either "moderate through", or reject. Is someone interested in joining our efforts? It'd be much appreciated - just drop me an email (please also copy me directly, and not only the list), then I'm happy to add you to the list of moderators. Thanks! Florian </pre> Florian Effenberger 2013-05-04T11:32:44 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/5955 <pre>I'm still having problems getting the English spellchecker to run in a localized version of LO (see https://bugs.freedesktop.org/show_bug.cgi?id=64004) but while I was fiddling around with that today, I came across another issue. If you open the addon manager, even if you drag the window across the whole width of the screen, many items have descriptions that don't fit on the screen (see screenshot here http://www.akerbeltz.org/sealach/dicts.jpg) The solutions that spring to mind include: - making the text wrap - introducing a length limit - and/or making the width of the window adjust according to the length of the longest string - ... after a certain letter count with a hyperlink I'm just putting these ideas out there, you know I'd love to do patches myself but my brain just doesn't want to function that way :/ Also, while showing someone how to install LO and the spellchecker, having waxed lyrical about it, I got egg on my face because the latest oxt I uploaded did not work because I had filled the name field but left the extension .oxt off. This is seriously annoying, not because I got egg on my face but if the system requires me to manually type out the extension, it should either prompt or give an error message when the user provides an unknown or missing extension (in terms of LO extensions). Cheers Michael </pre> Michael Bauer 2013-05-03T09:32:12 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/5951 <pre>Hi I found not translated entry, but i dont know where is (look at picture) picture -&gt; https://www.dropbox.com/sh/4sumduxmokzew1l/95ICupvcRL?m </pre> Konrad K. 2013-05-02T13:03:31 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/5948 <pre>Hi Andras Can You please update Portuguese dictionary for master and 4.x branch? You can grab the file here&lt;http://natura.di.uminho.pt/download/sources/Dictionaries/libreoffice/oo3x-pt_PT.oxt&gt; Thanks </pre> Sérgio Marques 2013-04-29T14:31:32 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/5947 <pre>Hi, please note that the commit deadline for 4.0.3.2, aka rc2, is today, April 29, 2013. It will be used as LO-4.0.3 final if no blocker is reported. See also http://wiki.documentfoundation.org/ReleasePlan#4.0_release http://wiki.documentfoundation.org/Release_Criteria http://wiki.documentfoundation.org/Development/Branches Best Regards, Petr PS: Please, help with reviewing pending commits. </pre> Petr Mladek 2013-04-29T07:43:13 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/5930 <pre>Hi all, there have been created the libreoffice-4-0-3 branch. It will be used for fine tuning of the 4.0.3 release. The following rules apply: + preferably just translation or blocker fixes + only cherry-picking from libreoffice-4-0 branch + 2 additional reviews needed; 2nd reviewer pushes + no regular merges back to anything The 'libreoffice-4-0' branch is still active and will be used for the 4.0.4 bugfix release. Please read more at http://wiki.documentfoundation.org/ReleasePlan http://wiki.documentfoundation.org/Development/Branches Now, if you want to switch your clone to the branch, please do: ./g pull -r ./g checkout -b libreoffice-4-0-3 origin/libreoffice-4-0-3 Hopefully it will work for you :-) Most probably, you will also want to do (if you haven't done it yet): git config --global push.default tracking When you do git push with this, git will push only the branch you are on; e.g. libreoffice-4-0-3 when you have switched to it. This will save you some git shouting at you. Happy hacking, Petr </pre> Petr Mladek 2013-04-16T13:52:15 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/5928 <pre>Hi! I found that for some reason the spell checking dic for Latgalian language in not working anymore the dic can be found here: http://extensions.libreoffice.org/extension-center/latgalian-spell-checking-and-hyphenation-module The dic is shown in the list of extensions, in character formatting dialogue the availability of spelling dic is indicated, but spell schecking is gone and there are no suggestions also. To add more to the confusion - the very dictionary is working in Mozilla products without any problems. Where is a problem? The other dic developed by me for Latvian languge is working as expected. Janis </pre> Jānis 2013-04-15T11:30:00 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/5925 <pre>Hi, please note that the commit deadline for 4.0.3.1, aka rc1, is on today, April 15, 2013. The tag and branch libreoffice-4-0-3 is going to be created tomorrow. Only commits with 3 reviewers will be allowed for that branch. See also http://wiki.documentfoundation.org/ReleasePlan#4.0_release http://wiki.documentfoundation.org/Release_Criteria http://wiki.documentfoundation.org/Development/Branches Best Regards, Petr PS: Please, help with reviewing pending commits. </pre> Petr Mladek 2013-04-15T06:50:36 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/5921 <pre>Hi, Locales for LibreOffice only include Northern Kurdish, and it's named "Kurdish" instead of the correct "Kurdish, Northern" (Kurdish encompasses all variants of the language, it's unspecific). Central Kurdish and Southern Kurdish need to be added too since they are basically different languages. Central and Southern Kurdish use a modified arabic script by default and are RTL whereas Northern Kurdish by default uses latin script and is LTR. I will suggest the mappings without country codes, this is because the variants of Kurdish are similar throughout each country and there's not much of a use in separating things by country. If country codes are an absolute must I can suggest them anyway. The three letter 639-3 codes should be used in the locale settings for the Kurdish variations and not the two letter 639-1 codes, the suggested names in the following list should be used and not simply "Kurdish". --- Codes and mappings (ISO 639-3): Mapping: ckb Info: RTL, unicode Language list: English: Kurdish, Central French: Kurde, Centrale German: Kurdisch, Zentral Kurdish, Northern: Kurdí Sorani Swedish: Kurdiska, Central Turkish: Kürtçe, Orta Mapping: ckb-Latn Language list: English: Kurdish, Central (latin) French: Kurde, Centrale (latin) German: Kurdisch, Zentral (lateinisch) Kurdish, Northern: Kurdí Sorani (latînî) Swedish: Kurdiska, Central (latinsk) Turkish: Kürtçe, Orta (latin) Mapping: kmr Language list: English: Kurdish, Northern French: Kurdes du nord German: Kurdisch, Nördliches Kurdish, Northern: Kurdí Kurmancî Swedish: Kurdiska, Nordlig Turkish: Kürtçe, Kuzey Mapping: sdh Info: RTL, unicode Language list: English: Kurdish, Southern French: Kurdes du sud German: Kurdische, Süd Kurdish, Northern: Kurdí Xwarig Swedish: Kurdiska, Sydlig Turkish: Kürtçe, Güney Mapping: sdh-Latn Language list: English: Kurdish, Southern (latin) French: Kurdes du sud (latin) German: Kurdische, Süd (lateinisch) Kurdish, Northern: Kurdí Xwarig (latînî) Swedish: Kurdiska, Sydlig (latinsk) Turkish: Kürtçe, Güney (latin) note: About the ku-TR and ku-SY that are currently there: change the language list name for them from "Kurdish" to "Kurdish, Northern". This means that there will be three "Kurdish, Northern" in total (ku-TR, ku-SY and kmr). All language tools and localizations should be updated and assigned to kmr (and not to ku), once that's done I guess ku-TR and ku-SY can be removed. If someone still wants to differentiate between Northern Kurdish in different countries, then the mappings kmr-XX can be used (and not ku-XX as ku is the macrolanguage kurdish and not specifically Northern Kurdish). note 2: sdh-Latn and ckb-Latn are LTR and use the same script as kmr. I think they use unicode, but I'm not 100%. note 3: In the language list, when I write "Kurdish, Northern:", I mean the localization that is currently named "Kurdish". Like I said, this localization should be renamed to "Kurdish, Northern". --- Microsoft added Central Kurdish to Windows 8 and Office 2013. Here are the LCIDs for Windows 8 (they're probably the same for Office 2013): Central Kurdish, 0x0092, ku Central Kurdish, 0x7c92, ku-Arab Central Kurdish Iraq, 0x0492, ku-Arab-IQ (source: http://download.microsoft.com/download/9/5/E/95EF66AF-9026-4BB0-A41D-A4F81802D92C/[MS-LCID].pdf ) A Word 2013 document written in sorani/arabic script and marked as "Central Kurdish Iraq" is assigned the code "ku-Arab-IQ" in the xml, just as the Microsofts LCID list says (so 0x0492 should be linked to "ckb"). Text written in latin can't be assigned "Central Kurdish Iraq" in Word 2013, this indicates that "Central Kurdish Iraq" ("ku-Arab-IQ") is reserved for sorani/arabic script only. Perhaps then, "ku" is reserved for Central Kurdish latin (if true then 0x0092 should be linked to "ckb-Latn") and "ku-Arab" for Central Kurdish throughout all countries – ie Iraq+Iran – meaning that 0x7c92 should be linked to "ckb". But it's hard to say at the moment. Regards Sahand </pre> Sahand.T 2013-04-11T19:29:58 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/5911 <pre>Hi All some users asked to add some autocorrection items for the Italian version. How could we do that? Thanks and regards, </pre> Valter Mura 2013-04-07T18:41:43 http://comments.gmane.org/gmane.comp.documentfoundation.libreoffice.l10n/5909 <pre>Hi, I was wondering how the priority of the auto correct lists are done. As part of https://bugs.freedesktop.org/show_bug.cgi?id=63149 I was trying to define a list for Hebrew which will correct the problems I have with English. But for entries which are defined in both lists, I always have the English settings being in affect, regard less of the text language. Any idea what's the trigger ? Kaplan </pre> Lior Kaplan 2013-04-05T10:06:06 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.documentfoundation.libreoffice.l10n