How are I18N keys synchronized between the developer and the shared repository ?
When I do a checkout/commit of a solution the i18n keys aren’t updated.
Currently i18n keys cannot be synchronized using team operations. They are stored in the i18n table both in the developer and Servoy Team Provider app. server.
So for now you have to either use the same i18n table on both, or keep the table up-to-date manually.
There already is a case created in the support system for making i18n keys subject of team sharing.
So you will have this sync possibility in the future - developer no longer using table but file-based i18n.
Thanks for the reply, can’t wait for that future update. Any suggestions on the best way to update the tables manually with respect to that the table has a servoy sequence number and with the possibility of multiple developer with their own table.
Thanks in advance,
Well, as the pks from multiple tables might overlap in your case I can only think of writing a small solution based on SQL on 2 i18n tables to combine those keys based on columns message_key, message_value, message_language. In this solution you would have to merge conflicts just like you do with the team provider.
or
Some DB specific tools might be able to help combine tables like this…