If you (and your colleagues/users) are an English native speaker, DON'T READ THIS. You don't have to bother. Lucky you.
The CiviCRM localisation has come a long way, and by now it's pretty comprehensive and surprisingly versatile. Sometimes the quality of the translated strings is a little questionable, ranging from "strange" to "funny", and sometimes far into the absurd. But that's mostly due to inexperienced translators, and nothing that a little bit of quality control by the Transifex coordinators can't fix.
There is, however, one problem that's been particularly elusive. What to do if the same English word has two or more different translations in your language, depending on the context? I'll give you an example in my native language, German:
You see the difference? Granted, German is an unnecessarily complicated language, but I'm sure there's similar examples in your language as well. Here's another one:
The problem arises when the string (like "to" or "next") is isolated in the code, e.g. for the different lables in a form or a button. However you decide to translate the string, it's going to be wrong in the other contexts. But how can we solve this?
The best approach, I think, is to add the context that string is used in - each time it appears during the page generation process. And luckily the underlying translation system, GNU GETTEXT, offers you a way to do exactly this - tag the string with a context.
This system is already being used in CiviCRM, e.g. for countries, states, or in order to separate menu entries from page content: The translation for "Home" in the menu is (in many languages) very different from the address type "Home". We just need to roll this system out to the not-that-simple cases, where the context is more than just "menu" or not.
I have started a collection of these cases HERE, and I welcome you to add all those cases that you just couldn't get the right translation for, because it would always be wrong in the other places.
The actual implementation of the changes will be a little more complex than it sounds. We have to make sure that the previous translations still work if no context-tagged translation is provided. That it works on every installation. That all the localisation tools pick it up. That it doesn't break anything. You get the picture. I will tackle this subject during the code sprint taking place right after CiviCon London. So please submit your cases until October 11th, and I will include them in the initial roll-out.