16
Japanese - 日本語 / Re: Status: re-generating EN canonical .pot file
« on: April 12, 2015, 02:36:48 am »
Hi Franco,
I just cleaned up my repo, (I got pretty messy in there, hack hack hack...) don't need help with the repo itself though-
When I finish the EN base, I'll gladly submit the single file as a merge request, from this branch:
https://github.com/dotike/opnsense.core.ja_JP.UTF8/tree/locale.EN.canonical
--
Basic status is this:
I've now been through 3 or 4 full passes, catching all the big issues now- and it's just down to a race to finish the last manual pass through the English .pot file.
- The branch I'm working from is now 28 days old, and I'll need to check the diff for any relevant changes to the translation file.
(Incedentally, I found a number of odd gettext calls in the source which I'll address later)
- After a lot of slogging through the source code, I could generate much of the English .pot file content in an automated manner. Yet, as with problems like this, comprehensive parsers take far longer to write than just editing the file- there are so many edge cases for how the strings are handled in the codebase.
Expected outcome: when I'm done with this pass, a functional .en POT file will be ready to push upstream, and I'll submit a pull request as soon as that's ready. Yet, there will be a few things still to do from there:
--
When the English file is done:
- Japanese, (and any other languages) can begin translation work
- OPNsense core will want to maintain the English file, as the canonical base for all other languages
- The gettext machinery will need to be hooked up in to make it all work
Best,
.ike
I just cleaned up my repo, (I got pretty messy in there, hack hack hack...) don't need help with the repo itself though-
When I finish the EN base, I'll gladly submit the single file as a merge request, from this branch:
https://github.com/dotike/opnsense.core.ja_JP.UTF8/tree/locale.EN.canonical
--
Basic status is this:
I've now been through 3 or 4 full passes, catching all the big issues now- and it's just down to a race to finish the last manual pass through the English .pot file.
- The branch I'm working from is now 28 days old, and I'll need to check the diff for any relevant changes to the translation file.
(Incedentally, I found a number of odd gettext calls in the source which I'll address later)
- After a lot of slogging through the source code, I could generate much of the English .pot file content in an automated manner. Yet, as with problems like this, comprehensive parsers take far longer to write than just editing the file- there are so many edge cases for how the strings are handled in the codebase.
Expected outcome: when I'm done with this pass, a functional .en POT file will be ready to push upstream, and I'll submit a pull request as soon as that's ready. Yet, there will be a few things still to do from there:
--
When the English file is done:
- Japanese, (and any other languages) can begin translation work
- OPNsense core will want to maintain the English file, as the canonical base for all other languages
- The gettext machinery will need to be hooked up in to make it all work
Best,
.ike