The good news is that the Java regular expression support has a flag
which can be set for searching called Canonical Equivalence
> * <p> When this flag is specified then two characters will be considered
> * to match if, and only if, their full canonical decompositions match.
> * The expression <tt>"a\u030A"</tt>, for example, will match the
> * string <tt>"\u00E5"</tt> when this flag is specified. By default,
> * matching does not take canonical equivalence into account.
> * <p> Specifying this flag may impose a performance penalty. </p>
I tested it and it seems to work for the "Åström" example you gave. I
will try to find some time to possibly add a new checkbox to the Oxygen
Find/Replace dialog. The setting will probably induce a small
performance penalty but probably nothing too severe.
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
On 2/20/2015 4:49 PM, Jens Østergaard Petersen wrote:
> Hi Radu,
> Thank you very much. oXygen for sure does not lack features, but this
> would be a very nice addition!
> On 20 Feb 2015 at 08:46:41, Radu Coravu ([log in to unmask]
> <mailto:[log in to unmask]>) wrote:
>> Hi Jens,
>> I tested and you are right, when you paste in Oxygen on Mac you always
>> obtain the content with one codepoint per character, even if the initial
>> copied content contained two codepoints per character. This is not
>> something we can control though, we use standard API to get content from
>> the clipboard and this is how we get it.
>> One workaround would be to use the Oxygen plugin for the Eclipse
>> workbench. Eclipse accesses the clipboard in some other (probably more
>> native) way than Swing applications so on Eclipse this behavior can no
>> longer be reproduced.
>> About this remark:
>> > For oXygen, I think this would mean that the Find/Replace menu should have an option to search in a normalized manner.
>> I would add an improvement request for this and see if we can do
>> something about it.
>> Radu Coravu
>> <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger