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 95888 - source code conversion from linux to windows and vice-verça
Summary: source code conversion from linux to windows and vice-verça
Status: RESOLVED DUPLICATE of bug 42638
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 5.x
Hardware: All Linux
: P3 blocker (vote)
Assignee: issues@editor
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-18 23:39 UTC by mhamednetbeans2
Modified: 2007-11-05 13:44 UTC (History)
0 users

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 mhamednetbeans2 2007-02-18 23:39:24 UTC
after saving a project on linux os the javadoc and the source code that contain
special character like 'é', 'à', 'è', etc... dont appear right, i have the same
problem when migrating from windows to linux, im using JDK 6.0 on both systems,
netbeans 5.5 on both system too, i'm a frech coder and im using a lot of 'é' !!!
Comment 1 Vitezslav Stejskal 2007-03-05 09:18:25 UTC
This is likely to be caused by the default character encoding on each system.
Could you please try to reproduce this problem with just the notepad
application. Try running 'java -jar <jdk-home>/demo/jfc/Notepad/Notepad.jar' and
create and save a file with the problematic characters. Then switch to the other
OS and run the notepad application the same way and load the file created in the
other OS. If this exhibits the problem then your both OSes are using different
character encodings. As a workaround I would recommend using the same character
encoding on both system (preferrably UTF-8).

There are some issues filed for Netbeans to support different character
encodings and for java this should be UTF-8. I can't remember the IZ# from top
of my head.
Comment 2 Miloslav Metelka 2007-03-05 15:54:00 UTC
Yes, this should be solved in terms of per-project encoding - issue 42638.
Marking as dup.

*** This issue has been marked as a duplicate of 42638 ***