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 151200 - I18N - non ascii or multibyte not show ok when run application
Summary: I18N - non ascii or multibyte not show ok when run application
Status: VERIFIED FIXED
Alias: None
Product: javafx
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 6.x
Hardware: Sun All
: P2 blocker (vote)
Assignee: Adam Sotona
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2008-10-23 18:55 UTC by Ken Frank
Modified: 2011-10-19 12:05 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
image (223.94 KB, image/gif)
2008-10-23 18:56 UTC, Ken Frank
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ken Frank 2008-10-23 18:55:34 UTC
see the gif.

Although it happens in for example en windows locale when using characters
from other locale, that is not user scenario we use, at least its been one
not seen as typical for nb users; but rather the scenario used is
to be in a given locale/regional setting and expect that the characters
of that locale, when used in fx code as shown in nb editor, will show ok
when program is run via nb - am using now just the standard execution
way, since saw that other run ways might not be working yet completely.

1. simple fx program that has title and label and in which japanese characters
are used, since am in ja locale/reg setting on windows

2. run the program - the ja characters are not shown correctly.see gif and compare 
between editor view of characters (ok) and application view.

note that fx project does not have encoding property (separate issue filed)
and don't know if the feq api is used for other things so that might
be reason for it; that is, if utf-8 is assumed but files are in windows
ja encoding ie sjis/windows31j, that could be probblem or visa versa.

3. Alexandr noticed this running in en locale using Russian characters;
which is something that works in windows but I don't think its really a supported
scenario for nb.

4. if this needs to be filed for fx compiler or runtime, please do so but please
leave this issue open so can be tracked.
Comment 1 Ken Frank 2008-10-23 18:56:34 UTC
Created attachment 72552 [details]
image
Comment 2 Andrey Yamkovoy 2008-10-29 11:31:12 UTC
Looks like runtime issue ... 
Since reproduced from running application reassign to Adam.
Comment 3 Adam Sotona 2008-10-30 15:59:06 UTC
Even the source encoding is not editable, it is still defined in project properties (source.encoding=UTF-8)
If the sources are edited and generated in another encoding, it is an internal issue of JavaFX project and editor, but
nothing related to the buildsystem.

Alternation of the encoding is another issue and it is true - it has not been implemented on all levels yet.
Comment 4 Andrey Yamkovoy 2008-10-31 13:17:10 UTC
Misha, please take a look ...
Comment 5 Lark Fitzgerald 2008-10-31 19:44:34 UTC
Fix will be made in trunk to prevent destabilization.
Comment 6 cms 2008-11-07 14:02:07 UTC
Support for source.encoding added (fix for #150947, integrated to trunk: http://hg.netbeans.org/javafx/rev/399d232fd180). However since the encoding property is ignored by packager, it's still 
not possible to show non ascii/multibyte symbols while application run.

Packager should support "-encoding" argument and pass its value to javafxc.

Assigning to Adam.
Comment 7 Adam Sotona 2008-11-27 13:26:31 UTC
The issue has been fixed in trunk in dependency on the new javafxpackager option -encoding (in development version).
Comment 8 Masaki Katakai 2009-03-23 14:06:52 UTC
Verified. encoding can be specified now by bug 150947.
Comment 9 David Strupl 2011-10-19 12:05:16 UTC
Cleaning bugzilla categories ....