Re: [libreoffice-l10n] The word "common" in Chinese conversion dialog
-- Original -- From: "Mihkel Tõnnov" ; Send time: Monday, Aug 30, 2021 2:46 AM > >> To be more specific and clear, the UI "Common terms" here is actually >> saying "Daily used common terms, but not the same in both simplified and >> traditional Chinese." >> > Thanks for the explanation. > > I found that there's an (attempted) explanation also in Help: > "Common terms are words that have the same meaning in traditional and > simplified Chinese but are written with different characters." (key-ID ujmVB > in current master) > However, this makes no sense to me -- what am I missing? In addition to Cheng-Chia Tseng's explanation, I'll offer two analogies with other languages. Think "apartment vs. flat" and "cookie vs. biscuit" in American English and British English, or east European languages that can be either written in Latin script or Cyrillic script (I remember Serbian is like this?). The difference between simplified and traditional Chinese is somewhere in between the two scenarios above. As for the Chinese conversion feature in LibreOffice, the cases covered by this "common terms" list are more like "apartment vs. flat", as the cases like "Latin vs. Cyrillic" are more easily done by rule-based replacement in large scale, and don't need this special "common terms" list. Hope this helps, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] Missing translatable strings in LO 7.1
-- Original -- From: "Adolfo Jayme Barrientos" ; Send time: Saturday, Aug 14, 2021 10:45 PM > > It can be approved, but there is only one more plannet point release > left for the 7.1 series (7.1.6), so I don??t think it??s worth the > effort. There are *two* scheduled point releases left for 7.1 series, 7.1.6 in September and 7.1.7 in November. See https://wiki.documentfoundation.org/ReleasePlan/7.1 for details. Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] Missing string since LO 7.1
Hi Carl, No need to say sorry, sometimes it's obvious where the strings show up just from the Weblate links (e.g.. when they are in a .ui file), this time it's in a .hrc header file and not obvious, so instead of digging into the code, I figured it's easier to just ask. Anyway, with your instructions I'm now able to find these two buttons, and indeed they seem to be untranslatable in 7.2.0 RC1. I've filed a bug in Bugzilla: https://bugs.documentfoundation.org/show_bug.cgi?id=143452 You and other people interested in this issue can follow up there and add any information I've missed. Regards, Ming -- Original -- From: "Carl Wellhöfer";; Send time: Tuesday, Jul 20, 2021 1:18 PM > > Hi Ming, > > sorry, I thought it would be enough naming the strings. LO 7.1 German > UI, start Writer - Menu Form - More Fields - Date Field - Context Menu > Control Properties... - Tab Page General - setting Drop-down to yes and > close the windows, then click on the arrow in the date field, the > buttons today and none are not translated. > > Greetings > Carl -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] Missing string since LO 7.1
Hi Carl, -- Original -- From: "Carl Wellhöfer" ; Send time: Monday, Jul 19, 2021 2:58 AM > > Hi, > > I received an advice from a user that two button in LO 7.1 Writer are > not translated. In LO 7.0 the buttons are translated. > > The strings in LO 7.0 are > > https://translations.documentfoundation.org/translate/libo_ui-7-0/svtoolsmessages/de/?checksum=ddab01ddb73408af > > https://translations.documentfoundation.org/translate/libo_ui-7-0/svtoolsmessages/de/?checksum=f6597580bde7fcb0 It would be helpful if the user or you can also describe how to see these two buttons from the user interface (which module, what steps to open which dialog/widget, etc.), so that other people can tracked down which part of the code changed since 7.0 that causes these two translatable strings to disappear. > They are not existing in LO 7.1 and Master. Regards, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
[libreoffice-l10n] German translation in AutoText dialog (was: Weblate permission to add comments)
Hi all, > My specific grievance is about bug 142813 [1] and German translation. As a > bug > triager I put the suggestion by the bug reporter into Weblate [2], but it just > got deleted by the German translator Christian Kuehl. I tried to contact him > via > email a week ago, but hasn't got any reply yet (maybe his Gmail account treat > my > Chinese address as spam, won't surprise me). > > 1. https://bugs.documentfoundation.org/show_bug.cgi?id=142813 > 2. > https://translations.documentfoundation.org/translate/libo_ui-master/swmessages/de/?checksum=310935ea3ff85678#history It has been a while since I sent this email, yet there seems to be no progress about this particular issue. So I'm changing the email subject and sending again, hoping someone from the German community can act on this. And if not, would Sophie or someone with comment privilege help explaining the issue on Weblate to catch the German translators' attention? Thanks, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] Weblate permission to add comments
Hi Sophie, -- Original -- From: "sophi" ; Send time: Tuesday, Jun 29, 2021 7:16 PM > > Hi Ming, > > [...] > > So may I, as a QA person who regularly triages l10n bugs, ask for Weblate > > permission to add comments for all languages? Or alternatively, someone > > with > > permission please add a German-specific comment on [2] and let the German > > translators know about the bug [1]. > > There is no such role as Add comments for all languages. What I do > usually is to post on this list with a request to the team to comment on > the bug or to let me know if they don't want to post on BZ. > > > Finally as a side note, it would be nice if there is a point-person from the > > German l10n community that has an email address registered on Bugzilla, so > > that > > relevant bugs can be easily CC'ed to, instead of just a mailing list address > > listed on [3]. > > This list is also here for that :) Members of the l10n team usually read it. I understand that there is technical limitation to achieve the "comments for all languages" goal I want. I'll use this list for communication about German l10n bugs in the future. > BTW, you have two accounts in Weblate, maybe one can be deleted? Yes, I have always been using the @PlateauWolf account this whole time, and don't remember ever registering for the @minghua one. Please delete the empty @minghua account. > Cheers > Sophie Thanks, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
[libreoffice-l10n] Questions about strings for sidebar customization
Dear Sophie, dear all, There were a set of strings recently added in 7.2/master, apparently used in Sidebar customization UI (Tools > Customize... dialog, Keyboard tab, "Sidebar Decks" category), that have some unusual spelling style. They don't use spaces in strings, instead concatenate all words together and use camel case, like "ScFunctionsDeck" [1]. Such style is common for naming variables in code, but rarely seen in UI. My questions are: Why are these strings spelled this way, instead of, say "Calc Functions Deck"? Are they supposed to be part of UI and be translated? For language like Chinese, which doesn't use spaces to separate words and doesn't have the uppercase and lowercase distinction for its characters, is it OK to just translate it like "SC functions deck"? There are probably other translators that have the same questions as I do, evidenced by the comment from user @tjhietala on Weblate page [1]. Regards, Ming 1. https://translations.documentfoundation.org/translate/libo_ui-master/officecfgregistrydataorgopenofficeofficeui/en/?checksum=91abd2f04e7c442d -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
[libreoffice-l10n] Weblate permission to add comments
Dear Sophie, Christian Lohmaier, and Christian Kuehl, I have a request about Weblate. Currently translators can't change the translation in languages other than their own, and can only make suggestions. This seems to me a good policy. However Weblate users not authorized to change translations can't make language-specific comments either, and this make it hard for suggestion makers to justify their suggestion, which is a not-so-good policy IMHO. My specific grievance is about bug 142813 [1] and German translation. As a bug triager I put the suggestion by the bug reporter into Weblate [2], but it just got deleted by the German translator Christian Kuehl. I tried to contact him via email a week ago, but hasn't got any reply yet (maybe his Gmail account treat my Chinese address as spam, won't surprise me). So may I, as a QA person who regularly triages l10n bugs, ask for Weblate permission to add comments for all languages? Or alternatively, someone with permission please add a German-specific comment on [2] and let the German translators know about the bug [1]. Finally as a side note, it would be nice if there is a point-person from the German l10n community that has an email address registered on Bugzilla, so that relevant bugs can be easily CC'ed to, instead of just a mailing list address listed on [3]. Regards, Ming 1. https://bugs.documentfoundation.org/show_bug.cgi?id=142813 2. https://translations.documentfoundation.org/translate/libo_ui-master/swmessages/de/?checksum=310935ea3ff85678#history 3. https://wiki.documentfoundation.org/Language_Teams -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] lo72b1 postponed?
Hi Martin, -- Original -- From: "Martin Srebotnjak" ; Send time: Monday, Jun 14, 2021 3:54 PM > > Hi, > do we have any notifications from the dev team - is lo72b1 postponed? No. 7.2.0 Beta1 was tagged in git yesterday afternoon European time [1], so a little bit delayed, but presumably no big deal and everything is on schedule. 1. https://git.libreoffice.org/core/+/refs/tags/libreoffice-7.2.0.0.beta1 Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] Setting Up Sesotho For LibreOffice Languages
Hi Sophie, hi all, -- Original -- From: ; Send time: Thursday, May 20, 2021 5:28 PM > > I understand your point of view, but there is nothing we can do on our > side, technically we need an existing ISO language code. I admit that I'm rather ignorant on how LibreOffice and Weblate handle these different languages, but why can't we just give them a combined language-and-country ISO code "st-LS" like we already do for English, Chinese and Portuguese (en-US, en-UK, zh-CN, zh-TW, pt-BR, etc.)? Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] Setting Up Sesotho For LibreOffice Languages
Hi, -- Original -- From: "Hlompho Mota" ; Send time: Wednesday, May 19, 2021 6:58 AM > > Greetings, > I would like to ask how one would get started in building the language for > Sesotho? > To an extend even building language support for the language. Someone who knows more probably will give you a more detailed answer, but for now you can look at the southern Sotho / Sesotho translation on Weblate [1] and find the area for improvement. For now you can only make suggestions, and since there is no contact person listed on the LibreOffice language teams page [2], you'll want to contact the previous translator to see how you can cooperate. If he/she is no longer working on the translation, you can write to this list again and ask to become the main translator for Sesotho and get access to directly change the translation string on Weblate instead of just making suggestions. 1. https://translations.documentfoundation.org/languages/st/ 2. https://wiki.documentfoundation.org/Language_Teams Hope this helps, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] 05140100.xhp -- LibreOffice Help - master text/shared/01
(Re-sending from a different email alias -- the previous one didn't seem to go through, likely because I sent it from an address not subscribed to the list. Sorry if you are receiving duplicates.) Hi, -- Original -- From: "dmtrs32 dmtrs32" https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] new string in 7.1
-- Original -- From: "sophi" ; To: "LibreOffice-l10n"; Subject: [libreoffice-l10n] new string in 7.1 > > Hi all, > > For information, this patch has add a new string in 7.1 after string > freeze (I was informed and accepted it) > > https://gerrit.libreoffice.org/c/core/+/110056 There is also another new string in dictionaries/da_DK.po, introduced by https://gerrit.libreoffice.org/c/dictionaries/+/109873 and https://git.libreoffice.org/dictionaries/+/44c6b936184e9f91d6d14fe65805640a0161fdfb Regards, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] Removal of 6.x strings
-- Original -- From: "Sérgio Marques"; To: "Lista de tradução Libreoffice"; > > Hi Christian and all, > > I don't know if the team is thinking about removing older projects from > weblate but for Portuguese language, I can assure you that you can remove > all 6.x projects because I'm the only one working on Libreoffice > translation and, for sure, I won't be touching that files anymore. Sérgio didn't elaborate the reason he wants the 6.x translations removed, so I'd like to concur and add a few comments about my experiences. Currently all five UI branches -- 6.3, 6.4, 7.0, 7.1, and master are linked together, so that changing translation of one old string on Weblate would trigger five changes, one in each branch. I assume for Help it's the same situation. This clutters quite a few places like my Profile > Recent Changes, History of the language overview page, etc. So if for whatever reason the old branches should be kept (I can think of a few), unlink them from master/7.1 so that they won't be automatically updated would be desirable. Ming > So if you think a good idea, please remove all Portuguese related files for > those projects. > > Regards -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
[libreoffice-l10n] Re: [libreoffice-l10n] At Korean LibreOffice "Find and Replace" show not "찾기 및 바꾸기"
Hi sebul, -- Original -- > From: "sebul"; > To: "l10n"; > Subject: [libreoffice-l10n] At Korean LibreOffice "Find and Replace" show not > "찾기 및 바꾸기" > > Hello I'm Korean > I installed LibreOffice at Windows 10 and Debian Linux > > My windows LibreOffice menu shows > "Find & Replace" (not 찾기 및 바꾸기) > Other menus are Korean. > > My Debian Linux's LibreOffice menu shows > "찾기 및 바꾸기" > Other menus are Korean, too. > > How can I fix MS Windows menu ? LibreOffice on Windows and Linux use the same translation. Is your Windows LibreOffice an older version (say, 6.4.x) than your Linux LibreOffice? That's the most likely reason you are seeing different Korean translations. Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] To find translation in the UI
-- Original -- From: "Ilmari Lauhakangas";; Send time: Tuesday, Oct 13, 2020 5:34 AM Subject: Re: [libreoffice-l10n] To find translation in the UI > > Ming H. kirjoitti 13.10.2020 klo 0.13: >>> Perhaps you want to look at the unreleased version instead. In this >>> case, you would navigate to a place like >>> https://dev-builds.libreoffice.org/daily/master/Win-x86_64@tb77-TDF/current/ >>> install the main package and also >>> LibreOfficeDev_7.1.0.0.alpha0_Win_x64_helppack_qtz.msi >> >> If Eugene wants to translate the UI instead of the help documentation, this >> is probably not a good idea. >> >> As far as I know, the daily builds only include English UI, no other >> languages, >> no KeyID. > > Just tried reinstalling Win-x86_64@tb77-TDF master build and I am happy > to say it includes KeyID as well as all the other languages. Indeed it does. I stand corrected. Sorry for the noise, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] To find translation in the UI
-- Original -- From: "Ilmari Lauhakangas";; Send time: Monday, Oct 12, 2020 5:11 PM Subject: Re: [libreoffice-l10n] To find translation in the UI > > Perhaps you want to look at the unreleased version instead. In this > case, you would navigate to a place like > https://dev-builds.libreoffice.org/daily/master/Win-x86_64@tb77-TDF/current/ > install the main package and also > LibreOfficeDev_7.1.0.0.alpha0_Win_x64_helppack_qtz.msi If Eugene wants to translate the UI instead of the help documentation, this is probably not a good idea. As far as I know, the daily builds only include English UI, no other languages, no KeyID. Regards, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
[libreoffice-l10n] New source strings in 7.0 branch?
Dear Sophie and fellow l10n teams, I've noticed that there are a few new (in fact, changed) strings related to document validations and signatures for the 7-0 branch on Weblate [1], which were checked into the git repo last week [2]. I don't remember seeing any announcement on this list. I personally don't mind string freeze breaks, as long as they are not too often or too many strings. But a reminder for the translators, even after the fact, is definitely desired and appreciated. Regards, Ming 1. for example, https://weblate.documentfoundation.org/translate/libo_ui-7-0/sfx2messages/zh_Hans/?checksum=9dd14b8ea9ffb8a7 2. https://git.libreoffice.org/translations/+/ef96ef3b0ec7c8ab41e66ef699eb3b7b0ff59c03%5E%21/source/zh-CN/sfx2/messages.po -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] Adding ckb to locale setting and win langpack
Hi Jwtiyar, -- Original -- From: "Jwtiyar ali";; Send time: Sunday, Aug 16, 2020 10:02 PM Subject: Re: [libreoffice-l10n] Adding ckb to locale setting and win langpack > > For locale data we already have in CLDR and glibc. How i can use these to > create new one to LO? Like Baurzhan said, LO has its own collection of locale specification files: > On Sun, Aug 16, 2020, 11:08 Baurzhan Muftakhidinov > wrote: >> >> For Format -> Locale setting, you probably should add ckb version to >> >> https://cgit.freedesktop.org/libreoffice/core/tree/i18npool/source/localedata/data See bug 127011 (https://bugs.documentfoundation.org/show_bug.cgi?id=127011) as an example. > Or LO doesn't import from gnu or cldr? As LO is cross-platform software, it's probably hard to find anything to rely on for all three supported platforms (Windows, Linux and macOS), and therefore maintaining its own locale database is a necessary evil. Hope this helps, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] Adding translation to master and 7
Hi, -- Original -- From: "Jwtiyar ali";; Send time: Tuesday, Jul 21, 2020 6:19 PM Subject: [libreoffice-l10n] Adding translation to master and 7 > > Hey > As you know ckb is not yet available in stable release before i was adding > all translation to master branch, now we have master and 7 version, i have > to add translation to which one? If you use Weblate's webpage-based editor to do the translating work, your change in "UI - master" project will be automatically copied to "UI -7.0" project, and similarly for "Help - master" and "Help - 7.0" as well, assuming both strings are untranslated or translated the same way (so changes to existing translations are copied, too). So there is no need to worry or make a conscious choice. Of course, as time goes on, the content of 7.0 and master will start to differ, and some strings may only exist in master, or the same spot in the UI will have different strngs for master and 7.0. In these cases you probably want to focus on 7.0 first, as that's the version ordinary users are likely to use and see. But if you use some other tool to do the translation work, you need to take extra steps to ensure master and 7.0 are properly synchronized, to avoid duplicated work in the future. Regards, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] Can I reject or "mark as obsolete" a suggestion on Weblate?
Hi Sophie, -- Original -- From: ; Send time: Thursday, Jun 4, 2020 7:58 PM Subject: Re: [libreoffice-l10n] Can I reject or "mark as obsolete" a suggestion on Weblate? > Hi Ming, > Le 04/06/2020 à 13:47, Ming H. a écrit : > >> I can't find a way on Weblate to either reject a suggestion, >> or mark it obsolete, so that it doesn't show up in the overview >> page anymore. Weblate documentation mentions deleting a >> suggestion ( >> https://docs.weblate.org/en/weblate-3.10.1/user/translating.html#translating >> ), >> but I can't figure out how to do it, maybe it's for the original >> author of the suggestion only? > > You should be missing some rights, what is your user name in Weblate? My handle on Weblate is PlateauWolf (plateauwolf at qq.com), thanks! Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
[libreoffice-l10n] Can I reject or "mark as obsolete" a suggestion on Weblate?
Hi all, I've been reviewing quite a lot of suggestions for simplified Chinese translations on Weblate recently. Most of them are good and I either accept them or accept and edit a bit. However there are some suggestions that are of poor quality, some are even outright wrong, so I just ignore them. (If you are interested in an example, see https://translations.documentfoundation.org/translate/libo_help-master/textsbasicguide/zh_Hans/?checksum=78974c2176f08d1e#suggestions ) The problem is that these bad suggestions still linger in the system and obscure the overview page https://translations.documentfoundation.org/languages/zh_Hans/ and makes it difficult for me to locate new suggestions for review. I can't find a way on Weblate to either reject a suggestion, or mark it obsolete, so that it doesn't show up in the overview page anymore. Weblate documentation mentions deleting a suggestion ( https://docs.weblate.org/en/weblate-3.10.1/user/translating.html#translating ), but I can't figure out how to do it, maybe it's for the original author of the suggestion only? Can anyone help? Thanks, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] Question about translating language names
Hi Eike, Thanks for the reply. -- Original -- From: "Eike Rathke"; Date: Jun 2, 2020 Subject: Re: [libreoffice-l10n] Question about translating language names > > Hi, > > On Friday, 2020-05-29 11:54:27 +0200, Sophie Gautier wrote: >> > However there is also >> > https://translations.documentfoundation.org/translate/libo_ui-master/svtoolsmessages/zh_Hans/?checksum=4abc603904d1d7fa >> > where the country notation is only "Congo". Does this mean >> > it's spoken in Republic of the Congo (a.k.a. Congo-Brazzaville)? >> > If yes, it's probably better to be explicitly spelled out, as >> > "Congo" is ambigous. > > Yes, "(Congo)" is the Republic of the Congo, Congo-Brazzaville. > IIRC those languages/locales simply were earlier supported and just > later the "(Democratic Republic of the Congo)" locales were added. Or maybe because "(Congo)" was used at a time when Dep. Rep. of the Congo was called "Zaire", and when it changed its name, we only updated "Zaire" to "Dep. Rep. of the Congo", but neglected "Congo". > Geez.. that's a mess. (Also seeing the follow-ups about the complications) Sorry for opening this can of worms. :-P Regards, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] Question about translating language names
Hi Sophie, -- Original -- From: ; Send time: Friday, May 29, 2020 5:54 PM Subject: Re: [libreoffice-l10n] Question about translating language names > > Hi Ming, > > Le 29/05/2020 à 11:02, Ming H. a écrit : >> I was translating various language names used in LO and had >> a question about the English strings, specifically the name of Congo. >> As a Chinese I know nothing about languages spoken in Africa, so >> I'm writing to the list, hope someone more knowlegable can answer. > >> For the languages presented in LO, the parentheses are usually used >> for notation of the country/region the language is spoken in. [...] > > In fact, this is part of the language name and not only the name of the > country. Look here for Kituba: > https://glottolog.org/resource/languoid/id/kitu1245 I respectfully disagree. They are just names linguists use to distinguish dialects/variants of the same language. Linguists may like to call them different languages like they differentiate all those dialects of English: https://glottolog.org/resource/languoid/id/stan1293 But to an ordinary layman, they are just the same language, spoken with slight differences in different countries. And note that although this website uses names like "Indian English", LO uses "English (India)" in the style I described. > But what is strange is that Aka has no area attached to it > https://glottolog.org/resource/languoid/id/akaa1242 > https://iso639-3.sil.org/code/soh In my original link https://translations.documentfoundation.org/translate/libo_ui-master/svtoolsmessages/zh_Hans/?q=source%3A%22(Congo)%22=2 you can see three other languages as well (click the "Next" button): Koongo, Njyem, and Yombe. > I wonder where it comes from, I'll ask Eike Eike is definitely the expert on these locale issues. It would be great to hear from him. Regards, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
[libreoffice-l10n] Question about translating language names
I was translating various language names used in LO and had a question about the English strings, specifically the name of Congo. As a Chinese I know nothing about languages spoken in Africa, so I'm writing to the list, hope someone more knowlegable can answer. For the languages presented in LO, the parentheses are usually [1] used for notation of the country/region the language is spoken in. And in https://translations.documentfoundation.org/translate/libo_ui-master/svtoolsmessages/zh_Hans/?checksum=c7f58abceaa60b71 Democratic Republic of the Congo, also known as Congo-Kinshasa, is noted as such. However there is also https://translations.documentfoundation.org/translate/libo_ui-master/svtoolsmessages/zh_Hans/?checksum=4abc603904d1d7fa where the country notation is only "Congo". Does this mean it's spoken in Republic of the Congo (a.k.a. Congo-Brazzaville)? If yes, it's probably better to be explicitly spelled out, as "Congo" is ambigous. There are also four other strings with "(Congo)" notations: https://translations.documentfoundation.org/translate/libo_ui-master/svtoolsmessages/zh_Hans/?q=source%3A%22(Congo)%22=2 which also need clarification. Thanks in advance, Ming 1. One exception I am familiar with, is Chinese (simplified) and Chinese (traditional). They probably should be "Chinese, simplified" and "Chinese, traditional" if applied the same notation styles as the other language strings. I fully understand how they've become the way they are now and don't in any means propose changes. -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] A few questions about translating color names
>> This is part of the translation, see >> https://weblate.documentfoundation.org/translate/libo_ui-master/svxmessages/fr/?checksum=127eea4231a364b1 >> or is there something I don't undersand? > > You understood fine. My question (b) is about what happens if the > French translator decides to translate it as "Rouge foncé deux", > which won't match the "Rouge foncé 2" name in the palette. A bit more clarification: my understanding is that the name shown in the palette will be from https://weblate.documentfoundation.org/translate/libo_ui-master/svxmessages/fr/?checksum=e599d9f72b8eb77b with " 2" added to the end, therefore "Rouge foncé 2". Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] A few questions about translating color names
Hi Sophie, -- Original -- From: "sophi"; Send time: Friday, May 15, 2020 8:18 PM Subject: Re: [libreoffice-l10n] A few questions about translating color names > > Hi Ming, > > Le 15/05/2020 à 12:16, Ming H. a écrit : > >> 1. Line 561-566, these are names of several colors used as default in >> various places. My questions are: (a) Does it mean different locales >> can actually use different default colors if we change it in the translation? > > Only the name of the color will be changed, not the color itself > >> And if not, what's the point of making it translatable? > > when you over a color, its name appears and it's also read by screen > readers, so it's mandatory to have them translated Good to know. My argument is then the translation can be automatically generated from other translatons, instead of making translators to do it twice. But that's a trivial thing. >> (b) What happens if the translation of these strings don't match the >> translation of the actual color names? This is easier to happen than >> perceived, as for example line 562 has "Dark Red 2", but for the >> translation of actual names there is only "Dark Red", and the " 2" part >> is added automatically without translation. So if a translator was >> tempted to translate the numbers to something language specific, there >> will be mismatch. > > This is part of the translation, see > https://weblate.documentfoundation.org/translate/libo_ui-master/svxmessages/fr/?checksum=127eea4231a364b1 > or is there something I don't undersand? You understood fine. My question (b) is about what happens if the French translator decides to translate it as "Rouge foncé deux", which won't match the "Rouge foncé 2" name in the palette. But from your answer above I guess it doesn't matter much, just a discrepancy between two strings describing the same color. >> 2. Line 627-651, these are colors used by the "material" palette. >> There are quite a few names like "Color A" in it. However these >> are not the full names of the colors, as the full names are like "Gray >> A200", with the "200" again added automatically without translation. >> So my question is: Why not just include the " A" part as the >> automatic suffix as well? After all, both Greek alphabet and Cyrillic >> alphabet starts with a letter close enough to the Latin "A", and it's >> not likely languages using other alphabets will translate this "A" part >> anyway. I can also imagine the headache this will cause for RTL >> languages. > > Where do you see that the name is Gray A200? could you tell me in which > module and palette? In the "material" palette, the two columns on the right, and the module shouldn't matter. It's only avaiable in 7.0 though. >> 3. Line 652-665, these are declared to be old names and likely used >> for backward compatibility reasons. My question is: Would the old >> files use localized names? If so, should we refrain from ever >> changing the translations of these? Then again, color pink is used >> in other palettes like material. > > Again, it's only a name, if you have a green color and translate it to > blue in your language, that will only be seen as a wrong translation, > but won't prevent to do anything with the color. Or maybe I missed > something in your questions. You may have missed a bit, but it's not important. As long as I know I'm free to change these translations, I'm good. Thanks, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
[libreoffice-l10n] A few questions about translating color names
I did an overview of translation of various colors used in LO, and in doing so had some questions. These questions are probably more towards developers than fellow translators and l10n admins, but I don't know which specific developers to ask, or if the dev mailing list is a good place for such questions. So here they are, please direct me to proper channels if needed. In this email I'm going to refer to several strings, and Weblate links are a bit cumbersome, so I'm going to use line numbers of the file core/include/svx/strings.hrc instead: https://opengrok.libreoffice.org/xref/core/include/svx/strings.hrc?r=b680547a 1. Line 561-566, these are names of several colors used as default in various places. My questions are: (a) Does it mean different locales can actually use different default colors if we change it in the translation? And if not, what's the point of making it translatable? (b) What happens if the translation of these strings don't match the translation of the actual color names? This is easier to happen than perceived, as for example line 562 has "Dark Red 2", but for the translation of actual names there is only "Dark Red", and the " 2" part is added automatically without translation. So if a translator was tempted to translate the numbers to something language specific, there will be mismatch. 2. Line 627-651, these are colors used by the "material" palette. There are quite a few names like "Color A" in it. However these are not the full names of the colors, as the full names are like "Gray A200", with the "200" again added automatically without translation. So my question is: Why not just include the " A" part as the automatic suffix as well? After all, both Greek alphabet and Cyrillic alphabet starts with a letter close enough to the Latin "A", and it's not likely languages using other alphabets will translate this "A" part anyway. I can also imagine the headache this will cause for RTL languages. 3. Line 652-665, these are declared to be old names and likely used for backward compatibility reasons. My question is: Would the old files use localized names? If so, should we refrain from ever changing the translations of these? Then again, color pink is used in other palettes like material. Thanks in advance, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] pocheck (6-4): Langauges with errors: am cy dsb fy mn nb szl vec
Hi Berend, -- Original -- From: "Berend Ytsma" Send time: Thursday, May 14, 2020 6:49 AM > Hi, > > For Frisia (fy) i can't locatie wat is wrong. The link gives my no matching > strings found. Try this one: https://translations.documentfoundation.org/languages/fy/libo_ui-6-4/search/?q=target%3AByskrift== > I did a Manuel check of the words an also couldn't find it You probably wasn't searching in the "LibreOffice UI - 6.4" component, or not using the "Target strings" condition while searching (only available under "Advanced query builder" after you've searched once). > Greets Regards, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] KeyID change across branches for the same string
Hi Christian, -- Original -- From: "Christian Lohmaier";; Send time: Wednesday, May 6, 2020 8:01 PM > On Sat, May 2, 2020 at 4:23 AM Ming H. <2097632...@qq.com> wrote: [...] >> They don't show up in the other's "similar strings" section either, though >> that's probably expected as that feature may only match strings in the same >> Weblate project. > >Not sure what you mean with "similar strings" section. [very detailed explanation of Weblate features snipped] Sorry, I meant the "other occurences" tab, which is the one I use most since it usually has a number prompting something worth looking at. I've never used Machine Translation or Translation Memory before, either on Weblate or elsewhere, I'll be looking into these useful tools. >> It would be nice if such problem can be avoided. I only noticed this >> because this is an extremely long string. There are probably many other >> short ones that fell through the crack and increased work for many >> translation teams. > > Nope, that was the only one, and this specific problem also cannot > happen anymore. Good to know, I'll stop worrying. :-) > ciao > Christian Thanks, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
[libreoffice-l10n] KeyID change across branches for the same string
Hi all (but most likely Christian), While doing translation for "UI - master" on Weblate today I came across the following string, at the time untranslated, with KeyID BUn8M: https://translations.documentfoundation.org/translate/libo_ui-master/sfx2messages/zh_Hans/?checksum=414ab42ae064f7da I was surprised that this was never translated for Chinese, so I went back to "UI - 6.4" and found this, with KeyID dPabj: https://translations.documentfoundation.org/translate/libo_ui-6-4/sfx2messages/zh_Hans/?checksum=414ab42ae064f7da In my naked eye, they look the same. They are also both from the same file (sfx2/uiconfig/ui/licensedialog.ui), and have the same context (licensedialog|label). So how did they end up with different KeyIDs? They don't show up in the other's "similar strings" section either, though that's probably expected as that feature may only match strings in the same Weblate project. It would be nice if such problem can be avoided. I only noticed this because this is an extremely long string. There are probably many other short ones that fell through the crack and increased work for many translation teams. Regards, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] Question about file download/upload on Weblate
Hi Christian, Thanks for the detailed explanation. -- Original -- From: "Christian Lohmaier";; Send time: Tuesday, Apr 28, 2020 11:25 PM Subject: Re: [libreoffice-l10n] Question about file download/upload on Weblate >> But occasionally I use the file downloading and uploading method to give a >> certain component an overall change, covering quite a few strings at the >> same time. [??] >> >> Is there any option or procedure that can enable automatic propagation >> between branches? > > Propagation of translations on file upload has been explicitly > disabled by weblate authors: > https://github.com/WeblateOrg/weblate/commit/c31b7e9f48dd828e1d63a9c81118b4ec204e64db > > Could be reenabled again on our instance if majority of translators agree. I can imagine the potential catastrophe if this is enabled and someone makes a careless mistake. I don't use the file DL/UL feature often enough to have a strong opinion. If no other translators want it, I'm fine with the current disabled status. >> Or do I have to upload the file twice, one for each branch? > > Please don't use the same file twice. Please download the files for > both branches separately and locally merge your changes before > reuploading Yes I understand PO files are a bit tricky. I tried "msgmerge -o new-master.po -N 6-4.po master.po" a while ago when I tried to rectify the discrepancy caused by my file upload, but the result new-master.po contained too many unrelated changes and I ended up discarding it and manually edited the master.po file instead. I'll ask on this list if I need to do this again in the future and can't figure it out myself. Regards, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
[libreoffice-l10n] Question about file download/upload on Weblate
I have a question regarding updating the translations on Weblate using the file downloading/uploading method. I usually just use the web interface of Weblate, and I appreciate the feature of linking the "6.4 UI" and "master UI" translations together so that the changes I did in one branch is automatically copied to the other as long as the source strings are the same (maybe the translated strings need to be the same as well? I am not sure). But occasionally I use the file downloading and uploading method to give a certain component an overall change, covering quite a few strings at the same time. However, if I do this to the "6.4 UI" branch, the changes are not propagated to "master UI" automatically. For example, the changes I made in https://translations.documentfoundation.org/translate/libo_ui-6-4/instsetoo_nativeinc_openofficewindowsmsi_languages/zh_Hans/?checksum=50716ed40498e6c7#history are not carried over: https://translations.documentfoundation.org/translate/libo_ui-master/instsetoo_nativeinc_openofficewindowsmsi_languages/zh_Hans/?checksum=50716ed40498e6c7#history Is there any option or procedure that can enable automatic propagation between branches? Or do I have to upload the file twice, one for each branch? Thanks in advance, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] Weblate Privilege - zh_CN
-- Original -- From: ; Send time: Tuesday, Mar 3, 2020 7:29 PM > > Hi Kevin, > Le 03/03/2020 à 11:08, Kevin Suo a écrit : >> 1. Could someone add plateauw...@qq.com to the weblate translator list, with >> proper privileges to submit translation, for Simplified Chinese (zh_CN) >> language? He currently is only able to make suggestions. > > Done Thank Kevin and Sophie! -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] Please clarify translation deadlines
Hi Tuomas, -- Original -- From: "Tuomas Hietala" ; Subject: [libreoffice-l10n] Please clarify translation deadlines > > I've been updating a lot of the Finnish translations of LO recently > (translated in Weblate on master branch, automatically propagated to 6.3 > and 6.4) However, I noticed many of them didn't make it to the 6.4.0 > release. Reading [1] and [2], I was under the impression that > translations made on Monday 27th January or earlier should have been > picked up in 6.4.0, but this clearly isn't the case. Did I misunderstand > something, is the information in the wiki wrong, or was there some other > issue? > > [1] https://wiki.documentfoundation.org/Translating_LibreOffice > [2] https://wiki.documentfoundation.org/ReleasePlan While I agree the deadline section of [1] is not clear, one thing you missed is that for the final release of a version (i.e. not RC1, RC2, etc.), there is an extra week of "wait for testing and make sure no showstopper in there" period, and the actual code-changing deadline should be a week before the release week, the same as the last RC. So for the 6.4.0 case, the code was tagged in Git sometime in the Jan. 20th - Jan. 26th week [3], and your expectation of Jan 27th was definitely too late. I'll leave the clarification of the exact dates to others. 3. https://wiki.documentfoundation.org/ReleasePlan/6.4#6.4.0_release Hope this helps, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] Request for breaking string freeze
Dear l10n teams, -- Original -- > I am writing to ask for approval of backporting a patch > to 6-4 branch that breaks string freeze. The patch is > about a new feature in 6.4, "Full-sheet preview/export" > in Calc, specifically about how it's is shown in the "PDF > Options" export dialog. The patch was backported to 6-4 branch on Jan 20th, and Christian has now synced it to the "LibreOffice UI - 6.4" project on Weblate. Now you can translate it for 6.4.1 release. It's in the filter/messages component, with keyID MpRUp. Note the same string is also in "LibreOffice UI - master". Thanks again for your understanding and patience. Regards, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] Questions about a couple of strings in UI master
-- Original -- From: "Mihail Balabanov" ; Send time: Thursday, Jan 23, 2020 8:48 PM > > Hello, > >I have questions about a couple of UI strings in LO master. > > Q2: What is the meaning of ??f.?? and ??ff.?? in the string below? Is it > ??folio?? from Latin or something like that? Should it be translated? (was > ??p?? and ??pp?? before) According to the relevant bug #94411, they stand for "and the following page(s)". https://bugs.documentfoundation.org/show_bug.cgi?id=94411 Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [libreoffice-l10n] Request for breaking string freeze
Hi Sopie and Christian, -- -- > > Hi Ming, > Le 13/01/2020 ?? 23:30, Ming Hua a ??crit : >> >> What I'm proposing is to backport the renaming patch sometime >> after 6.4.0 is released, likely end of January, then leave enough >> time for translators to work on it before 6.4.1 is released at the >> end of February. Presumably the users willing to adopt new >> releases early will be less bothered by such string changes. > > I guess there is enough time for 6.4.1 to translate the string. Would > that be ok for you too Martin? Since Martin said there won't be any problem, and there aren't objections from other translators either, I'll take it as a "yes" for backporting this string change from the l10n team. I'm not familiar with the timing of the syncing between git and weblate. The wiki https://wiki.documentfoundation.org/Translating_LibreOffice says translations are submitted before the Monday tagging deadline, which should be Jan. 20th for 6.4.0 RC3. Is it still the case, and does it mean it's safe to start the backporting after Jan. 21st? I know this is Christian's ballpark, does he read every mail on this list, or should I contact him individually? Thanks, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
[libreoffice-l10n] Request for breaking string freeze
Dear Sophie and l10n teams, I am writing to ask for approval of backporting a patch to 6-4 branch that breaks string freeze. The patch is about a new feature in 6.4, "Full-sheet preview/export" in Calc [1], specifically about how it's is shown in the "PDF Options" export dialog. Recently there was a bug report (#129714, [2]) that asks for changing the current wording "Full-sheet previews" as the feature also covers exporting to PDF, and describing it as "previews" may be misleading. After discussion the wording change to "Whole sheet export" has been decided and the patch was applied to git master on January 11th. Since this is a new feature in 6.4, I feel first introducing it one way and then changing the name right next release would be a disservice to users. So I propose to backport it (just the renaming patch, the feature is already in 6.4) to 6-4 branch and have it consistent from 6.4.1 release and on. Of course this breaks the string freeze, and a cursory search on Weblate [3] shows the string (translation tag 2o29R) has been translated to 27 languages. So I'm asking these teams to approve this late request, since you need to translate the new string for the next release sooner or later anyway. Meanwhile, languages that haven't translated it yet can avoid a bit of extra work. [1] https://wiki.documentfoundation.org/ReleaseNotes/6.4#Full-Sheet_Previews [2] https://bugs.documentfoundation.org/show_bug.cgi?id=129417 [3] https://weblate.documentfoundation.org/search/libo_ui-6-4/?q=+source%3Afull-sheet+previews+type=translatedignored=False P.S.: I can't find the procedure for string freeze break described on wiki, so I'm just writing to this list. If there are more people (documentation team?) that I should ask, please let me know. Thanks, Ming -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/l10n/ Privacy Policy: https://www.documentfoundation.org/privacy
