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
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
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
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
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,
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
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
>
>
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
> > se
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
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.
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
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
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]:
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 :
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:
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
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
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
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
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
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
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
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
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
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
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
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
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
28 matches
Mail list logo
