Re: [libreoffice-l10n] RID_SVXSTR_OUTLINENUM_DESCRIPTION change
On Fri, 2023-04-28 at 14:40 +0200, Eike Rathke wrote: > That's unfortunate though, because it's not available in Weblate and > translators Since "migrate to boost::gettext" we gained extracting comments via xgettext which we use with something like xgettext -C --add-comments --keyword=NC_:1c,2 --from-code=UTF-8 --no- wrap foo.hrc I tend to prefix comments targeted for translators with "To translators: " -- 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] PRODUCTNAME
On Tue, 2022-04-05 at 13:48 +0200, Milos Sramek wrote: > Hi, > thank you for your explanation. I thought that these placeholders are > resolved at build time. > > There are still hundreds of %PRODUCTNAME in the strings. Will all of > them be replaced? No, only this relatively small set which appeared in the accessibility descriptions of the .ui files. -- 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] PRODUCTNAME
On Wed, 2022-03-30 at 15:46 +0200, Milos Sramek wrote: > Does anybody know why were these changes necessary? https://bugs.documentfoundation.org/show_bug.cgi?id=146971 for the tip of the problem where changing the PRODUCTNAME for the accessiblity descriptions at runtime triggers accessibility features under gtk3 which has a 9x startup slowdown. I was able to bodge it for 7-3 and 7-2 without changing strings, but for trunk I changed things to not allow PRODUCTNAME in accessibility descriptions which has the knock on of needing these new strings. -- 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] what means "Key" in color picker dialog and why is this "Black" sometimes ?
On Sun, 2022-02-27 at 09:33 +0100, Heiko Tietze wrote: > This is the color picker dialog showing up when you click on "Custom > Color" in the floating widget. "Key" is the last entry for CMY*K* > setting the black value. I've submitted a patch to add translator notes to those entries for the future: https://gerrit.libreoffice.org/c/core/+/130650 -- 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] Bulk translation of new " stock" strings
On Thu, 2021-02-18 at 21:41 +0200, Tuomas Hietala wrote: > Hello all, > > What are these "stock" strings for anyway? And why isn't there a > more meaningful context string? > > This is from https://lists.freedesktop.org/archives/libreoffice/2021-January/086638.html where previously all the ok, cancel, help buttons didn't have translatable strings but used "stock" names like gtk-ok, gtk-cancel, gtk-help. These "stock" names are deprecated in gtk3 and gone in gtk4 so we will need to provide our own translations for them in each module.mo. The attempted compromise was to use a context of "stock" for those translations so each set would only appear once in each module. -- 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: Fwd: [libreoffice-l10n] Unclear new strings to translate
On Mon, 2020-08-10 at 12:01 +0300, Mike Kaganski wrote: > But for a random Russian user, who tries to understand why their text > is red, reading a random English description like "Color of > character", or random English-based ID like "CharColor", might be > absolutely incomprehensible. A string like "Цвет символа", to the > contrary, would make sense. So - well, on the second thought: no, we > should not avoid translation here There is already a member in SfxPoolItem "GetPresentation" which is used in the "organizer" tab of some dialogs to give a human-readable representation of an SfxPoolItem, I wonder (without looking into it) if that is anyway useful in this circumstance. -- 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] What is CF as in "CF One"?
On Fri, 2020-08-07 at 18:27 +0200, Kolbjørn Stuestøl wrote: > In LibreOffice UI 7.0 > ( > https://translations.documentfoundation.org/translate/libo_ui-7-0/svxmessages/nn/?q=state%3A%3Ctranslated=24#nearby > ) > and perhaps other places, the words "CF One", "CF Only One" etc. are > used > > What does "CF" mean and where is it used and what for? CF is "Crow's Foot" http://document-foundation-mail-archive.969070.n3.nabble.com/libreoffice-l10n-Meaning-of-td4277617.html#a4277622 see: https://bugs.documentfoundation.org/show_bug.cgi?id=130074 it refers to various types of arrow ending you can find in insert, shape, line, line, right click on that line, and in the "arrow styles" list. -- 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] What's a „long dot“?
On Tue, 2020-03-31 at 16:08 +0200, Michael Wolf wrote: > Caolán McNamara schrieb: > > > Is this RID_SVXSTR_DASH1 "Long Dot" ? If so it isn't a character > > but a > > fairly recent addition of an attempt at a description for a line > > style > > seen in e.g. impress, format->object->line->line->line properties > > Hi Caolán, > > thank you, yes, you are right but this description and similar ones > (e.g. double dot) are confusing. There are no strange long dots, the > dotted lines just have a bigger spacing between the dots. The original text isn't my creation but if there is a better suggestion for a description I can submit a change based on that. -- 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] What's a „long dot“?
On Tue, 2020-03-31 at 15:03 +0200, Michael Wolf wrote: > Hi, > > what character a "long dot" is? How does it look? What Unicode code > does it have? Is this RID_SVXSTR_DASH1 "Long Dot" ? If so it isn't a character but a fairly recent addition of an attempt at a description for a line style seen in e.g. impress, format->object->line->line->line properties -- 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] Insert Bibliography Entry dialog: illogical wording
On Tue, 2019-12-17 at 01:06 +0200, Mihkel Tõnnov wrote: > In my mind, it would be logical to name that one "Entry", and rename > the first header (current "Entry") to "Bibliography source" or > similar, as it now is header only for the upper part of the dialog, > not the whole dialog anymore. That seems reasonable to me, https://gerrit.libreoffice.org/#/c/85270/ would make that change > And depending on the chosen first header, the options "From > bibliography database" / "From document content" should probably be > updated, too. What do you think the update should look like ? -- 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] The "Standard" button
On Mon, 2019-11-11 at 18:09 +0100, Martin Srebotnjak wrote: > I am having a problem localizing the "Standard" button that appears > in the "Character" and "Paragraph" dialog as called with the menu > command Format > Character.../Paragraph... in Writer. It is > positioned at the bottom of the dialog, no matter which tab is > selected, and is situated between the > buttons "Reset" and "OK". The presence of the button in those dialogs was a bug: https://bugs.documentfoundation.org/show_bug.cgi?id=128313 which should be fixed in 6.3.4 > This strings seems missing in po files (it tried searching for it, > also variants with _ and tilde in different positions in it), but to > no avail. It should probably appear in cui, but I am not sure. The translation string is the one of STR_STANDARD_SHORTCUT in https://opengrok.libreoffice.org/xref/core/include/sfx2/strings.hrc?r=2756ed93#99 but it not applied to the "Standard" buttons of the char and para dialog because they're not supposed to be visible in that mode -- 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] Strings [L] and [S] in optfltrembedpage.ui
On Fri, 2019-09-27 at 16:28 +0200, Michael Wolf wrote: > thank you for your quick reply. So these strings are accesskeys. They are a cheesy way to get narrow column titles for the checkbox columns in the options page, with the prefix then repeated in the longer strings which are used as explanatory keys shown underneath as to what on early the aesthetically pleasing short columns might mean. > I'm still dreaming of localization notes for LibreOffice localizers > anytime. :-) I'll add translator facing comments to this case with https://gerrit.libreoffice.org/#/c/79722/ IIRC the gettextizing of LibreOffice should mean such notes should appear in the translator side. -- 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] Strings [L] and [S] in optfltrembedpage.ui
On Fri, 2019-09-27 at 15:36 +0200, Michael Wolf wrote: > Hi, > > there are the String [L] and [S] in file optfltrembedpage.ui. What > do they refer to? What are they? Accesskeys or commandkeys? Can they > be translated? "Load" and "Save", the [L] and [S] should be the same as used in the "[L]: Load and convert the object" and "[S]: Convert and save the object" strings. This is visible in tools->options->Load/Save- >Microsoft Office -- 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] Re: plural forms translation, ngettext
On Tue, 2018-11-20 at 13:50 -0600, Kevin Scannell wrote: > A Chaoláin a chara > > There's one small issue however: the number of plural forms showing > up for Irish is incorrect; we should have five plural forms with the > following specification: > > "Plural-Forms: nplurals=5; plural=n==1 ? 0 : n==2 ? 1 : (n>2 && n<7) > ? 2 :(n>6 && n<11) ? 3 : 4;\n" ... > Would it be possible to update the documentfoundation.org Pootle > instance with this new string? I think sophi will fix those up from your submission to this list -- 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: plural forms translation, ngettext
On Tue, 2018-10-23 at 12:36 +0200, Christian Lohmaier wrote: > No issue with pootle, but pocheck needs to be taught to deal with it. Ah, https://gerrit.libreoffice.org/#/c/62637/ conflicted because this is already dealt with :-) -- 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] plural forms translation, ngettext
I was asked in https://bugs.documentfoundation.org/show_bug.cgi?id=83128 about supporting ngettext-alike plural forms. https://gerrit.libreoffice.org/#/c/61426/ is my proposal on that. To current Translate::get(id) we add Translate::nget(id, cardinality) when requesting the translation. To current NC_(context, string) we add NNC_(context, singular, plural) when declaring the strings for translation We add --keyword=NNC_:1c,2,3 to our xgettext invocation resulting in a change in the output .po for my calc SCSTR_TOTAL example from msgctxt "SCSTR_TOTAL" msgid "%1 results found" msgstr "" to msgctxt "SCSTR_TOTAL" msgid "1 result found" msgid_plural "%1 results found" msgstr[0] "" msgstr[1] "" Locally at least this works to give the desired expected results of "1 result found" vs "2 results found" for the simple example. caolanm->cloph: would this work smoothly with our current pootle stuff? -- 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] Re: .src and .ui gettext migration
On Wed, 2017-07-19 at 13:24 +0200, Leandro Regueiro wrote: > Hi, > changing the msgctxt is problematic from Pootle point of view since: > > - Pootle will detect these as new strings that will be imported with > no translation, and Pootle will mark old strings as obsolete. > > Please hold, and work out a plan to push these strings to Pootle in > order to avoid losing translations. The original email has... " To try and minimize disruption I've a script available in master as solenv/bin/update-for-gettext to update our current translations to give them a new msgctxt (and update their keyid comment) ... I've ... run this over the sample tarball of .pos extracted from pootle that cloph provided. i.e. python2 /path/solenv/bin/update-for-gettext translations/libo_ui It shrinks and normalizes the msgctxt and updates the keyid comment for .src and .ui strings and moves them into a per-module messages.po. caolanm->cloph: will this script suffice for getting pootle updated ? " so that's what I hoping to do here, update the existing translations in pootle that have the old autogeneratoed msgctxt to have the new "static" msgctxt so that (most) translations are not considered obsolete -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-l10n] Re: .src and .ui gettext migration
On Fri, 2017-07-14 at 15:57 +0200, Eike Rathke wrote: > Questions: > * where does the new implementation live that determines the actual > "resource" to be used for the current UI language, including > possible language fallbacks? We pass GetUILanguageTag to boost, and that's always one of the languages we translate to, as opposed to GetLanguageTag which could be basically anything. So if someone's desktop locale is, say "de_AT", then boost is just going to get "de_DE" from LibreOffice as the UI language. boost itself in boost/libs/locale/src/shared/message.cpp (or somewhere like that) will then try de_DE/module.mo and fallback to de/module.mo > * does std::locale that replaces ResMgr and Translate::Create() that > uses boost::locale::generator with the new > LanguageTag::getGlibcLocaleString() fully handle BCP47? No, boost::gettext takes a posix locale string as its argument when it builds a std::locale to use as input to the translate methods http://ww w.boost.org/doc/libs/1_48_0/libs/locale/doc/html/rationale.html#why_pos ix_names which is a bit sucky, but I updated liblangtag to handle the only one of the locales we translate to (ca-valencia) which it didn't already know how to map to a posix/glibc locale, so we should have a valid posix/glibc locale string for each of the bcp-47 language tags that identify a UI translation target -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] .src and .ui gettext migration
On Thu, 2017-07-13 at 12:54 +0300, Mihkel Tõnnov wrote:
> Hi Caolán, *,
>
> 2017-07-13 12:43 GMT+03:00 Caolán McNamara <caol...@redhat.com>:
>
> > [snip]
> > In our code I've autogenerated matching initial contexts for the
> > matching .ui and .hrc source strings.
> >
>
> Could you clarify what do you mean by that?
I'll take a pair of real examples:
Currently a .hrc/.src entry of SV_APP_CPUTHREADS
//in vcl/inc/svids.hrc
#define SV_APP_CPUTHREADS 10800
//in vcl/source/src/app.src
String SV_APP_CPUTHREADS
{
Text [en-US] = "CPU threads: ";
};
corresponding .po entry where the msgctxt is currently autogenerated on
extraction from .src to .po
msgctxt ""
"app.src\n"
"SV_APP_CPUTHREADS\n"
"string.text"
msgid "CPU threads: "
msgstr "something or other"
turns into
//in our source where the 1st arg is the context and all existing
//entries contexts are simply derived from the define name
#define SV_APP_CPUTHREADS NC_("SV_APP_CPUTHREADS", "CPU threads: ")
corresponding .po entry
msgctxt "SV_APP_CPUTHREADS"
msgid "CPU threads: "
msgstr "something or other"
and the msgctxt is no longer generated on export to .po just taken from
the source entry
The other case is .ui entries, they go from e.g.
//vcl/uiconfig/ui/printdialog.ui
Options
with a .po entry of
msgctxt ""
"printdialog.ui\n"
"label21\n"
"label\n"
"string.text"
msgid "Options"
msgstr "Optionen"
where the msgctxt is similarly autogenerated on export to .po
to...
//vcl/uiconfig/ui/printdialog.ui
Options
where the context/msgctxt for existing strings has been one-time
derived from the .ui filename and widget/object the string belong to
with a corresponding .po entry of
msgctxt "printdialog|label21"
msgid "Options"
msgstr "Optionen"
--
To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-l10n] .src and .ui gettext migration
So, I'm pretty happy with my latest iteration of migrating to gettext
and I've got it up and running on all supported platforms.
backstory is https://lists.freedesktop.org/archives/libreoffice/2017-Ma
y/077818.html with the modification that we retain a msgctxt, albeit a
shorter one than the current pseudo msgctxt that is generated for the
current .po files
To try and minimize disruption I've a script available in master as
solenv/bin/update-for-gettext to update our current translations to
give them a new msgctxt (and update their keyid comment)
I've successfully run this over the sample tarball of .pos extracted
from pootle that cloph provided. i.e.
python2 /path/solenv/bin/update-for-gettext translations/libo_ui
It shrinks and normalizes the msgctxt and updates the keyid comment for
.src and .ui strings and moves them into a per-module messages.po.
For .src strings the msgctxt typically becomes the 2nd line of the
current msgctxt i.e. the #define of the string or stringarry
For .ui strings the msgctxt typically becomes uifilename|widgetname
(caolanm->cloph: will this script suffice for getting pootle updated ?)
In our code I've autogenerated matching initial contexts for the
matching .ui and .hrc source strings.
(newly added strings can have arbitrary meaningful context strings
e.g. NC_("papersize", "A4") its just the existing ones that will have
ones mechanically generated from the existing metadata available)
Is there any outstanding concerns or questions.
--
To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-l10n] where do the canonical translations live, git or pootle
On Wed, 2015-01-28 at 10:20 +0100, Stephan Bergmann wrote: On 01/19/2015 11:03 AM, Sophie wrote: - if there is a way to script changes, script them otherwise wait until there is a script available to commit them I am not sure I understand you here (to me, the otherwise part reads: if there is no way to script changes, wait until there is a script available, which would not make sense). When talking about (developer-side) scripting, is it actually OK to commit modifications to the translations in the translations git sub-repo? My understanding was that such modifications would be overwritten by the next import commit (as typically done by Andras, AFAIU from some Pootle database). This has always been a clear as mud to me as to what the *current* translation workflow is and how as a developer I can fix a translation. e.g. in the past changing the Letter size translation in Spanish to Oficio instead of the literal translation was a pain. And right now I want to fix a gadzillion Indic translations short-cuts to ascii chars and not characters that only available via IM. What I want to do is to commit to the translations git repo and forget about it. Does that work ? C. -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-l10n] Re: where do the canonical translations live, git or pootle
On Thu, 2015-01-29 at 15:24 +0100, Christian Lohmaier wrote: Hi Caolán, *, On Thu, Jan 29, 2015 at 3:10 PM, Caolán McNamara caol...@redhat.com wrote: On Wed, 2015-01-28 at 10:20 +0100, Stephan Bergmann wrote: On 01/19/2015 11:03 AM, Sophie wrote: What I want to do is tp commit to the translations git repo and forget about it. Does that work ? Nope, as on the next export from pootle those changes will be overridden again. The changes need to be done in pootle. (not necessarily via web-UI, that would be tedious, but the change needs to be reflected in pootle to stick). But as some languages use offline translation, even doing the change in pootle might be undone when teams just upload their local copy again without bothering to check for updates that were done in pootle. So IMO there's the root of the problem. Lets say a developer does want to make LibreOffice comply with the GNOME HIG and stick full colons at the end of every label that is a label for another widget and is willing to fix all the translations at the same time then he can't really do it. So there really needs to be some way for developers to mass change translations themselves, and ideally a trivial way. I think we should not worry too much about the offline upload and overwrite style case. There's no helping that :-) C. -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-l10n] Re: Need info on sd/source/ui/accessibility.po for l10n
On Mon, 2014-05-12 at 18:35 +0200, Sophie wrote: Hi all, We (l10n team) need some information for localization purpose. In libo43_ui/sd/source/ui/accessibility.po, some strings in the form of PresentationOutlinerShape UnknownAccessiblePresentationShape Few of our languages support this sort of notation where there is a mix of capitals in one attached word. How should we translate that, are we allowed to separate the words (add spaces or underscores) and remove the capitals? Where does it appears in the UI? Looking at where they get used, they are the accessibility descriptions for the things they describe, presentation pages and notes and so on. So you'd need an accessibility tool to hear them read out as you select them in the UI. Anyway, it looks completely safe to separate them with spaces and remove the capitals etc, and just format them as natural for your language. We should probably separate them in the English version too. C. -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] space between values and units in spinners, fdo#71688
On Tue, 2014-01-21 at 21:19 +0100, Martin Srebotnjak wrote: for Slovenian I already asked to include space in front of % and it was done. I also changed all translated strings accordingly. It was done for 4.2 or even before, can't remember. Hopefully those settings for Slovenian were inherited by 4.3. The translations of % of vcl/LANG/source/src.po are now no longer used in favor of the icu-based percent formatter. I checked the CLDR list[1] and sl is not listed there as using a space, so I suggest you submit the correct pattern to CLDR for sl at http://cldr.unicode.org/index/bug-reports In the mean time I have now added sl to the list of special cases (along with es) that CLDR has currently the wrong data about and force a space in there, so 4.3 should now again retain the space for sl C. [1] http://www.unicode.org/cldr/charts/24/by_type/numbers.number_formatting_patterns.html -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] space between values and units in spinners, fdo#71688
On Tue, 2014-01-21 at 11:32 -0600, Adolfo Jayme Barrientos wrote: On Tue, Jan 21, 2014 at 5:59 AM, Caolán McNamara caol...@redhat.com wrote: [...] c) If you agree with icu's % formatting for your language then update the translations for X% to be consistent with that formatting. Otherwise we can fix icu or make a blacklist of languages which should be excluded from the default icu percent formatting. Caolán, how can we submit a fix for ICU? For instance, Spanish formatting should be exactly the same as German, i.e. “#,##0 %”. So icu gets them via the CLDR, see the chart at http://www.unicode.org/cldr/charts/24/by_type/numbers.number_formatting_patterns.html and see the how-to-update guide at http://cldr.unicode.org/index/bug-reports The CLDR is an awesome piece of work, e.g. default paper sizes of regions and so on. It's worth knowing about it and worth checking that it's right for your locale to help out all projects. For LibreOffice I can special case Spanish to have a space between the value and %, but is it a normal space like between words or should it be a narrow space like Stephen dug out from his German style guide. C. -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-l10n] space between values and units in spinners, fdo#71688
For 4.3 we are now, in the normal case, putting space between values and units in spinners. e.g. now 10 mm instead of 10mm. (http://en.wikipedia.org/wiki/ISO_31-0) For the degree symbol we are not putting space between value and unit, i.e. it remains 10° I think those are hopefully uncontroversial. The tricky case is the % symbol, because, while ISO-31-0 implies that 10 % is the preferred scientific format, English style guides prefer 10% and 10 % looks just plain wrong. It's a locale-dependent formatting rule (http://en.wikipedia.org/wiki/Percent_sign) So to resolve this we now have a function formatPercent which takes the number and the locale and runs it through icu's PercentInstance to format it according to that locale's formatting rule. Which gives e.g. 10 % for de and 10% for en. (http://site.icu-project.org/) What this means is that: a) In the English strings in .src files the source text should not have a space between number and %. I think these are all fixed now. b) You should check that the icu percent formatting rule is considered correct for your language in the context of a office suite UI e.g. in the spinner of view-zoom-zoom-variable c) If you agree with icu's % formatting for your language then update the translations for X% to be consistent with that formatting. Otherwise we can fix icu or make a blacklist of languages which should be excluded from the default icu percent formatting. C. -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-l10n] Re: l10n process, en_US version, Help files
On Wed, 2013-12-11 at 17:19 +0100, Sophie wrote: Hi all, This mail is posted to the dev list and the l10n list, please follow up on the l10n list. I would like to open a discussion on the l10n workflow, the quality of the en_US version and the Help files. All is linked and I would like to discuss how we can improve the process here. I'm sure that having a better understanding between the l10n process and the dev process should help us to improve things :) So here is a proposal, it's a bit long, sorry for that. *Before updating Pootle: - it's important for l10n team to know the approx load of work that will be needed to achieve the whole work. Time between beta1 and rc1 is short and that will help to better organize this time between translation and proof reading. - depending also on the type of changes, we could use different tools to optimize the work. *When the l10n start: - we need a continuous communication and a planing of the updates made in Pootle, those translating off line are always frightened to lose something in the run. - it's exhausting when you think you are over and to see a new bunch of words coming. Knowing it in advance help to manage the time too *After RC1 and l10n integration - we need to know when integration is made after our fixes, there is currently no communication on this == for these three items, I have asked today to Andras and Christian how we can put that in place and where I can help them to do so, knowing also that Christian is managing this part almost alone now. *About the en_US overall quality - the process to rely on the l10n team to fix the en_US version is ok, even if it gives us extra work to understand what is meant before we realized it's a mistake. So it's also error prone for all the translations. - but that doesn't solve the several typos that already exist and that are overlooked by the l10n team (e.g in the Character Font Effect dialog, there is Overline _c_olor and Underline _C_olor and this is the same for several dialogs) - that doesn't solve also the lack of universal vocabulary used in several dialogs (e.g Tab/Pane/Panel/Deck to name the same object or Graphic/Picture/Image). I've nothing to propose here but to define a glossary where developers could pick the good word but I'm not sure it will be used * About the help files - I always wonder why there is a Help button on a new dialog when no help file is appended ;) One thing that we could with the new .ui file format is to confirm if each dialog actually has a help entry for it. There is an easy hack at https://bugs.freedesktop.org/show_bug.cgi?id=67350 to extract out the new-format helpids from the help and determine if they actually exist. That would weed out typos where the help gets detached from the thing it documents. Similarly someone could script if each new-format dialog has a help entry and make a list of stuff that is missing help and turn those into a list of tasks to document those things. Another thing that could be automated is to generate a skeleton help page from a new-format dialog. i.e. generate the help ids bookmarks for the interactive widgets, buttons, checkboxes, etc. and have fill-me-in headings and bodytext. C. -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-l10n] Deckard: a web based Glade Runner
On Wed, 2013-06-12 at 12:58 +0300, Коростіль Данило wrote: Added Nicolas, who is the developer. Top-posted to keep content. On Wed, Jun 12, 2013 at 2:05 PM, Miloš Šrámek milos.sra...@oeaw.ac.at wrote: Hi, there exists a web-based tool for display of translated glade dialogs: https://launchpad.net/deckard gnome dialogs: http://deckard.malizor.org/ It would be really great to have something like that for LO - it would simplify our work and simultaneously improve the quality of translations. On the launchpad page, it says: In the long run, it would be cool to have distinct instances for distinct projects like Xfce or LibreOffice. As I understand it, the runner takes translation from a po file in a repository, converts it and displays the dialog. So, to see the result, it is necessary to upload po file to the repository. Can we talk to Deckard developers regarding that? Milos -- - Milos Sramek Gregor Mendel Institute of Molecular Plant Biology, Dr. Bohr-Gasse 3, 1030 Vienna, Austria TEL: +43 1 79044 9810 EMAIL: milos.sra...@oeaw.ac.at - -- sankarshan mukhopadhyay https://twitter.com/#!/sankarshan As far as I know the tool is based on GTK3+, so at least we need to wait for the port to .ui dialog system. Nevertheless, even that couldn't mean it'd support LO, but I'm not sure. +dev list and Caolán McNamara. Probably Caolán who's converting the dialogs may tell us more. And yes, it's really really useful tool for localization QA, especially for such huge project as LO. So I'm looking forward to that great feature as well. Looks great. I think it should basically just work for LibreOffice and the 250+ new .ui elements. Our .uis pretend to be gtk3 ones, with a handful of custom widgets, mostly previews. We have a glade catalog for the custom ones to provide stubs for glade. So, what does deckard do there, does it load the .ui with standard gtk3 code, i.e. expects all the widgets to be instantiatable, or does it load it the glade way, i.e. can reuse a glade catalog to handle those ? There might also be a little bit of tweaking required to stitch the .po and .ui together because we're not (currently) using gettext natively in LibreOffice but are using it as an intermediate format so it probably wouldn't work to just throw a libreoffice .po with translations for a dialog at the normal gtk3 gettext loader and get it to do the right thing. C. -- To unsubscribe e-mail to: l10n+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/l10n/ All messages sent to this list will be publicly archived and cannot be deleted
