[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Can we move kf5_entry.desktop files into kconfigwidgets.git?
From:       Luigi Toscano <luigi.toscano () tiscali ! it>
Date:       2021-08-23 7:46:32
Message-ID: 0e527c81-c8cf-7bee-453d-0da7afa2dd2d () tiscali ! it
[Download RAW message or body]

Alexander Potashev ha scritto:
> Hi,
> 
> I would suggest that we move the files `kf5_entry.desktop` from
> `trunk/l10n-kf5/*/messages/kconfigwidgets/kf5_entry.desktop` into the
> kconfigwidgets source code repository, presumably into
> `kconfigwidgets.git/src/languages/*/kf5_entry.desktop`. A similar file
> for US English `kconfigwidgets.git/src/entry.desktop` can also be
> moved to `kconfigwidgets.git/src/languages/en_US
> /kf5_entry.desktop`, for consistency.
> 
> kf5_entry.desktop files belong to source code because translators
> aren't supposed to directly edit these files, and we can simplify
> translations' automation scripts
> (https://invent.kde.org/sysadmin/l10n-scripty). A side effect is that
> `kconfigwidgets._desktop_.pot` and `l10n._desktop_.pot` would converge
> to just one file `kconfigwidgets._desktop_.pot`, however I don't think
> it's a bad thing.

Merging files with a long history could be a bit problematic from the
licensing point of view and I think it would be better to avoid that.

> 
> 
> Is anyone currently working or planning to work on this move (or a
> similar solution)?
> Is there a tracking bug/Phabricator task?

The plan is to actually get rid of those files, adding new classes in KI18n
and relying on external translations:
https://www.volkerkrause.eu/2021/05/22/kf5-iso-codes-api.html



-- 
Luigi
> 

[prev in list] [next in list] [prev in thread] [next in thread]