Community
Participate
Working Groups
3.5RC1 Steps: 1) Create a general project using at least one non-ASCII character 2) Open the project context menu and use "Configure > Convert to Plug-in Projects" 3) All necessary files are added, however there are problems with non-ASCII characters in MANIFEST.MF See the attached screenshot.
Created attachment 136193 [details] Screenshot illustrating the issue
The reason this is done is because on conversion, we generate a BSN. The BSN is only ASCII characters. I propose close WORKSFORME unless you have an enhancement or bug request :)
What is usually done is such cases, non-ASCII characters are replaced with suitable ASCII characters. In the case from the screenshot it would be "wozek". Maybe someone from the community would like to address the issue :-)
Is there something in ICU4J that does that? Or somewhere in Eclipse code that we could reuse?
I was not precise. I've seen this in some other apps, not in Eclipse itself. About ICU4J, I think that someone from the UI team should be asked. Maybe Kevin.
Paul is our ICU4J expert (or at least knows more than me).
(In reply to comment #6) > Paul is our ICU4J expert (or at least knows more than me). I've asked the ICU guys, I'll post when I know more. Dani, is there anything in text that does what they're asking? Or more generally, do we have an action that can convert one encoding to another. I'm always getting hit by (c) or ae being entered on windows and preventing my files from compiling on linux because they can't be read by UTF-8, and I haven't been able to find a good way to "cleanse" the files (aside from finding the offending chars and using sed 's//g' :-) PW
>we generate a BSN BSN? Is this some standard?
I wonder how you can say "WORKSFORME". For languages like Hebrew the convert-functionality is simply always broken. Not sure what support you expect from ICU or Text: the name is correctly available, the manifest.mf is UTF-8 and the PDE editor supports non-ASCII hence you only need to get the conversion right.
(In reply to comment #8) > >we generate a BSN > BSN? Is this some standard? Bundle Symbolic Name? I'd expect that as long as the non-ASCII characters can be expressed in UTF-8, it would work fine.
(In reply to comment #3) > What is usually done is such cases, non-ASCII characters are replaced with > suitable ASCII characters. In the case from the screenshot it would be "wozek". > Maybe someone from the community would like to address the issue :-) > While no longer relevant, ICU contains com.ibm.icu.text.Transliterator which can do this (when configured with the correct rules). PW
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.
