I am having problems with how Domino displays selection lists in the Web when they have non-ASCII characters in it. Domino is encoding the value automatically - in a format I have no idea how to decipher.
For example, if I have a selection list with $, £ and € symbols selected, the HTML looks like this.
To confuse the matter further, if I supply a Value and Display value for it, it will not convert the values. So for example, the values are assigned Dollar | $, Pound | £, Euro | € - it will look like this - and it works fine.
This is true for selection lists, checkboxes and radio button.
Does anyone know why it does this, and if there is a way to override it?
It’s probably a workaround for how one or more browsers would encode the text value to submit it as form data when the value attribute is missing, so the answer would seem to be to supply the value attribute yourself by using an alias. There’s no law saying the alias can’t be the same as the text itself.
Subject: RE: Selection List with non-ASCII Character
That could be correct. But a browser that submit non-Ascii data incorrect is probably not being used much anymore.
I’m am hoping for a setting on the server that would turn this off. It’s obviously not required.
Correcting the DBLookups is not really a feasible solution for me. I have a global system with probably 1,000+ different lookups. Any one of them could have non-ASCII characters.
This is only a problem when you are accessing the ‘value’ via Javascript on the browser. It obviously pulls up garbage. So I only need to worry about fields that are being accessed via Javascript. But that’s still quite a few.
Subject: RE: Selection List with non-ASCII Character
Since this is new behaviour for Domino (I’ve only been made aware of it in postings over the past couple of weeks and it wasn’t there when I was doing multilingual work in R5 or D6), I’d suggest that the problem browser (if that is indeed the case) is probably newer and in current use.
Subject: RE: Selection List with non-ASCII Character
Yes - it would seem to be new behavior - I would have thought I would have seen this problem before if it wasn’t. But I have not upgraded the server in well over a year - it’s still at 7.0.1.
My guess is the problem has been around for quite some time, just never noticed it. It is only an issue if there is no Alias defined. And then - it only is an issue if I access the “value” with JavaScript. And finally - do something with it that would cause an error because of the invalid value. And of course - that error would have to be enough that the user would actually report it.
A lot of conditions - so this behavior may have been around for awhile.