I agree there is a string freeze, but isn't more important to focus on freezing 
existing strings, rather than preventing us from doing anything for 2 weeks? I 
think in this case the pros (being able to do append to existing database) out 
way the cons (user losing their database, Chinese user seeing an English phrase 
in a beta app). 

Although I also accept it could be a slippery slope.

However if we are going for a hardline approach perhaps we can temporarily use 
an existing translation, context "OpenLP.Ui", source "Starting import...". Then 
add it to the translation bug, to fix after beta?
-- 
https://code.launchpad.net/~raoul-snyman/openlp/wizard/+merge/53199
Your team OpenLP Core is subscribed to branch lp:openlp.

_______________________________________________
Mailing list: https://launchpad.net/~openlp-core
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~openlp-core
More help   : https://help.launchpad.net/ListHelp

Reply via email to