Bug 54394 - Add script to add french translation to extended attributes, portal entries (LDAP contents)
Add script to add french translation to extended attributes, portal entries (...
Status: NEW
Product: UCS
Classification: Unclassified
Component: General
UCS 5.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2022-01-28 15:54 CET by Florian Best
Modified: 2022-02-04 12:52 CET (History)
2 users (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Internationalization
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2022-01-28 15:54:16 CET
The french extended attributes and portal entry descriptions are currently translated in the package joinscripts.

We should remove those translations from the joinscripts and add a script which extracts all to be translated strings from joinscripts and puts them e.g. into a .po file and ship it (the .mo file) via the univention-l10n-fr package.

A joinscript of univention-l10n-fr should then modify all existing extended attributes/portal entries/etc and update the corresponding french translation by looking it up in the .mo file.

A similar mechanism once existed for UCR variables (ucr-l10n and ucr-l10n-generate-po in packaging/univention-l10n).
Comment 1 Philipp Hahn univentionstaff 2022-02-04 11:20:46 CET
Alternative idea from <https://git.knut.univention.de/univention/internal/hackathon/orga/-/issues/16>:

Define a declarative style to create EAs and Portal entries instead of having bash code creating those entries.
+ allows use to improve script to translate declaration into code
+ simplifies extraction of translation strings
Comment 2 Florian Best univentionstaff 2022-02-04 12:52:25 CET
A theoretical problem I see are dynamic texts, e.g.:

management/univention-self-service/34univention-self-service.inst
--append link='"en_US" "'"https://${hostname}.${domainname}/univention/self-service/?header=try-hide#page=passwordchange"'"' \

Collecting data from the system would cause the UCR expanded values to be inserted.

We also can't differentiate where the data comes from: UCS package, UCS@school package, UCS app, etc?
And we would need to install all components to collect all data.

Maybe we have to wait for a declarative solution as mentioned in comment 1.
Or we start with a bash parser of joinscripts which cover the basic cases?