Bug 48739 - fix order of slicing and umlaut transformation in user creation templates
fix order of slicing and umlaut transformation in user creation templates
Status: NEW
Product: UCS
Classification: Unclassified
Component: UDM (Generic)
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
http://forge.univention.org/bugzilla/...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-02-22 13:09 CET by Daniel Tröder
Modified: 2019-02-22 13:09 CET (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.023
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Tröder univentionstaff 2019-02-22 13:09:06 CET
When a template is used to shorten a string and transform the umlauts, the behavior can be surprising.

Example from Bug #48696:

"<firstname>[0:5].<lastname>[0:5]<:umlauts,lower>"

This should generate something like this:

Elisabeth Schäfer -> elisa.schae (5 characters)

But in fact it generates this:

Elisabeth Schäfer -> elisa.schaef (6 characters)

The reason is, that UDM first slices and the makes the umlaut transformation. But that expands the "ä" to "ae".

Modify UDM to apply length changing operations (like ":umlauts") before slicing.

Alternatively change this to a documentation bug and give a hint in the manual including the example solution: "<firstname:umlauts>[0:5].<lastname:umlauts>[0:5]<:lower>".