When considering how to best approach this idea, it seemed as if the best solution was just essentially a giant dictionary for each individual language, with the words updating based on your language preferences/geography.
Here is the beginning of the structure of the dictionary I am building. All site buttons/etc will by determined by the results of importing Lang, and using it like so:
instead of "Explore" on the backed it will look like: "Lang['explore']['en']" for english, "Lang['explore']['cn']" for chinese, etc. Capitalization can be handled by passing function arguments specifying which letters should be emphasized. For example, 'explore' would be "get_lang('explore', 'en', [1])", which would result in "Explore" showing up on the page.
Thankfully, there aren't too many phrases on the site.
I could write a script to automatically translate all these words for me, but I know enough about languages to know that would be a terrible idea. It is a thought, though.
I apologize for the delay leftover from last week, I have several days guaranteed free to work on this project this week, and I won't go MIA again anytime soon, even though I won't be avaliable Thurs/Fri as I have to fly cross country for job interview.
Plus, I was able to get the inline-expansion stuff effectively completed today. There still needs to be style tweaks, but yeah, it's there.
There's a website called Rev.com that pays "freelancers" from other countries slave wages (by our standards but not there's) to do translation jobs. I don't know how much it would cost but they are really fast especially for an easy translation job like this.
I dunno how other websites do it though, whether they have a translation script or if they hire translators.
Try submitting a post to https://www.reddit.com/r/translator/. I don't know if the sub is aimed to this type of work but if so, some people might be interested.
As silver mentioned, the translations should prioritize smooth structure over verbosity. I'm not nearly qualified to have an opinion on this, I'll take whichever translations I can get regardless!
I'll work on the final step of this implementation tomorrow. I'm leaving wednesday for a job interview, so I'm going to try and get things completed by then.
That being said, I'm not nearly qualified to judge the quality of xyz translation. I'll innately value the judgement of native speakers over my own when it comes to word choice, the only important thing is that the key remain in english si I can know wtf is going on!
Here is the beginning of the structure of the dictionary I am building. All site buttons/etc will by determined by the results of importing Lang, and using it like so:
instead of "Explore" on the backed it will look like: "Lang['explore']['en']" for english, "Lang['explore']['cn']" for chinese, etc. Capitalization can be handled by passing function arguments specifying which letters should be emphasized. For example, 'explore' would be "get_lang('explore', 'en', [1])", which would result in "Explore" showing up on the page.
You can find the basic structure of the file I just finished typing up here https://github.com/civicsoft/ieddit/commit/883a5dc698780513d543a05cf7bd3497c5210b9f
Thankfully, there aren't too many phrases on the site.
I could write a script to automatically translate all these words for me, but I know enough about languages to know that would be a terrible idea. It is a thought, though.
I apologize for the delay leftover from last week, I have several days guaranteed free to work on this project this week, and I won't go MIA again anytime soon, even though I won't be avaliable Thurs/Fri as I have to fly cross country for job interview.
Plus, I was able to get the inline-expansion stuff effectively completed today. There still needs to be style tweaks, but yeah, it's there.