<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<pre class="moz-quote-pre" wrap="">Hi all,
I am fully in line with Łukasz's proposition for creating a dedicated branch for the website translations, in addition to documentation and application translation branches.
Therefore, I have no idea about the feasibility, impacts and modifications to do so.
For me, the translation process/terminology/wording are a bit different between applications and documentation, justifying (for years) two separate translation branches.
For website translations, I am translating within the FR team,KDE announcements and many others websites. The translation work is a bit different to doc and apps (more HTML, links, ref, ...). Workload is greater, reactivity to changes depending on team size, requiring dedicated skills (ex: Krita or Kdenlive). Good proposition to separate websites translations for me, without mixing apps and websites.
Just to understand the naming in the new branch, Łukasz, is this what you are proposing?
</pre>
<ul>
<li> <span style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;">messages/documentation-docs-kdenlive-org/
==> messages/websites/</span></span><span
style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;"></span><span
style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;">kdenlive-org</span></span></span></li>
<li><span style="font-family:monospace"><span
style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;">messages/websites-kde-org
</span></span></span><span style="font-family:monospace"><span
style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;"><span
style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;">==>
messages/websites/kde</span></span><span
style="font-family:monospace"><span
style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;">-org
(with files frameworks_announcements.po
menu_shared.po promo.po release_announcements.po
www_www.po)</span></span></span></span></span></span></li>
</ul>
<p>Hope it helps.<br>
</p>
<p>Cheers. Xavier</p>
<pre class="moz-quote-pre" wrap="">
</pre>
<div class="moz-cite-prefix">Le 28/11/2021 à 10:40, Łukasz
Wojniłowicz a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:20211128104058.5937a3cf@luklap.workgroup">
<pre class="moz-quote-pre" wrap="">Hi all,
at <a class="moz-txt-link-freetext" href="https://l10n.kde.org/">https://l10n.kde.org/</a> under "Statistics" label the translations are
divided into following areas:
1) Applications
2) Documentation
but since a while a trend started to set in that big chunks of
documentation go into the "Applications" area like with the recent
"documentation-docs-kdenlive-org".
I may have no capacity to translate that, but it will appear constantly
as untranslated in the area of Applications (onto which I put the most
priority), and clutters the view more and more.
I suggest:
1) moving the documentation prefixed chunks out of the "Applications"
area into the "Documentation" area.
2) creating a new "Websites" area and moving the websites prefixed
chunks out of "Applications" area into the "Websites" area.
Those three areas are so big on themselves and distinct from each other
that they deserve to be kept in separate spaces.
That way you don't have to use prefixes like "documentation" or
"websites" to mark non-application chunks in the "Applications" area.
Thanks.
Cheers,
Łukasz
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Xavier Besnard
Place de la halle
82330 Varen
Tél: 06 49 37 44 17
Courriel: <a class="moz-txt-link-abbreviated" href="mailto:xavier.besnard@neuf.fr">xavier.besnard@neuf.fr</a></pre>
</body>
</html>