LocalizationProject
ActivePublic

Details

Description

The KDE project which touches Localization [l10n] (and Internationalization [i18n])

Recent Activity

Yesterday

aspotashev added a comment to T11721: Splitting of i18n strings.
i18n("Lorem ipsum dolor sit amet, consectetur adipisici elit, " +
     "sed eiusmod tempor incidunt ut labore et dolore magna aliqua.")
  • even if that is fixed, the two strings would be still considered separate and extracted separately; there is no way to say that they are really the same string (otherwise weird things can happen if a variable is part of a concatenation). The string should really be a unique string.
Fri, Sep 20, 1:01 PM · Localization, Kirigami, Plasma
ltoscano added a comment to T11721: Splitting of i18n strings.

Just to reiterate when I say that I will enforce the rule it means that I will do this while keeping other priorities in check, in particular that "functionality is more important to me". What I don't want to see is commits breaking the rules without giving me notice, prior discussion and a path forward. That's why I reverted the original commit.

Fri, Sep 20, 8:57 AM · Localization, Kirigami, Plasma
ltoscano added a comment to T11721: Splitting of i18n strings.

If not via newlines could it be possible to make it work by combining strings with +? Like:

i18n("Lorem ipsum dolor sit amet, consectetur adipisici elit, " +
     "sed eiusmod tempor incidunt ut labore et dolore magna aliqua.")

Not sure why this doesn't work at the moment. Is it because of this xgettext tool?

Fri, Sep 20, 8:51 AM · Localization, Kirigami, Plasma
romangg added a comment to T11721: Splitting of i18n strings.
In T11721#201554, @mart wrote:

