August 28 - Translations Live on Desktop For Members!
August 28 - Translations Live on Desktop For Members!
Big thank you to everyone who has helped with the translation project!!! Your efforts can now be seen in ACTION on member accounts!
You can access this update by going to your settings (on your member acct) and looking for the BRAND NEW "Language Preferences" section!
It looks like this:
Big thank you to everyone who has helped with our translation project! This is truly a FOR THE COMMUNITY BY THE COMMUNITY EFFORT! It is a project we should all be proud of!
Special thanks to @Jake for taking the lead in managing the project in recent months. We are very happy to have his help and support.
We will continue to add new translations, it will be ongoing... but thisis a great start!!
Woohoo! This is a fantastic update and I'm excited to see it help many more members!
@Laura I asked about context in many translations and never got responded. We all know that word-to-word translation off context are low quality and can make non sense. For this reason, I was forced to pause it. It is important for me to make a good job and accurate translation.
@TortueDesBois those translating are fluent in the language they are translating. We translate in phrases to add fluidity to the words themselves. We also have proofreaders that go through and double check the translation to be sure it does sound right and not like someone put it through Google Translate. Does this make sense?
@Teagan
Sometimes, we NEED the context, mainly when there are isolated words. My native language is French. I'm very comfortable reading English too. I'm translating from English to French. I requested the context of some words or expressions, for making sure that I'm getting it right in the context. It would be essential that they reply about the context so I can actually translate them properly. By example, if it's a button, a menu or a directive. I know for sure that "Feed" is not about giving food, because I know the site enough. But sometimes I'm not sure where it is on the site or what the context is. If they want accurate translations or the work being done correctly and in a timely way, they should give those informations.
I also seen people translating words without take into consideration the context or where its located on the site. Some translations sounds such bots. I reported some of those people in past. But I understand why they sometimes just go by "guess". We don't have the context and can't get it. And some people prefer going faster than waiting for those informations. NOT ME. I want the context before to continue to translate. I don't want make a bad job.
Quick request- can we have an English (UK) option? I saw my member account in the GRs saying it's American English- as a Brit, I actually find this a little offensive (if you know me you'll know I'm very proud and protective of British English). It's rather upsetting to a lot of Brits to be labelled as not speaking our language. (Yes I know this sounds a little psycho but it's an easy fix surely?)
Edited by Lucy to add- Just saw we have Quebecois French as well as European French? So why not British/Aus/Canada/NZ English?
Yes, and Spanish speakers around the world have all been transported to Mexico! So that's one design fault. The solution is to remove the country code, except for languages like French that really do have different versions in 7 Cups.
Another design fault is that a single setting is being used for both the user interface and the content. This is a big problem. Suppose I prefer the UI in Hungarian. Forcing my chat language to Hungarian severely restricts my ability to connect with a listener. The solution is to have two separate settings.
And another problem, in the implementation rather than the design, is that the translation is incomplete, so when I read a page I'm constantly having to switch my thoughts between languages. We should not offer to translate the site unless we really mean translate the site.
And what does "No Preference" mean? When I select No Preference it just changes back to English (US).
And lastly, the menu choice for English (US) says "(translate site)" but US English is not a translation! Similarly, English (with no country code) should be the default in the general request queue. I don't imagine many members really have no preference and are able to chat in any language in the world!
Maybe in future some more work could be put into site updates before they go live? This kind of thing has happened before.
@Lucy @john7ux
