Summary: | RedHat Linux LANG=en_US.UTF-8 causes some files *NOT* to be compiled | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Barry Searle <searle> |
Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | critical | ||
Priority: | P3 | CC: | thatnitind, wesley.wright |
Version: | 1.0 | ||
Target Milestone: | 2.1 RC2 | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: |
Description
Barry Searle
2002-11-07 14:41:59 EST
Sounds like a file encoding issue. Does this also occur in WSAD 5.0 (based on Eclipse 2.0) ? Is it ok to close? Olivier, could you please try simple things in our latest to see if it works ok ? Philippe, I don't have access to a Linux box. Do you have one in SNZ? I would be great if you could try with WSAD 5.0 on your specific test cases. It is fairly difficult to reproduce your problem especially if only two files don't compile and they have nothing special. Let us know if you can provide us steps to reproduce. Thanks. I have tracked down some additional information. As mentioned before, by default RH 8.0 has LANG=en_US.UTF-8. According to O'reilly's JAVA in a Nutshell, 3rd edition p.234 under native2ascii, "javac can only process files encoded in the eight-bit Latin-1 encoding, with any other characters encoded using the \uxxx Unicode notation." native2ascii fails on the files which were not compiling. It appears that the comments in this file contain some special characters. When I switch the language, it appears that WSAD is able to do some conversion which allows the files to compile. What could we do to fix the problem? Is it still a problem? Can you provide these two files as a test case? Thanks for your help. > What could we do to fix the problem? Is it still a problem? It's still a problem. Currently it's possible to change the file remove any questionable characters. It also seems possible to change the default LANG and this may be helping convert the file somehow. > Can you provide these two files as a test case? Unfortunately they contain code I'm not allowed to send out the door. See bug 29554 and you will see two of the special characters which sometimes cause problems. One of the files in question has the text "Gov<92>t Allotment" in it which may be part of the problem; however it is difficult to reproduce using that test file outside the full environment. You seem to have a issue with character encoding. This support has been improved in 2.1 stream since 1.0. Can you reproduce your problem with latest integration build or 2.1M4 with the proper encoding set in Eclipse. See bug 29863 to find out how to set a different encoding. Any update ? I just recently got WSAD 5.0 and an in the process of rebuilding our workspace to work with the new release. If I can reproduce in this environment, I will update the bug. Any result with WSAD 5.0? I've had limited time to work on this... so far I haven't had any trouble. I will update within the next week if I receive any problems. Removing RC1 milestone. Any news on this front with WSAD 5.0? If not, we might want to close this on as WORKSFORME. Closing, please reopen if this is still an issue with a 5.0 build. seems to have been resolved |