[Trennmuster] Review hyphenation pattern definitions

[Werner LEMBERG]

[Ich muß das separat an die Liste schicken, denn der Listserver
 verweigert die Annahme der ursprünglichen E-Mail wegen zu vielen
 Leuten in der CC-Liste.]

From: Sander van Geloven <sander.vangeloven at opentaal.org>

> On 01/13/2014 08:35 AM, R.Baars wrote:
>
>> I would like to add something to this text:
>> 
>>     This leads to an interesting question, namely how uppercase and
>>     lowercase influence hyphenation, and how uppercase and
>>     lowercase should be represented in the word list.  This is not
>>     discussed at all.
>> 
>> Case is actually not considered at all in current technology.  For
>> Dutch, any word can get a capital at the start when at the start of
>> a sentece, but when it has a capital in the middle of a sentence,
>> it might be a proper name.  Proper names don't follow normal
>> hyphenation rules, since most of them are international.
>> 
>> Do we need something in the specification to denote
>> 'case-specificicity' ?
> 
> The standard as is now says that if none is provided, hyphenation is
> undefined.  In case for a word with upper case letters, we could add
> the rule that it uses what is specified for lower case letters.
> 
> In this way we can override that, for example my name, which is also
> a verb in Dutch, is not hyphenated when it has upper case.
> 
> geloven;ge~lo~ven # verb
> Geloven;Geloven # surname
> 
> However, a sentence like [lit:] "Believe we all can." "Geloven
> kunnen we allemaal." would for that case not hyphenate on Geloven if
> needed.
> 
> Is this what we want?

I don't think so.  Instead, I would rather state in your document that
case issues are not yet discussed, and that the current pragmatic
solution is to lowercase everything.  However, this is problematic in
some cases, at least in German, since there are words like `MASSE'
that have two lowercase forms with different hyphenation (`Ma-ße' and
`Mas-se').


    Werner