New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Localization Upgrades #691
Conversation
Fixed conflicts with develop. |
…o localize Conflicts: conf/defaults.config lib/WeBWorK/ContentGenerator.pm lib/WeBWorK/ContentGenerator/Instructor/ProblemSetDetail2.pm lib/WeBWorK/ContentGenerator/ProblemSets.pm lib/WeBWorK/URLPath.pm
Hi Goeff. The localization pull request now has conflicts probably because there were some maketext changes in the earlier achievements PR. It's probably best if you compare the 5 files that have simultaneous changes and make choices. I'd probably get the choices right but there is a chance that I wouldn't understand which is the right one. I'll check and pull the localization PR as soon as you have the conflicts resolved. |
Conflicts resolved. I also updated the po files to include strings added by #686 |
…o localize Conflicts: lib/WeBWorK/AchievementEvaluator.pm lib/WeBWorK/AchievementItems.pm lib/WeBWorK/ContentGenerator/Instructor/AchievementList.pm lib/WeBWorK/Localize.pm
OK. It’s all good so far. This review may take awhile. Take care, Mike
|
The edit button on the course info and problem set info (problem header ) pages blends in with the background instead of standing out in white. --- this might be because the xXx brackets are interfering with the style sheets or the javaScript |
It is because of the xXx. The xXx will be removed before this is pulled On Thu, May 19, 2016 at 4:27 PM, Michael Gage notifications@github.com
|
what else needs to be done here? Is this ready to pull? |
I would need to remove the xXx brackets before we pull. Another possibility is to solicit feedback from various translators. It would be a good time for them to take a look at the pot file (I put the latest one on Transifex) to see if any of the strings need to be reworked. |
xXx debugs removed. |
On second thought lets pull this. There are changes in a lot of files and there is more chance that we will generate conflicts with feature branches the longer this sits around. |
I agree. |
update_localization_files
which will updatewebwork2.pot
and all of the po files. In theory we can ask any developer making a pull request to run this. That will keep our language files a little more up to date.maketext
calls to many new things. So many maketext calls...x
which can be wrapped around strings and leaves them unchanged. This is for when the string is defined as a constant (and$r->maketext
) isnt present. The constant can be fed tomaketext
for translation and thex
function around the string definition allowsxgettext.pl
to scrape it for the pot file.maketext
definitions to help with debugging. This is a temporary change and should be reverted before the pull is merged.To test: Check out this branch, as well as the corresponding PG branch (openwebwork/pg#273) The entire interface basically needs a once over. Each page (that we still support) should be visited and interacted with. Things to look for:
If you find missing maketext strings you can post about it here and I will fix them, or you can make a pull request to the
localize
branch on my github and I will pull those changes there.In some ways this pull request is not completely done. The template pot file has been updated to include a ton of new strings and all of the po files are very out of date. Keeping the translations current, though is likely to be an ongoing project. So if you know someone who is bilingual and likes WeBWorK let them know.
Edit: We are managing the actual translation of the pot file at https://www.transifex.com/webwork/webwork2/ You should direct people here if they are interested in doing translation for WeBWorK.