Don't know if this had been filed in BT, but since now using iz, filing
here to be sure; please close if this is a dup - I do still these same
situations in current builds.

in some bundle files in these areas, need some clarifications on some
things as to should they be translated or not, since some are in
all lower case, which sometimes mean api kind of words not to be translated.

Thats why its a p2, since its very important to know about this for the
localization work.


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 i
n 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)

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

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

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 ...
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, there should be just jdk official font names used,
not specific fonts that dont have mappings, since it can cause fonts not
to display multibyte correctly.

and since this might be run on variety of platforms, are there other such
hardcoded names needed for other platforms; if so should be just jdk font names.
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 ?

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) ?

in same module
ICON_Palette_ExpandAll_Button=Expand_All.png
...
...

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 Co
mponents --
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 ?
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 ?