Web Translation tool

[Josep M. Ferrer]

El 21/3/24 a les 0:49, Carl Schwan ha escrit:
> Hello everyone,
>
> A few days ago, I suddenly got the motivation to look into building a small
> web tool for our translation designed in a way that it can coexist with the
> current workflow. It was also an excuse to learn a bit of Rust 🦀 and to refresh
> my knowledge on VueJs :)
>
> The idea is to have a simple website allowing people to login with their
> gitlab account and then let them edit the po files with a web ui. For KDE
> developers/translators, it would allow to either publish their changes
> immediately to SVN or save their changes inside the database to allow someone
> else to review them. For non kde developers, only after a review would the
> change be allowed to be merged in SVN.
>
> Here is the repository:https://invent.kde.org/carlschwan/webl10n/
>
> Currently this is still very much in progress but I can already login with
> gitlab, load all po files in the summit directory in SVN, submit changes to the
> db, and then display the changes in a 'review' interface and I'm progressing
> quite fast. To give you a better idea, how the current progress I alsoed
> uploaded a bunch of screenshots to my website:
>
> https://carlschwan.eu/assets/webl10n/home.png
> https://carlschwan.eu/assets/webl10n/components.png
> https://carlschwan.eu/assets/webl10n/files.png
> https://carlschwan.eu/assets/webl10n/editor.png
> https://carlschwan.eu/assets/webl10n/editor-confirmation.png
> https://carlschwan.eu/assets/webl10n/review.png
>
> Before I invest more time on it, it would be good to have some feedback on the
> idea and if there is someone among you who is familiar with Rust or VueJs,
> help is also welcome.
>
> Cheers,
> Carl
>
>
>
Sorry, I don't know Rust nor VueJs, so I can't help with programming 
tasks. But I can give you some feedback:

- In this stage, this tool only works with summit environment, but I 
estimate that only 50% or less of KDE translation teams work with 
summit. It can be possible to use the usual branches (stable/trunk) for 
non-summit teams?

- Editor and editor-confirmation should display metadata for translation 
units. Metadata includes translator comments (# ), source code (#:) and 
disambiguation context (msgctxt).  As a plus, it will be very useful 
that a click on the source code will open a new window with the source 
code (from invent.kde.org or similar). Translator comments (# ) should 
be an editable field. Metadata fields are a big help in translation 
workflow because they help to improve quality and consistency of 
translated messages.

- Note that in many languages there are some plural forms for each 
translation unit (plural forms depends on language). This requires a 
special handling.

- Note that there are tags (html, qt, sphinx, etc.) that must be present 
in the original and translated messages. Also, there are entities 
translating documentation. This requires a special handling.

- Editor and editor-confirmation should have a spellchecker for 
translations (as a plus, also for original message to find typos in 
original messages). This will help with spellchecking translated messages.

- Editor and editor-confirmation should have a Memory Translation to 
pick translations from, as Lokalize has currently. This helps 
translation teams to be consistent across all KDE translations.

On the other hand, I think this tool can be very useful for new 
translators and for established teams, because it hides the complexities 
of SVN to new translators at the beginning, but the established teams 
retain the control over translations, avoiding inconsistencies or 
undesirable changes.

Of course, I can help you testing this tool.

Thanks for your work.

Josep M. Ferrer

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-i18n-doc/attachments/20240322/4e0f65cd/attachment.htm>