ant then
if i want to change 'ö' to ö ??
how do i do that in xls??? :-?
And how do i change
ö
to
ö
?
Paul Clapham wrote:If you want to compare something to a string literal in an <xsl:if> element then you have to put quotes around that literal. Like so:
ant then
if i want to change 'ö' to ö ??
how do i do that in xls??? :-?
Sorry, there's not enough context to that. Where is this quoted string from which you want to drop the quotes?
And how do i change
ö
to
ö
?
Make sure that whatever is displaying that character knows that it's being encoded in UTF-8 for display. (That's a guess at your real question, too, since you provided no context for it.)
Niklas Karlsson wrote:
thanks for your repply!
please look at the updated text (but remove all "-" )
(and i use UTF-8 :-( )
Paul Clapham wrote:
Niklas Karlsson wrote:
thanks for your repply!
please look at the updated text (but remove all "-" )
(and i use UTF-8 :-( )
Sorry, what updated text?
And if you're seeing ö in your output then you aren't using UTF-8 there. It's possible (and quite likely) that your XML document is encoded in UTF-8, but whatever you use for output assumes something else.
Paul Clapham wrote:If your XML contains a degree character (as in "-999 ° C") then it's almost certainly encoded in UTF-8, but anyway you can tell by looking at the document's declaration -- either it specifies the encoding, or else it's encoded in UTF-8 (or UTF-16).
And if I understand your situation correctly, you're doing an XSL transformation which puts its output -- somewhere. And you're using -- something -- to look at that output. So there are two questions to ask about that: first, what encoding is the XSL transformation's output using? And second, when you look at that output, what encoding is that looking thing assuming?
You seem to think that "ö" is in your XML document somewhere and that you can deal with it on that basis. But the "ö" character requires two bytes when it's encoded in UTF-8. If you use UTF-8 throughout the process then you'll see that character on your screen. But if at some point your software interprets those two bytes as if they were encoded in ISO-8859-1 or cp-1252 or some similar encoding, then you're going to see "ö" on your screen. So as I've explained, there are two places you have to look at to find out where the problem is.