Differences in handling german Umlaute of Runrev

Ken Ray kray at sonsothunder.com
Tue Jul 10 10:36:13 CDT 2007


On Mon, 9 Jul 2007 13:35:23 +0200, Tiemo Hollmann TB wrote:

> There are so many differences, that I don't want to describe them all here.
> I created a test stack to show the differences and put it under my name
> "Tiemo" on revonline. So if anyone is interested and wants to give me a
> feedback of your experiences, you can upload the sample stack. Because it is
> a bug concerning the character set, I don't know the behaviour on English
> systems.

OK, here's my test results (in all cases Rev 2.8.1-gm-2, "f2" means 
what showed up in the "field2" field, "r" means what showed up in the 
"result" field, 'a' means "lowercase a with umlaut" and 'A' means 
"capital a with umlaut" - same for O and U):

Mac OS X 10.4.9
	a-umlaut (using "=", data in field)  --> f2 shows 'a', r shows 'a'
	o-umlaut (using "=", data in field)  -->  f2 shows 'o', r shows 'o'
	u-umlaut (using "=", data in field)  --> f2 shows 'u', r is empty
	a-umlaut (using offset, data in field)  --> f2 shows 'a', r shows 'a'*
	o-umlaut (using offset, data in field)  --> f2 shows 'o', r shows 'o'*
	u-umlaut (using offset, data in field)  --> f2 shows 'u', r shows 'u'*

	a-umlaut (using "=", data in prop)  --> f2 shows 'a', r shows 'a'
	o-umlaut (using "=", data in prop)  -->  f2 shows 'o', r shows 'o'
	u-umlaut (using "=", data in prop)  --> f2 shows 'u', r is empty
	a-umlaut (using offset, data in prop)  --> f2 shows 'a', r shows 'a'*
	o-umlaut (using offset, data in prop)  --> f2 shows 'o', r shows 'o'*
	u-umlaut (using offset, data in prop)  --> f2 shows 'u', r shows 'u'*

Win Vista Home Premium
	a-umlaut (using "=", data in field)  --> f2 shows 'a', r shows 'a' AND 
'A'
	o-umlaut (using "=", data in field)  --> f2 shows 'o', r shows 'o'
	u-umlaut (using "=", data in field)  --> f2 shows 'u', r is empty
	a-umlaut (using offset, data in field)  --> f2 shows 'a', r shows 'a' 
AND 'A'*
	o-umlaut (using offset, data in field)  --> f2 shows 'o', r shows 'o' 
AND 'O'*
	u-umlaut (using offset, data in field)  --> f2 shows 'u', r shows 'u' 
AND 'U'*

	a-umlaut (using "=", data in prop)  --> f2 shows 'a', r shows 'a' AND 
'A'
	o-umlaut (using "=", data in prop)  --> f2 shows 'o', r shows 'o'
	u-umlaut (using "=", data in prop)  --> f2 shows 'u', r is empty
	a-umlaut (using offset, data in prop)  --> f2 shows 'a', r shows 'a' 
AND 'A'*
	o-umlaut (using offset, data in prop)  --> f2 shows 'o', r shows 'o' 
AND 'O'*
	u-umlaut (using offset, data in prop)  --> f2 shows 'u', r shows 'u' 
AND 'U'*


* When running this test, the contents of the field "field1" was being 
manipulated and ended up getting blank lines where some of the 
comparisons took place - I don't know if this is what you expected or 
not.


Hope this helps you track stuff down,

Ken Ray
Sons of Thunder Software, Inc.
Email: kray at sonsothunder.com
Web Site: http://www.sonsothunder.com/



More information about the use-livecode mailing list