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

List:       kde-i18n-doc
Subject:    Re: Web Translation tool
From:       Karl Ove Hufthammer <karl () huftis ! org>
Date:       2024-04-10 18:24:23
Message-ID: 45f19f40-8ae1-434c-88b2-3b78781498ab () huftis ! org
[Download RAW message or body]

Yaron Shahrabani skreiv 05.04.2024 22:15:
> Great, that makes a lot of sense, thank you!
> Now I have 2 other problems:
> 1. I don't know how to combine KF5 with KF6 in the same project.

As Łukasz Wojniłowicz mentioned, you can use the branch translation 
feature in Lokalize. But a IMHO simpler solution is to instead switch to 
using the PO Summit workflow: 
https://techbase.kde.org/Localization/Workflows/PO_Summit

Then you will have only a single file to translate (for each 
application/library), instead of one file for each branch (currently up 
to four branches: trunk6, trunk5, stable6 and stable5). And you don't 
have to worry or care about a PO file being renamed in one branch, but 
not the other (which breaks Lokalize's branch sync feature), a PO file 
being split into several PO files (in one branch but not the other), or 
multiple PO files being merged into a single PO file (in one branch but 
not the other). All this is automatically handled for you by some nice 
people. :)


-- 
Karl Ove Hufthammer

[Attachment #3 (text/html)]

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">Yaron Shahrabani skreiv 05.04.2024
      22:15:<br>
    </div>
    <blockquote type="cite"
cite="mid:CACVjhxUYUOfiSx9-c=z5+bKNfg0wv_iMwZggOQzSe6AiEQmAFg@mail.gmail.com">
      <div class="gmail_default" style="font-family:tahoma,sans-serif">Great,
        that makes a lot of sense, thank you!</div>
      <div class="gmail_default" style="font-family:tahoma,sans-serif">Now
        I have 2 other problems:</div>
      <div class="gmail_default" style="font-family:tahoma,sans-serif">1.
        I don't know how to combine KF5 with KF6 in the same project.</div>
    </blockquote>
    <p>As Łukasz Wojniłowicz mentioned, you can use the branch
      translation feature in Lokalize. But a IMHO simpler solution is to
      instead switch to using the PO Summit workflow:
      <a class="moz-txt-link-freetext" \
href="https://techbase.kde.org/Localization/Workflows/PO_Summit">https://techbase.kde.org/Localization/Workflows/PO_Summit</a></p>
  <p>Then you will have only a single file to translate (for each
      application/library), instead of one file for each branch
      (currently up to four branches: trunk6, trunk5, stable6 and
      stable5). And you don't have to worry or care about a PO file
      being renamed in one branch, but not the other (which breaks
      Lokalize's branch sync feature), a PO file being split into
      several PO files (in one branch but not the other), or multiple PO
      files being merged into a single PO file (in one branch but not
      the other). All this is automatically handled for you by some nice
      people. :)<br>
    </p>
    <p><br>
    </p>
    <pre class="moz-signature" cols="72">-- 
Karl Ove Hufthammer</pre>
  </body>
</html>



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

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