This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Translation of product's core objects leads to imprecise and inconsistent UI and documentation
This affects all IBM products: while the complete localization of products might be a great feature for non-technical products in order to lower entry barriers and reach more customers, it is a disaster for engineers and programmers.
Engineers and programmers need to be precise in their language, thus names of objects are very important. However IBM's translators seem to translate nearly everything - even the objects that have been "invented" by the product itself and don't exist in the real world / language.
Examples: Node (en) - Knoten (de) ...although in common language "Knoten" and "Knotenpunkt" get mixed, only the latter has the abstract meaning of "node". A "Knoten" is just a knot and you don't want that in your message flow.
MessageFlow (en) - Nachrichtenfluss (de) ...actually this translation is not bad. But message flow files have the extension ".msgflow", even in the german UI, so you won't get rid of the english word. That's an inconsistency.
QueueManager (en) - Warteschlangenmanager (de) ...you might think of a guy in front of an Apple store yelling "go back into the line!!!" ...so the german translation is nonsense. For consistency you should also not translate "Queue" into "Warteschlange".
Breakpoint (en) - Unterbrechungspunkt (de) ...no german programmer has ever translated breakpoint.
Typetree structure (en) - Typenbaumstruktur (de) ...this one is from the WTX plugin for IIB. And nobody would ever unterstand what the german word could mean.
Deploy (en) - Implementieren (de) ...now that's even worse: "Implementieren" is a pretty common word for programmers in Germany, but its main meaning is not "to deploy", but "to implement". Since there's no precise translation for "deploy" in german we tend to say "deploy", too.
I don't want to start a discussion about better translations, because that might be related to personal taste. Instead I want to start (or join) the discussion about where to draw the line of translating objects at all.
Many people might be afraid that the result being "denglish", a mixture of languages, and that might be true - but it's precise. And that's what the main audience of the developer tools care about.
P.S.: At least for the UI there's an easy solution: install the english version by default and let the user opt-in for a localized UI. Currently it's the other way round. However the german documentation should contain more english names, too.
Do not place IBM confidential, company confidential, or personal information into any field.