as my personal 2 cents user facing strings are so important that they should exampted by that rule (or even the frameworks coding styles amended"
for QML, it's not easily changeable, and in general having javascriptis always kindof dangerous having newlines that aren't strictly necessary, as the interpreter can always think "let's try to put a ; in there and let's see what happens"
for qml, we should really have separate coding styles, that don't diverge from kdelibs where make sense, but the kdelibs ones really are c++ specific ones

Fri, Sep 20, 8:45 AM · Localization, Kirigami, Plasma
romangg added a comment to T11721: Splitting of i18n strings.

[...]
I find the fact that you want to give a stricter interpretation of a rule like this, which also affects other community members, a bit over the line with the powers of a maintainer. It should be part of a community discussion inside your project at least (Plasma), if not a more general one. I also personally find the fact that this is a "will" without adding a "if possible" a bit too strong; see below.

Fri, Sep 20, 8:39 AM · Localization, Kirigami, Plasma
mart added a comment to T11721: Splitting of i18n strings.

as my personal 2 cents user facing strings are so important that they should exampted by that rule (or even the frameworks coding styles amended"
for QML, it's not easily changeable, and in general having javascriptis always kindof dangerous having newlines that aren't strictly necessary, as the interpreter can always think "let's try to put a ; in there and let's see what happens"
for qml, we should really have separate coding styles, that don't diverge from kdelibs where make sense, but the kdelibs ones really are c++ specific ones

Fri, Sep 20, 8:35 AM · Localization, Kirigami, Plasma
ltoscano added a comment to T11721: Splitting of i18n strings.

This is not off-topic, because the limit you are trying to enforce is not an absolute limit, as stated in the same code that you are quoting. It's not about "code style can just go to shit". If the QML does not allow to have this, well, either fix QML (at this point probably for Qt6), there in no much to do: an important feature like translations cannot be broken, as I pointed out on IRC, with my translator co-coordinator hat on.

As already said I interpret it as an absolute limit and will enforce it this way. Besides you're reiterating what I already said: An important feature like translations cannot be broken? As I said earlier: "functionality is more important to me." Either fix QML? Well, that's what this task is supposed to be about.

Fri, Sep 20, 8:13 AM · Localization, Kirigami, Plasma
romangg added a comment to T11721: Splitting of i18n strings.

This is not off-topic, because the limit you are trying to enforce is not an absolute limit, as stated in the same code that you are quoting. It's not about "code style can just go to shit". If the QML does not allow to have this, well, either fix QML (at this point probably for Qt6), there in no much to do: an important feature like translations cannot be broken, as I pointed out on IRC, with my translator co-coordinator hat on.

Fri, Sep 20, 8:03 AM · Localization, Kirigami, Plasma
ltoscano added a comment to T11721: Splitting of i18n strings.

This is not off-topic, because the limit you are trying to enforce is not an absolute limit, as stated in the same code that you are quoting. It's not about "code style can just go to shit". If the QML does not allow to have this, well, either fix QML (at this point probably for Qt6), there in no much to do: an important feature like translations cannot be broken, as I pointed out on IRC, with my translator co-coordinator hat on.

Fri, Sep 20, 7:36 AM · Localization, Kirigami, Plasma
romangg added a comment to T11721: Splitting of i18n strings.
In T11721#201544, @pino wrote:

[...]
So @romangg: please do not use non-absolute rules as absolute hammer to enforce poor localization, and think more about the users, thanks.

Fri, Sep 20, 7:25 AM · Localization, Kirigami, Plasma
pino added a comment to T11721: Splitting of i18n strings.

BTW, since the "100 characters per line" was brought as single argument, let's actually check what the KDE Frameworks Coding Style actually say.
Quoting bits from https://techbase.kde.org/Policies/Frameworks_Coding_Style (emphases mine):

Fri, Sep 20, 6:02 AM · Localization, Kirigami, Plasma

Thu, Sep 19

cullmann added a comment to T11723: Translation of jekyll or hugo based websites .

If it helps, do all the experiments you want on kate-editor.org.
The web-server will re-pull the git all 5 minutes after some change.

Thu, Sep 19, 7:04 PM · Websites, Localization
ognarb added a comment to T11723: Translation of jekyll or hugo based websites .

Now I see that you mean, I added an import function. python3 translations.py extract directory/with/po/files

Thu, Sep 19, 5:24 PM · Websites, Localization
ltoscano added a comment to T11723: Translation of jekyll or hugo based websites .

No, I think that's the structure required by sphinx. Make sure that import_po_dirs returns the structure that you need.
Please note that the use case of docs-krita-org involves multiple pot files. If you just need one (but again, it depends on the size), this is a simpler case:
https://cgit.kde.org/plasma-browser-integration.git/tree/StaticMessages.sh

Thu, Sep 19, 5:00 PM · Websites, Localization
ognarb added a comment to T11723: Translation of jekyll or hugo based websites .

Ok so I suppose the po files need to be located at locale/$lang/LC_MESSAGES, do I need to make a bash script instead?

Thu, Sep 19, 4:55 PM · Websites, Localization
ltoscano added a comment to T11723: Translation of jekyll or hugo based websites .

Take a look at what krita does:

Thu, Sep 19, 4:47 PM · Websites, Localization
ognarb added a comment to T11723: Translation of jekyll or hugo based websites .

@ltoscano I created a merge request for translating the content of kate-editor.org https://invent.kde.org/websites/kate-editor-org/merge_requests/6

Thu, Sep 19, 4:44 PM · Websites, Localization
ltoscano added a comment to T11723: Translation of jekyll or hugo based websites .
Thu, Sep 19, 3:18 PM · Websites, Localization
ognarb created T11723: Translation of jekyll or hugo based websites .
Thu, Sep 19, 3:11 PM · Websites, Localization
romangg added a comment to T11721: Splitting of i18n strings.

Wasn't this solution mentioned here https://phabricator.kde.org/D23783#527600 ?

You mean like the following?

i18n(Lorem ipsum dolor sit amet, consectetur adipisici elit,\
     sed eiusmod tempor incidunt ut labore et dolore magna aliqua.)

True, the only difference is that the solution mentioned in D23783#527600 can not have an arbitrary indent. I'm not an expert on JavaScript string concatenation capabilities, but it would be nice to have multi-line strings not break the indent of code before and after.

Thu, Sep 19, 12:24 PM · Localization, Kirigami, Plasma
ltoscano added a project to T11721: Splitting of i18n strings: Localization.
Thu, Sep 19, 12:02 PM · Localization, Kirigami, Plasma

Thu, Sep 5

huftis abandoned D13219: Locale-aware formatting of numbers on status bar.

Should this be cancelled given this should be fixed on the latest ki18n?

Thu, Sep 5, 5:31 PM · Localization

Wed, Sep 4

aacid added a comment to D13219: Locale-aware formatting of numbers on status bar.

Should this be cancelled given this should be fixed on the latest ki18n?

Wed, Sep 4, 8:33 PM · Localization

Sun, Sep 1

huftis added a comment to D13219: Locale-aware formatting of numbers on status bar.

I’ve just tested this, but changing %1 to %L1 doesn’t seem work; the %L1 is displayed verbatim.

Did you test it with Qt's system, or KI18n? I meant to use it with tr() (KF5 Tier 1 libraries that uses Qt localization system, like KI18n).

Sun, Sep 1, 5:19 PM · Localization

Aug 10 2019

adrianchavesfernandez added a comment to D15759: Add new ways to launch pology on file(s).

How does this ‘fix’ https://bugs.kde.org/show_bug.cgi?id=198872?

Aug 10 2019, 7:30 AM · Localization

Jul 23 2019

safaalfulaij added a comment to D13219: Locale-aware formatting of numbers on status bar.

I’ve just tested this, but changing %1 to %L1 doesn’t seem work; the %L1 is displayed verbatim.

Jul 23 2019, 2:13 PM · Localization

Jul 22 2019

huftis added a comment to D13219: Locale-aware formatting of numbers on status bar.

Since this turned already into a discussion, shall we use %Lx version for KF5 libraries using Qt's translation system? I mean in the source text.

Jul 22 2019, 12:12 PM · Localization

Jun 16 2019

michaldybczak removed a watcher for Localization: michaldybczak.
Jun 16 2019, 11:38 AM
fbampaloukas added a member for Localization: fbampaloukas.
Jun 16 2019, 8:41 AM
fbampaloukas added a watcher for Localization: fbampaloukas.
Jun 16 2019, 8:41 AM

Jun 13 2019

pshinjo added a watcher for Localization: pshinjo.
Jun 13 2019, 9:00 AM

Feb 27 2019

aspotashev added a watcher for Localization: aspotashev.
Feb 27 2019, 10:11 PM

Dec 17 2018

yurchor added a comment to D13219: Locale-aware formatting of numbers on status bar.

Human's life is short. Can we have a "grace" period (say 3 years)?

Dec 17 2018, 5:48 AM · Localization

Dec 16 2018

aacid added a comment to D13219: Locale-aware formatting of numbers on status bar.

I still object to this being merged, the actual problem has to be fixed, not workarounded in every single app.

Dec 16 2018, 6:31 PM · Localization
yurchor added a comment to D13219: Locale-aware formatting of numbers on status bar.

QLocale().toString is the only thing that currently works. No other ways, like the recommended [1] ki18n*() with subs() or another formatting, do work.

Dec 16 2018, 6:02 PM · Localization

Dec 5 2018

sdepiets added a comment to D17364: Bump lokalize version to 18.12.

Uhm, the review landed already in the previous version (before some comments) and on master?

Dec 5 2018, 1:10 PM · Documentation, Localization
sdepiets closed D17364: Bump lokalize version to 18.12.
Dec 5 2018, 11:22 AM · Documentation, Localization
ltoscano added a comment to D17364: Bump lokalize version to 18.12.

Uhm, the review landed already in the previous version (before some comments) and on master?

Dec 5 2018, 10:34 AM · Documentation, Localization
ltoscano added a comment to D17364: Bump lokalize version to 18.12.

If this is targeted to Applications/18.12 as I think it is, the doc change would break the freeze. I'd suggest to leave out index.docbook from this change, and only fix it after merging the change into the master branch.

Dec 5 2018, 10:30 AM · Documentation, Localization
sdepiets updated the diff for D17364: Bump lokalize version to 18.12.

Update doc

Dec 5 2018, 10:27 AM · Documentation, Localization
ltoscano added inline comments to D17364: Bump lokalize version to 18.12.
Dec 5 2018, 10:19 AM · Documentation, Localization
sdepiets updated the diff for D17364: Bump lokalize version to 18.12.

Use cmake versioning

Dec 5 2018, 10:12 AM · Documentation, Localization
sdepiets added a comment to D17364: Bump lokalize version to 18.12.

(if you want more time to think about this, given that the tagging of Applications 18.12 is tomorrow, I'd suggest to bump the version to 2.1 on the Applications/18.12 branch now anyway)

Dec 5 2018, 9:46 AM · Documentation, Localization
ltoscano added a comment to D17364: Bump lokalize version to 18.12.

(if you want more time to think about this, given that the tagging of Applications 18.12 is tomorrow, I'd suggest to bump the version to 2.1 on the Applications/18.12 branch now anyway)

Dec 5 2018, 9:42 AM · Documentation, Localization
ltoscano added a comment to D17364: Bump lokalize version to 18.12.

The version should be definitely increased at this point.
As the new de-facto maintainer, I'd say that you can bump the version to whatever version you want.

Dec 5 2018, 9:19 AM · Documentation, Localization
yurchor added a comment to D17364: Bump lokalize version to 18.12.

Please change the version in DocBook as well

Dec 5 2018, 9:11 AM · Documentation, Localization
sdepiets added a project to D17364: Bump lokalize version to 18.12: Localization.
Dec 5 2018, 7:17 AM · Documentation, Localization

Dec 2 2018

davidedmundson requested changes to D16832: fix empty runner list after switching to new locale.

Dead runners will surely be empty on the first load. You could still have had a locale change then.

Dec 2 2018, 5:29 PM · Localization, Frameworks

Dec 1 2018

shaforostoff added inline comments to D16832: fix empty runner list after switching to new locale.
Dec 1 2018, 2:46 PM · Localization, Frameworks

Nov 14 2018

davidedmundson added inline comments to D16832: fix empty runner list after switching to new locale.
Nov 14 2018, 9:36 PM · Localization, Frameworks