Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0013792
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] E. Translationmajoralways2010-06-28 03:132022-02-01 08:08
ReporterskengakuView Statuspublic 
Assigned ToTriage Platform Base 
PrioritynormalResolutionopenFixed in Version
StatusacknowledgedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product Version2.50MP14SCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0013792: Every single Help Title turns out to be wrong in Japanese

DescriptionI am wring this to attract Openbravo Development's ATTENTIONS.

When you click the "?" icon in the top left, a Help screen gets popped up. After translating MP14, it turns out every single Help SCREEN TITLE is wrong.

In the below, "Lower case" means an English word, "UPPER CASE" means a Japanese word.

1. In PO files, "Help for" and "tile" are in different lines.
2. In English "Help for""title" is displayed in a Help screen.
3. But once translated in Japanese, proper word sequence becomes "TITLE" "FOR" "HELP".
4. Once I change the User Option Language to Japanese, every single help pop-up screes shows its title, "FOR" "HELP" "TITLE", which is quite odd.

In a future MP release, please please ple-----ase DO NOT use this technique, please DO NOT under estimate structural differences among different languages.

I assume there are more of these cases. To rescue the most visible Help screen, I will change the Japanese translation for "Help for", but it will cause different problems, if "Help for" is used in ifferent contexts.
Steps To Reproduce1. Install Japanese Translation Module for MP14:
2. Change User Option / Language to Japanese, from English:
3. Click "?" icon top right:
Proposed SolutionDo not separate a message sentence in multiple parts.
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
depends on feature request 0005897 acknowledgedTriage Platform Base Errors messages with parameters 
Not all the children of this issue are yet resolved or closed.

-  Notes
(0028807)
alostale (manager)
2010-06-28 08:51

 Please, could you provide any concrete example of this incorrect behavior, just to make it clearer?

Thanks
(0028808)
skengaku (reporter)
2010-06-28 08:59

 Unless you don't read Japanese, it's quite challenging to give you a concrete example.

"Help for Business Partner" is the one of examples.
The translation of "Help for" is "のヘルプ";
The translation of "Business Partner" is "ビジネスパートナー"

"Help for Business Partner" is actually "ビジネスパートナーのヘルプ"
but with the current MP14, it's displayed "のヘルプビジネスパートナー", which is quite odd.
(0029030)
iciordia (manager)
2010-07-03 09:47

 Skengaku, Asier,

this issue would be completely solved with feature request 5897, but not before. Translations should be allowed to change the order of the parameters in the message. I am prioritizing this one, but it won't happen after the summer at least.

Ismael
(0029032)
skengaku (reporter)
2010-07-03 11:58

 I got you, but I'm not so sure, if it could be a resolution or not. Let me just verify it once it becomes a reality.

Let me leave a comment that I have to disagree with your comment, "Translations should be allowed to change the order of the parameters in the message".

While I translate PO files without any contexts, I have absolutely no clues about such a order on any screens. Also I have absolutely no clues which part is used in what contexts, whatsoever!!

Meaning, I have no chance changing such a order while translating.
(0029773)
iciordia (manager)
2010-08-03 18:10

 Skengaru,

there are two different aspects in your requirement:
1) when translating a message it should be possible to change the position of variable parameters in the message since different languages can have different possitions
2) it is very difficult to translate Openbravo messages without any clue about the context of that message. Best way to get the context is from Openbravo UI itself.

Feature request 5897 would solve the first aspect, while an additional tool would be needed to solve the second. My idea for this is to allow the translator to do it from the Openbravo UI directly, so you can "right click" any label or message in the system to directly open the tranlation editor for that message.

Ismael
(0046899)
iciordia (manager)
2012-03-29 16:30

 This issue can not be managed as a bug, it requires the FR 5897 and then review all splitted messages and merge them including the parameters (variable part) on them. So I move the issue to the design defect pool.

Ismael
(0052489)
AugustoMauch (manager)
2012-09-24 23:32

 Effort: 10
Impact: mid
Plan: mid

- Issue History
Date Modified Username Field Change
2010-06-28 03:13 skengaku New Issue
2010-06-28 03:13 skengaku Assigned To => alostale
2010-06-28 08:51 alostale Note Added: 0028807
2010-06-28 08:51 alostale Status new => feedback
2010-06-28 08:59 skengaku Note Added: 0028808
2010-07-03 09:47 iciordia Note Added: 0029030
2010-07-03 09:47 iciordia Relationship added depends on 0005897
2010-07-03 09:51 iciordia Priority normal => urgent
2010-07-03 09:51 iciordia Severity critical => major
2010-07-03 09:51 iciordia Status feedback => scheduled
2010-07-03 11:58 skengaku Note Added: 0029032
2010-08-03 18:10 iciordia Note Added: 0029773
2012-03-29 16:30 iciordia Note Added: 0046899
2012-03-29 16:30 iciordia Type defect => design defect
2012-09-24 23:32 AugustoMauch Note Added: 0052489
2012-09-24 23:32 AugustoMauch Priority urgent => normal
2017-03-31 14:36 alostale Status scheduled => acknowledged
2017-04-10 14:34 alostale Assigned To alostale => platform
2022-02-01 08:08 alostale Assigned To platform => Triage Platform Base

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker