While working on the translation of MMEX, I’ve come across some inconsistencies and cases where clarification is needed to ensure accurate and uniform translations. To improve consistency and avoid individual interpretations, would it be possible to have a dedicated space (e.g., a specific forum thread, a Crowdin discussion section, or a Slack/Discord channel) where translators can discuss and resolve these issues collaboratively?
Additionally, in this "Translations" section, can we use this post to report minor issues like typos, awkward English phrasing, or unclear translations? Or should we use a different tool for this purpose?
This would help maintain translation quality and ensure alignment with the intended meaning of the original strings. Let me know what you think!
Dedicated space for discussing translation inconsistencies/errors
Moderator: Renato
-
- Super User
- Posts: 79
- Joined: Sat Mar 21, 2015 9:15 am
- Are you a spam bot?: No
- Location: Italia
-
- Developer
- Posts: 646
- Joined: Wed Dec 21, 2011 5:58 am
- Are you a spam bot?: No
- Contact:
Re: Dedicated space for discussing translation inconsistencies/errors
I think you just got a good start here. this was created to serve this purpose.
-
- Super User
- Posts: 79
- Joined: Sat Mar 21, 2015 9:15 am
- Are you a spam bot?: No
- Location: Italia
Re: Dedicated space for discussing translation inconsistencies/errors
I've already submitted some translation requirements via the discussions on Crowdin, but I’m also reposting them here in case I have better luck in getting feedback.
First request: Standardizing the translation of strings with "&" symbols
I've noticed that some strings contain words with the "&" symbol.
I'm not entirely sure of its purpose, but I believe that, as in other translations, "&" might be used for keyboard shortcuts
(e.g., in "&Open", the letter "O" could be accessed via CTRL+O).
If this is the case, we should ensure that the same letter is retained in the translation.
However, if "&" serves a different function, could someone clarify its purpose so we can translate it correctly?
Would it be possible to establish clear guidelines so that everyone follows the same approach instead of translating them inconsistently?
I'm happy to review and provide context for each string affected by this issue to ensure uniformity.
Second request: Multi Transactions Update
Link to Crowdin discussion
The term "Update" suggests a general update, but this function actually allows users to select multiple transactions and modify them.
A more accurate translation could be "Multiple Transactions Edit" or "Bulk Transactions Edit" to better reflect its purpose.
First request: Standardizing the translation of strings with "&" symbols
I've noticed that some strings contain words with the "&" symbol.
I'm not entirely sure of its purpose, but I believe that, as in other translations, "&" might be used for keyboard shortcuts
(e.g., in "&Open", the letter "O" could be accessed via CTRL+O).
If this is the case, we should ensure that the same letter is retained in the translation.
However, if "&" serves a different function, could someone clarify its purpose so we can translate it correctly?
Would it be possible to establish clear guidelines so that everyone follows the same approach instead of translating them inconsistently?
I'm happy to review and provide context for each string affected by this issue to ensure uniformity.
Second request: Multi Transactions Update
Link to Crowdin discussion
The term "Update" suggests a general update, but this function actually allows users to select multiple transactions and modify them.
A more accurate translation could be "Multiple Transactions Edit" or "Bulk Transactions Edit" to better reflect its purpose.
-
- Developer
- Posts: 646
- Joined: Wed Dec 21, 2011 5:58 am
- Are you a spam bot?: No
- Contact:
Re: Dedicated space for discussing translation inconsistencies/errors
For desktop MMEX, you may refer to https://docs.wxwidgets.org/3.2/overview_i18n.html as it is fully relying on wxWidgets ecosystem
Personally, I prefer multi-transaction update as well and this is from c++ source code.
Personally, I prefer multi-transaction update as well and this is from c++ source code.