One thing that comes to my mind is that it might get confusing in "international" (english speaking) discussions when referring to a status "code" which is translated into a foreign language...

What if we use both versions - maybe like

• translated (original) or
• original (translated)

in select lists or wherever the translated status appears?

It will be too long for statuses...

I am not understanding the problem. You mean that an English person may say Pending and I say Wachten (Dutch) that we won't understand each other?

I am not understanding the problem. You mean that an English person may say Pending and I say Wachten (Dutch) that we won't understand each other?

Yeap, that could be the problem.

Yes that's it - if you guys don't see a problem at all, that's just fine, so let's forget about it

That's an interesting question btw. Potentially it could rise an issue in workflow and understanding. We need someone from JBS to help us here...

@nicksavov @dextercowley @brianteeman

We need someone from JBS to help us here...

@infograf768

+1 on translating. Even if any problems present themselves, I think there will be more pro's than con's in making the tracker more accessible internationally. Plus, there's always Google Translate :)

If the status of an item is not automatically displayed translated in the interface language chosen by the reader/poster, then we do have an issue indeed. Using Google Translate (or rather ImTranslator) would be a real pain.

The tracker item is always in English, how this is presented to the reader can be in their native tongue. This only affects the UI not the content. A status is fixed so can be translated and then understood by the reader.

For Google Translate, I meant if someone were to use their language's term in another area (e.g. Google Groups). We'd have Google Translate to fall back on in situations like that.