This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 78070 - I18N - not clear if some messages can or should be translated
Summary: I18N - not clear if some messages can or should be translated
Status: VERIFIED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@soa
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2006-06-16 14:09 UTC by bugbridge
Modified: 2006-11-23 20:13 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bugbridge 2006-06-16 14:09:53 UTC
Original status: 1-Dispatched; Suggested Status: NEW

Suggested Target Milestone : 5.5

Original submitter: kfrank

Description:
Some messages in some bundle files, its not clear if should be translated
or needs to be in bundle at all, and this info is needed both for l10n work
but also to be able to properly do i18n testing.

1. colons in

org-netbeans-modules-compapp-models-bpelmodel.jar
org-netbeans-modules-compapp-models-wsdlmodel.jar

for the OpenIDE lines, they need to be = signs.


2. 
org-netbeans-modules-compapp-models-bpelmodel.jar

VAL_BOTH_FAULT_MESSAGE_TYPE_AND_FAULT_ELEMENT_ARE_PRESENT = "Both
faultMessageType "{0}" and faultElement "{1}" should not be specified in catch
"{2 }";
....
and about 10 other msgs

- are the initial and final quotes needed ?
that is,  do they need to  be part of the msg user sees ?
(its ok if they do, but need to know)


4. org-netbeans-modules-compapp-projects-jbi.jar

---> Is it ok to translate these words ? If not, then #NOI18N comment is

soapaction.displayName=soap-action
soapaction.description=soap-action

inputfile.displayName=input-file
inputfile.description=input-file

outputfile.displayName=output-file
outputfile.description=output-file

... and others ...



5.  org-netbeans-modules-mapper.jar

a. 

 FONT_METHOID_TITLE=MS Sans
 FONT_METHOID_TITLE_US=Verdana
 FONT_METHOID_TITLE_JAPAN=MS UI Gothic
 FONT_METHOID_DEFAULT=MS Sans
 FONT_METHOID_DEFAULT_US=Verdana
 FONT_METHOID_DEFAULT_JAPAN=MS UI Gothic

- are these words seen in display or actually used as some choices
for fonts ?

- if they should not be translated, then need
#NOI18N comments

- if for actual fonts, should there be just jdk official font names
since this might be run on variety of platforms ?
these seem to be specific for windows.

- also, there are other locales and fonts than just Japanese,
and altho we localize just for ja and zh, any user can run
product in any locale so are font names/choices for those needed also ?


b. png and gif names for icons

normally l10n does not localize icons or even most gifs
unless there is text to translate in them (which should
not be done) -- so do these png or gif file names for icons
need to be in bundle files ? (vs being in the source code) ?

ICON_Palette_ExpandAll_Button=Expand_All.png
...
...


6. org-netbeans-modules-sun-manager-jbi

a. Are lines below with // meant for being part of some java, jsp
xml or other file and the // is for comments ?

If so, please comment in bundle so its clear to l10n.

ManageDeployments.BINDING_COMPONENTS=// -- Binding Components --
ManageDeployments.ENGINE_COMPONENTS=// -- Engine Components --
ManageDeployments.SHARED_NAMESPACE_COMPONENTS=// -- Shared Namespace Components --
ManageDeployments.DEPLOYMENT=// -- Deployments --

StatusProvider.StatusProvider=// -- Status Provider -- 
...


b. 
BI_ICON=resources/JBI.png
SERVICE_ENGINES_ICON=resources/ServiceEngine.png
SERVICE_ENGINE_ICON=resources/ServiceEngine.png
....

as asked above, do these need to be in bundle file ?


7. org-netbeans-modules-bpel-editor-expression

a.
LBL_Control_xsl:if_inputParm1=boolean value
LBL_Control_xsl:if=xsl:if
LBL_Control_xsl:choose=xsl:choose
...
...

can these be localized ? - although some obvious that they
would not be, some could be -

if not to be localized, need #NOI18N comment for each.


b. 
LBL_Operator_not_equal_inputParm1=any value
LBL_Operator_not_equal_inputParm2=any value
LBL_Operator_not_equal_outputParm=not equal:boolean value
LBL_Operator_not_equal=not equal

LBL_String_format-number_inputParm1=number value
LBL_String_format-number_inputParm2=string value
LBL_String_format-number_inputParm3=string value
LBL_String_format-number_outputParm=string value
LBL_String_format-number=format number

.... many more

---> are these lines ok to translate ?
Comment 1 Jun Qian 2006-09-17 22:08:41 UTC
I18n problems in CompApp Project (4) and JBI Manager (6) are fixed now.
Comment 2 Jun Qian 2006-09-21 01:16:56 UTC
According to Tientien, wsdlmodel will be removed by this Friday. 

That leaves us with the following modules:
 * bpel model
 * bpel mapper
 * bpel editor


Comment 3 Joshua Sandusky 2006-09-22 03:44:12 UTC
Ed Wong has fixed the I18N issues with the mapper.
Here is a summary of what he has done:

Mapper Updates

5. org-netbeans-modules-mapper
(All externalized strings have been reviewed, and strings that should not be
internationalized have been marked with #NOI18N).
a. these fonts no longer exist, the default Java AWT fonts are used instead to
ensure maximum portability/compatibility
b. the image file names should not be translated, #NOI18N indicators next to
each image file name have been added to prevent any confusion

7. org-netbeans-modules-bpel-editor-expression:
(All externalized strings have been reviewed, and strings that should not be
internationalized have been marked with #NOI18N).
a. these strings have been removed
b. all these should tooltip and label texts should be translated. Unless a
#NOI18N indicator is seen, a translation needs to be done.
Comment 4 Jun Qian 2006-09-22 21:04:00 UTC
Moving to bpel editor now...
Comment 5 Jun Qian 2006-09-23 01:29:22 UTC
BTW, bpelmodel, wsdlmodel and xsdmodel under compapp/models/ have been removed
from CVS, so (1) and (2) are no-ops.
Comment 6 Michael Frisino 2006-09-24 15:42:44 UTC
I am unaware of any remaining issues here.
Comment 7 Ken Frank 2006-11-23 20:13:00 UTC
verified