Bug #9532
codepage support in ASC(), CHR(), OUTPUT TO ... CONVERT and FIX-CODEPAGE()
0%
Related issues
History
#1 Updated by Greg Shah over 1 year ago
Codepages (UTF-8, ISO8859-1, IBM850) need to be tested/fixed in ASC(), CHR(), OUTPUT TO ... CONVERT and FIX-CODEPAGE().
#2 Updated by Constantin Asofiei about 1 year ago
Hi Delia, what is the state of #4766? Can you do some preliminary tests with the codepages mentioned by Greg?
#3 Updated by Delia Mitric about 1 year ago
Constantin Asofiei wrote:
Hi Delia, what is the state of #4766? Can you do some preliminary tests with the codepages mentioned by Greg?
Hello, #4766 is not ready. There are cases for certain codepages that make an exception from the rule that need to be treated. As Greg proposed, I was working on some files that mapped conversion between compatible codepages when I discovered problems with UTF-16xx/UTF-32xx.
Also, cases like CHR(7829367., "UTF-8", "UTF-8") where 7829367 = ASC ("www", "UTF-8", "UTF-8") aren't yet covered. I was focusing on making the rule correct for all combinations of codepages for ONE character, not a string.
If it is necessary, I can focus just on the mentioned codepages above.
#4 Updated by Constantin Asofiei about 1 year ago
Delia, please restart working on this.
#6 Updated by Constantin Asofiei 12 months ago
Delia Mitric wrote:
Constantin Asofiei wrote:
Delia, please restart working on this.
Should I focus on the three codepages written in #9532-1?
Yes.
#7 Updated by Constantin Asofiei 12 months ago
- Related to Bug #4766: fix CHR and ASC added
#8 Updated by Constantin Asofiei 12 months ago
- Related to Support #9445: compatibility test FIX-CODEPAGE added