Add new keys via Jabilon

[Дмитрий Нескажуев]

I can't find, how I can add new translation (new keys) via Jabilon.
Is it possible?

Hi,

this is not possible, as it's pretty pointless to add a new key when the software isn't using the key. The developer who adds a new localizable String in the software needs to create the key in the "master" language.

Greetings
.sascha

PS: For further questions please use the Google group at https://groups.google.com/forum/#!forum/jabylon and not the Github issue tracker.

I understand, for simple translation of existing software the add new feature unnecessarily.
But we try to use Jabilon during development. We want to give possibility to analitics and testers to add new keys without dev help.
Also we want to avoid merge conflicts with properties files.

I think, it's usfull feature, which can be enabled by project configuration or user permission.

[Sascha Vogt]

Hi,

Am 11.03.2016 um 13:41 schrieb Дмитрий Нескажуев:
> this is not possible, as it's pretty pointless to add a new key when
> the software isn't using the key. The developer who adds a new
> localizable String in the software needs to create the key in the
> "master" language.
>
>

> I understand, for simple translation of existing software the add new
> feature unnecessarily.
> But we try to use Jabilon during development. We want to give
> possibility to analitics and testers to add new keys without dev help.
> Also we want to avoid merge conflicts with properties files.
>

> I think, it's usfull feature,which can be enabled by project
> configuration or user permission.

We also use it for development, yet I'm still unsure what does it help
if an analyst or tester adds a key? It will not be visible in any
software (because the software doesn't use the new key).

Conflicts will also not happen. Devs add the key in the master language
(you cannot change the master language in Jabylon). Jabylon will only
adjust the properties from the translated languages. So Jabylon and devs
will never produce any conflicts.

Greetings
-Sascha-

[Дмитрий Нескажуев]

пятница, 11 марта 2016 г., 15:59:19 UTC+1 пользователь Sascha Vogt написал:

>> Conflicts will also not happen
with 8 developers we periodically has merge conflicts

>> if an analyst or tester adds a key? It will not be visible in any software (because the software doesn't use the new key). 

Tester can add missing keys during testing (after development)
analyst can add new keys before development and provide keys in issue. I know, looks very ugly, but we have free analyst's time

[Sascha Vogt]

Hi,

Am 11.03.2016 um 16:20 schrieb Дмитрий Нескажуев:
>>> Conflicts will also not happen
> with 8 developers weperiodically has merge conflicts

Sure, but not in the translation properties, as only Jabylon should
modify them, and Jabylon in itself won't create a conflict.

>>> if an analyst or tester adds a key? It will not be visible in any
> software (because the software doesn't use the new key).
>
> Tester can add missing keys during testing (after development)
> analyst can add new keys before development and provide keys in issue. I
> know, looks very ugly, but we have free analyst's time

It might be that analysts have free time, but unless some dev put a key
into the application and makes a translation visible it doesn't matter
how many keys you create. Also "creating" the key doesn't save the dev
any time (I'd guess it costs more time that way round, because the dev
needs to lookup the key instead of just picking one and adding it to the
app).

So I'm sorry to tell you, Jabylon does not and most likely never will
support the addition of new keys.

If you absolutely need to (not recommended) edit the master language
(translation) then you can workaround by creating the "master language"
a second time as translated language. Though that might lead to a mess
when the real master language and the translated one diverge.

So you could have a:
Messages.properties with
key1=Label One
key2=Label Two
Messages_en.properties
key1=Label One
key2=Label Two

Then Messages_en can be translated via Jabylon (but you will have to
regularly sync Messages_en with Messages.

Hope that helps
Greetings
.sascha

[Дмитрий Нескажуев]

Hi .sascha,

>>> Conflicts will also not happen
> with 8 developers weperiodically has merge conflicts
Sure, but not in the translation properties, as only Jabylon should
modify them, and Jabylon in itself won't create a conflict.

I tell about conflicts during development. I want to avoid them by Jabilon.
 

 

So I'm sorry to tell you, Jabylon does not and most likely never will
support the addition of new keys.

Never say never =) especially in Open Source

I can't understand, why utility application can has such strict restriction.

Just after start using of Jabilon I got requests about add/delete keys.

This is a common desire to add/delete something in same way like you edit it.


Usually applications has posobilities for messages customisation without code change.
For Example Grails domains validation. You can simply overwrite message for domain of field by new key