[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Web Translation tool
From:       Yaron Shahrabani <sh.yaron () gmail ! com>
Date:       2024-03-27 7:21:36
Message-ID: CACVjhxX6BQ7NuE2UpPPnM_bvFDNUmVhoTtU840U5-+pyis37SQ () mail ! gmail ! com
[Download RAW message or body]

Keep up the good work and thank you for another great project!
I'll try to help you dockerize the build and the product so it'll be easier
to develop and deploy, thank you!
Yaron Shahrabani

<DevOps - Hebrew translator>



On Wed, Mar 27, 2024 at 1:12 AM Albert Astals Cid <aacid@kde.org> wrote:

> El dijous, 21 de març de 2024, a les 0:49:17 (CET), Carl Schwan va
> escriure:
> > 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.
>
> How would that work when we rename files (doesn't happen a lot, but it
> does
> happen from time to time).
>
> >
> > 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,
>
> summit is an unofficial way of doing translations, do you plan to support
> the
> regular way? Or do you think we should all move to summit?
>
> > 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
>
> Looks good :)
>
> How easy would it be to deploy in a very limited manner so that interested
> folks can have a look at the thing in a live scennario?
>
> >
> > 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.
>
> As others have mentioned maintainability is a potential concern, how big
> is
> the codebase? How easy do you think it'd be to hack on for a total newbie?
>
> I'm guessing having access to the Translation Memory (i.e. how the word
> has
> been translated in other instances) wouldn't hurt.
>
> Cheers,
>   Albert
>
> >
> > Cheers,
> > Carl
>
>
>
>
>

[Attachment #3 (text/html)]

<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">Keep up the good work and \
thank you for another great project!</div><div class="gmail_default" \
style="font-family:tahoma,sans-serif">I&#39;ll try to help you dockerize the build and the product so \
it&#39;ll be easier to develop and deploy, thank you!<br clear="all"></div><div><div dir="ltr" \
class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div \
dir="ltr"><span style="font-size:large"><span style="font-family:georgia,serif"><font \
color="#990000">Yaron</font></span><font color="#330000"><span style="font-family:georgia,serif"> <font \
size="4"><span style="font-family:times new \
roman,serif">Shahrabani</span></font></span></font></span><blockquote style="margin:0 0 0 \
40px;border:none;padding:0px"><div><font color="#666666"><span style="font-size:x-small"><font \
color="#FF0000">&lt;</font></span><font size="2"><span style="font-family:monospace">DevOps</span> - \
<span style="font-family:garamond,serif">Hebrew translator</span></font><span \
style="font-size:x-small"><font \
color="#FF0000">&gt;</font></span></font></div></blockquote></div></div></div></div></div></div></div><br></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Mar 27, 2024 at 1:12 AM Albert Astals Cid \
&lt;<a href="mailto:aacid@kde.org">aacid@kde.org</a>&gt; wrote:<br></div><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">El dijous, 21 de \
març de 2024, a les 0:49:17 (CET), Carl Schwan va escriure:<br> &gt; Hello everyone,<br>
&gt; <br>
&gt; A few days ago, I suddenly got the motivation to look into building a small<br>
&gt; web tool for our translation designed in a way that it can coexist with the<br>
&gt; current workflow. It was also an excuse to learn a bit of Rust 🦀 and to<br>
&gt; refresh my knowledge on VueJs :)<br>
&gt; <br>
&gt; The idea is to have a simple website allowing people to login with their<br>
&gt; gitlab account and then let them edit the po files with a web ui. For KDE<br>
&gt; developers/translators, it would allow to either publish their changes<br>
&gt; immediately to SVN or save their changes inside the database to allow<br>
&gt; someone else to review them. For non kde developers, only after a review<br>
&gt; would the change be allowed to be merged in SVN.<br>
<br>
How would that work when we rename files (doesn&#39;t happen a lot, but it does <br>
happen from time to time). <br>
<br>
&gt; <br>
&gt; Here is the repository: <a href="https://invent.kde.org/carlschwan/webl10n/" rel="noreferrer" \
target="_blank">https://invent.kde.org/carlschwan/webl10n/</a><br> &gt; <br>
&gt; Currently this is still very much in progress but I can already login with<br>
&gt; gitlab, load all po files in the summit directory in SVN,<br>
<br>
summit is an unofficial way of doing translations, do you plan to support the <br>
regular way? Or do you think we should all move to summit?<br>
<br>
&gt; submit changes to<br>
&gt; the db, and then display the changes in a &#39;review&#39; interface and I&#39;m<br>
&gt; progressing quite fast. To give you a better idea, how the current progress<br>
&gt; I alsoed uploaded a bunch of screenshots to my website:<br>
&gt; <br>
&gt; <a href="https://carlschwan.eu/assets/webl10n/home.png" rel="noreferrer" \
target="_blank">https://carlschwan.eu/assets/webl10n/home.png</a><br> &gt; <a \
href="https://carlschwan.eu/assets/webl10n/components.png" rel="noreferrer" \
target="_blank">https://carlschwan.eu/assets/webl10n/components.png</a><br> &gt; <a \
href="https://carlschwan.eu/assets/webl10n/files.png" rel="noreferrer" \
target="_blank">https://carlschwan.eu/assets/webl10n/files.png</a><br> &gt; <a \
href="https://carlschwan.eu/assets/webl10n/editor.png" rel="noreferrer" \
target="_blank">https://carlschwan.eu/assets/webl10n/editor.png</a><br> &gt; <a \
href="https://carlschwan.eu/assets/webl10n/editor-confirmation.png" rel="noreferrer" \
target="_blank">https://carlschwan.eu/assets/webl10n/editor-confirmation.png</a><br> &gt; <a \
href="https://carlschwan.eu/assets/webl10n/review.png" rel="noreferrer" \
target="_blank">https://carlschwan.eu/assets/webl10n/review.png</a><br> <br>
Looks good :)<br>
<br>
How easy would it be to deploy in a very limited manner so that interested <br>
folks can have a look at the thing in a live scennario?<br>
<br>
&gt; <br>
&gt; Before I invest more time on it, it would be good to have some feedback on<br>
&gt; the idea and if there is someone among you who is familiar with Rust or<br>
&gt; VueJs, help is also welcome.<br>
<br>
As others have mentioned maintainability is a potential concern, how big is <br>
the codebase? How easy do you think it&#39;d be to hack on for a total newbie?<br>
<br>
I&#39;m guessing having access to the Translation Memory (i.e. how the word has <br>
been translated in other instances) wouldn&#39;t hurt.<br>
<br>
Cheers,<br>
   Albert<br>
<br>
&gt; <br>
&gt; Cheers,<br>
&gt; Carl<br>
<br>
<br>
<br>
<br>
</blockquote></div>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic