Add context, glossary and screenshorts in translations

susanthenerd

I'm translating into romanian and in many places having a context/glossary/screenshots of the source would make it much easier.

It would make translating so much easier. Providing a better context especially for small phrases would help translators understand what should be written in a given place the best. Languages like romanian have for different contexts different words that would be better used. Also glossary support would be awesome for better consistency (in the idea that translators can pick together a given translation for something and keep it consistent when that name appears). Or just screenshots would make it be make it so much easier.

stoyle

I'd like to help translate kagi pages to my mother tongue. But doing so is slightly scary, I don't want to misinterpret something which by others would make kagi look "silly".

Just seeing the English translation and the key does not really show the entire context of where a key is used. So it is rather easy to get something slightly wrong. Also some text have very limited space, something one would just have to guess in localazy.

So here are a couple of suggestions

Use feature flags to let translator preview "current" translations, or last deployed at least.
Allow a given set of users to switch to a translation not yet "published". E.g. a query param. , value stored in session storage.
Render translation keys, in stead of translations, e.g. with a query param, value stored in session storage. This could also be just meta keys in html, e.g. a data prop.

Or anything else providing context of where and how a given key is in use.

susanthenerd

I also asked for the same thing in #2448 and got no response. It would be so much usefull

Vlad

You can always leave a comment on Localazy for a given string if you are unsure. We simply do not have resources to do what you are asking for right now.