Closed linksgo2011 closed 9 years ago
@ticup I submit some code, please check if wrong, increased international support, and a Chinese language pack
@linksgo2011 : Looks great! I was just wondering if there is any way we could manage Cody's i18n in cody itself...
@jcoppieters If I'm correct, the cms interface is already written in cody itself, no? So we could easily insert linksgo's translations into the db?
Of course, this would also mean a more difficult upgrade transition, because people would need to update their databases, whereas with the json solution they can just update cody and it will work.
@ticup I have dealt with all the template on static text above, using the __ () package, so that we can convenient to internationalization of template, because users can modify the content of the database, so we only need to change the database content in the next version
Let's try to merge this! I think the json locale files are a good choice.
but before we do:
Questions:
Johan.
jcoppieters
Because I am not familiar with the project, you may submit a change for me. I think whether can choose when creating a language? Make notes in the document, using the corresponding language themselves add language file
lin
@linksgo2011: Ok, here is what I suggest:
Redo the pull request, but now instead of doing a pull request from linksgo:master to jcoppieters:master, do a pull request from linksgo:master to the jcoppieters:i18n branch (I created it).
Like this I can just accept the pull request and then easily incorporate the suggested changes by @jcoppieters and then finally merge them into the master branch!
Thanks a bunch!!
@ticup Ok
Wow thanks man!
Johan.
Sent from my iPad.
On 25 Aug 2015, at 21:14, Tim Coppieters notifications@github.com wrote:
Closed #30.
— Reply to this email directly or view it on GitHub.
(Add a language pack, default to en, users need to manually modify the default language, then increase when creating select language.