Bug 41091 - Improve description of steps to undertake for updating translation packages
Improve description of steps to undertake for updating translation packages
Status: RESOLVED DUPLICATE of bug 41912
Product: UCS extended documentation
Classification: Unclassified
Component: Developer documentation
unspecified
Other Linux
: P5 normal (vote)
: ---
Assigned To: Bugzilla Mailingliste
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-04-21 13:24 CEST by Alexander Kläser
Modified: 2016-08-04 12:47 CEST (History)
0 users

See Also:
What kind of report is it?: ---
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): External feedback, Internationalization
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kläser univentionstaff 2016-04-21 13:24:02 CEST
From Ticket#2016031421000382 I conclude that the description in the manual of how to update a translation package (11.1.4.) could be improved. I would suggest a clear step-by-step description, somehow the current nesting seems a bit confusing to me. Also the use of "update" and "source files" is somewhat misleading (at least if I understand it correctly).

This could then look like, e.g.:

--------- 8< ----------
(1) Update translation source files:
  cd ...
  svn up

(2) Update files in translation package, if changes occur in the UCS source packages that need a change of the translation files:
  cd ...
  univention-ucs-translation-update-source-files.py ...

(3) Adjust translations of the package manually.

(4) Compile translation files. This step is necessary each time before building the translation .deb package.
  cd ...
  univention-ucs-translation-update-target-files.py ...
--------- 8< ----------
Comment 1 Alexander Kläser univentionstaff 2016-08-04 12:47:08 CEST
Marked as RESOLVED as the description needs to be updated anyway (cf. Bug 41912).

*** This bug has been marked as a duplicate of bug 41912 ***