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

List:       kde-i18n-doc
Subject:    Re: Naming scheme and requirements to work for the new KCM modules
From:       Yuri Chornoivan <yurchor () ukr ! net>
Date:       2018-05-19 16:41:03
Message-ID: 6364228.MzJ0XB6SXU () localhost ! localdomain
[Download RAW message or body]

субота, 19 травня 2018 р. 19:08:06 EEST Albert Astals Cid написано:
> El dissabte, 19 de maig de 2018, a les 11:37:43 CEST, Albert Astals Cid va
> 
> escriure:
> > El divendres, 18 de maig de 2018, a les 9:52:16 CEST, Luigi Toscano va
> > 
> > escriure:
> > > Yuri Chornoivan ha scritto:
> > > > Hi,
> > > > 
> > > > Another KCM is ported to Qt Quick.
> > > > 
> > > > https://phabricator.kde.org/D12936
> > > > 
> > > > It seems that there are no clear instructions on how to deal with
> > > > translations and nobody can test if they work at all for the ported
> > > > modules (and other parts of what was once KDE and now is a set of
> > > > parts
> > > > that sometimes cannot be put together).
> > > > 
> > > > Can somebody point me to some wiki page on what exactly should be made
> > > > in
> > > > the new KCMs to make them really translatable?
> > > 
> > > As far as I know, there is no difference between the old and the new
> > > KCMs
> > > (and we have already few QtQuick-based ones).
> > > As libraries, the name of the catalog should be set only by the defining
> > > TRANSLATION_DOMAIN, and that name should match the catalog generated by
> > > Messages.sh
> > > 
> > > So the only rule should be: make sure to now change the name of the
> > > domain
> > > when porting. Or at most use kcm5_<name> in the name one and ping us.
> > > 
> > > Do you see something different?
> > 
> > As far as I understand TRANSLATION_DOMAIN only works for C++ and since
> > this
> > project has i18n calls in qml files, i don't think having
> > TRANSLATION_DOMAIN is enough.
> 
> Obviously, what is being used for i18n in QML is the aboutdata component
> name, someone with time should make sure the aboutdata component name and
> the TRANSLATION_DOMAIN (which should very seldomly be used, but that battle
> is already lost) have the same value and it matches what the Messages.sh
> has.
> 
> Yuri you were already having a look at that, can you do that?

Sure.

https://phabricator.kde.org/D12982

Thanks for your advice.

Luigi wants kcmx_* scheme so it is not trivial and we should wait for 
developers to fix this. Seems that I cannot.

Best regards,
Yuri


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