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 117814 - Problems with german umlauts, assuming this is a general non-US-ASCII problem
Summary: Problems with german umlauts, assuming this is a general non-US-ASCII problem
Status: RESOLVED FIXED
Alias: None
Product: utilities
Classification: Unclassified
Component: Diff (show other bugs)
Version: 6.x
Hardware: All Windows ME/2000
: P4 blocker with 1 vote (vote)
Assignee: diff-issues@utilities
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-04 17:07 UTC by jiai
Modified: 2008-11-21 15:36 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Merge Conflicts resolver windonw (32.68 KB, image/png)
2008-04-21 10:26 UTC, ris 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jiai 2007-10-04 17:07:15 UTC 
The diff component (in this case the "Merge Conflicts resolver") shows mangled umlauts when merging local and remote
files. E.g. "nötig" becomes "nötig". This doesn't affect the source code but it is really irritating when you try to
find out which problems exists when merging.

Product Version: NetBeans IDE Dev (Build 200710030000) Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b06 System:
Windows 2000 version 5.0 running on x86; Cp1252; de_DE (nb)
Comment 1 ris 2008-04-21 10:25:12 UTC 
Same issue here.

The issue seems to be related with Merge Conflicts Resolver window not displaying the file in the configured encoding
(UTF-8 in my case).
The original source window displays correctly non-us_ascii chars (please see the attached screenshot).
The main problem with this issue is that, once the conflicts are resolved, the file is saved using the same encoding as
in Merge Conflicts Resolver window, so all non-us_ascii chars aren't saved correctly.

the steps to reproduce the issue would be:
1.- Create a java source file with non-us_ascii chars.
2.- Upload it to a repo (I'm using SVN, don't know if it also reproducible with CVS).
3.- Force a conflict.
4.- Update the file, so NB can detect the conflict.
5.- Right click -> resolve conflict to display Merge Conflicts Resolver window.
6.- Solve conflicts.
7.- Save file.
8.- All non-us_ascii chars aren't saved correctly

I don't remember this happening with NB5.5
Product Version         = NetBeans IDE 6.0 (Build 200711261600)
Operating System        = Windows XP version 5.1 running on x86
Java; VM; Vendor        = 1.6.0_04; Java HotSpot(TM) Client VM 10.0-b19; Sun Microsystems Inc.
Comment 2 ris 2008-04-21 10:26:46 UTC 
Created attachment 60480 [details]
Merge Conflicts resolver windonw
Comment 3 ris 2008-04-21 10:27:54 UTC 
I also think that the priority of this issue should be raised, as it can break source code in case you use non-us_ascii
chars for identifiers
Comment 4 Tomas Stupka 2008-11-21 15:36:07 UTC 
should be already fixed.

there were some encoding related issues fiex in diff/merge in the meantime. please verify if the problem still appear in
6.5 and feel free to reopen othwerwise

thanks