Re: [xsl] Will every XSLT processor reduce upper-case('ß') to SS ?

[Wolfgang Laun <wolfgang.laun@xxxxxxxxx>]

Since April 4, 2008 Unicode contains the character 'LATIN CAPITAL
LETTER SHARP S' (U+1E9E) due to an initiative of the German Standards
institute (DIN). Addition 4:2008 to the standard ISO/IEC 10646
appeared on June 23, 2008, which provides sort of an "international
blessing". The ultimate authority for German spelling is the "Rat f|r
deutsche Rechtschreibung", which hasn't endorsed this novelty yet;
thus the rule to replace "_" with "SS" is still valid officially.

It is absolutely wrong to replace '_' by a single 'S'.

Personal remark: Practical use typically precedes an official
amendment of a rule; hence it would be advisable to use U+1E9E today,
provided your font has a fitting glyph. Otherwise, you may have to
stick with the "SS" replacement. - It is downright ugly to see a
single '_' among all upper case lettering, therefore avoid it.

-W



On 05/01/2013, David Carlisle <davidc@xxxxxxxxx> wrote:
> On 05/01/2013 10:08, Costello, Roger L. wrote:
>> Hi Folks,
>>
>> Here is a common German surname:
>>
>>        Strau_
>>
>> I used SAXON to convert the surname to uppercase:
>>
>>      upper-case('Strau_')			returns STRAUSS
>>
>> Notice that _ was converted to SS.
>>
>
> Assuming the processor is using Unicode later than 3.2 all processors
> should use the same (unicode defined) tables. The Xpath upper-case
> function does not depend on the locale or (directly) the processor, just
> on the version of Unicode supported.
>
> the definition of upper-case notes:
>
>  > These functions may not always be linguistically appropriate ....
>
> see
>
> http://www.w3.org/TR/xpath-functions/#func-upper-case
>
> David
>
> --
> google plus: https:/profiles.google.com/d.p.carlisle