openlp-core team mailing list archive

[Jonathan Corwin <j@xxxxxxxxxxxx>]

Well the whole .ts or .po debate has been discussed in the past, and .ts is the way we chose. We try not to reopen debates every time a new developer joins the team, we'd never get any work done :) Now we're at beta, hopefully approaching RC, it's really too late to change such decisions unless there is some really huge benefit to the end user. Looking at your advantages, although good for the developer, I'm not sure the end user will notice much improvement.

Also there are a fair few translations completed. http://pootle.projecthq.biz/projects/openlp/
Changing the way we do translations would require a conversion of existing translations, lots of testing, new translation hosting. We really haven't got the resource to do all this.

Looking through my mail archive, it looks as though there was a time that we used translate(self.context, 'string'). However we had to change the self.context to 'context' so we could use pylupdate. Of course pylupdate may have become more intelligent in the year or two which has passed since that decision was made, I don't know.

I'm hoping one of the people who actually know something about this tool will jump in and offer their input!
-- 
https://code.launchpad.net/~gerald-britton/openlp/constants/+merge/59990
Your team OpenLP Core is requested to review the proposed merge of lp:~gerald-britton/openlp/constants into lp:openlp.