Worttrennung can contain multiple values separated by comma about duden HOT 3 OPEN

I'm not so good at designing good APIs. However, your suggestion to leave the current field as is with the first option and then another another option with all options sounds good to me.

from duden.

There is "Zivildienstleistender" and "Zivildienst Leistender". Each has one word separation.

from duden.

@tbm Thank you for reporting this!

I didn't know that this problem existed. It is indeed not great.

As for how to handle this:

• my first thought was to return list of lists of word parts in case several words/variants are detected
• but it is not ideal to have a different type return based on contents.

So my idea is:

1. Return only word separation of first option, i.e. ['Zi', 'vil', 'dienst', 'leis', 'ten', 'der']
2. Add another property, e.g. .word_separation_variants which would return all options split.

This way, a kind of backward compatibility would be preserved, but also different variants could be read.

I see that the .name property is handled fine

In [3]: w.name
Out[3]: 'Zivildienstleistender'

but the other variant "Zi­vil­dienst Leis­ten­der" cannot be read. Maybe this can be another property e.g. .name_variants

This sounds like it would not be hard to implement.

from duden.