[systemd-devel] Journal Message Catalog

Keith Robertson kroberts at redhat.com
Fri Feb 15 03:01:45 PST 2013

On 02/15/2013 05:23 AM, Michal Vyskocil wrote:
> On Thu, Feb 14, 2013 at 10:46:34PM +0100, Lennart Poettering wrote:
>> On Thu, 14.02.13 15:21, Keith Robertson (kroberts at redhat.com) wrote:
>>> On 02/14/2013 03:14 PM, Lennart Poettering wrote:
>>>> Note that you may have multiple catalog files and you can distribute the
>>>> translations among multiple files. This leaves full flexibility to the
>>>> projects which want to provide message catalog entries. For example,
>>>> they could create individual files:
>>>> /usr/lib/systemd/catalog/foobar.catalog
>>>> /usr/lib/systemd/catalog/foobar-de_DE.catalog
>>>> /usr/lib/systemd/catalog/foobar-fr_FR.catalog
>>> If a project follows the pattern described in [1] do they still need
>>> to suffix every message ID therein with '-de_DE' or, can systemd
>>> discover the locale from the catalog name (ie.
>>> foobar-de_DE.catalog)?
>> Hmm, interesting idea...
>> We could extend the msg catalog compiler to look at the filename for the
>> "default" implied language if the message ids are not suffixed... But if
>> we do that, we probably should use "." as separator so that:
> What about to store localized catalogs in gettext-style subdirs instead?
> So the de_DE/foobar.catalog and maybe even C/foobar.catalog for C and
> en_US locale? If nothing it will make operations like readdir or glob
> a bit faster and users are typically interested in one (+ C as a backup) locale
> only.

Is the LL_CC dir created by the msg catalog compiler or would it be a 
directory hierarchy expected by the msg catalog compiler as input?

Just asking because I'm not sure that people would care about the 
organization of a compiled i18n systemd message catalog.  AFAIK these 
catalogs are not reusable and are specific only to systemd.

In short, if you want store compiled catalogs for performance reasons 
that way then by all means do it ,but I'm not sure that's the best way 
to organize the actual source catalogs.


>> foobar.catalog ? language is C if not explicitly suffixed in the file
>> foobar.de_DE.catalog ? language is de_DE if not explicitly suffixed in the file
>> and so on. That should be a good solution for your usecase, right?
> so either
> foobar.catalog -> C
> de_DE/foobar.catalog
> either
> C/foobar.catalog
> de_DE/foobar.catalog
> where C can be a link to en_US.
> Regards
> Michal Vyskocil
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20130215/eb13175c/attachment-0001.html>

More information about the systemd-devel mailing list