Ian, You’re my hero! I never thought of the cli as a way to do this …
Thanks everyone! Leo Am 16. Nov. 2018, 18:19 +0100 schrieb Ian Y. Choi <[email protected]>: > Hello, > > Not pretty sure since I have never tried, but I think the following way would > work if you don't want to keep track of history on source string changes: > > - 1. Download both pot and po files > (or download po files, and generate pot files from po files - e.g., > https://stackoverflow.com/questions/5938869/how-to-generate-a-new-pot-template-from-a-translated-po-file > ) > - 2. Change both of source strings in pot and po files > - 3. Upload a changed pot files to update source strings in Zanata > - 4. Upload a changed po files to reflect translated strings with different > source strings in Zanata > > Source & translation document upload should be fine. > Please see http://docs.zanata.org/en/release/client/commands/push/ for more > details. > > > With many thanks, > > /Ian > > [email protected] wrote on 11/17/2018 1:49 AM: > > Hey, thanks for your responses. > > > > That’s what my script originally meant to do: Match the translations and > > generate a po from them. But as good as the plan was the bad it worked: I > > don’t know if I’m blind or not, but I couldn’t find any way to upload po's > > containing translations to zanata, only pot's > > > > Leo > > > > /// > > > > Leonhard Kreißig > > > > Bergstr. 6 > > 45219 Essen > > > > Tel.: (02054) 87 55 407 > > Mobil: 0151 62 90 29 89 > > Am 16. Nov. 2018, 17:00 +0100 schrieb Bryan Kearney <[email protected]>: > > > If you have scripts to fix the pot and po files, then do the needful on > > > your machine and then push the source and trnaslations back to the server: > > > > > > zanata push --push-type both > > > > > > -- bk > > > > > > On 11/16/18 9:59 AM, [email protected] wrote: > > > > Anyone? > > > > > > > > Leo > > > > Am 14. Nov. 2018, 16:19 +0100 schrieb Leonhard Kreissig > > > > <[email protected]>: > > > > > Heyho, > > > > > > > > > > I’m currently maintaining a project that contains many faulty base > > > > > strings (in English). > > > > > I’ve set up a new translation to English where native speakers > > > > > corrected the strings. > > > > > > > > > > Now I want to swap the strings so in case my i18n tools fail there are > > > > > correct strings and so ‚real‘ translators for other languages have a > > > > > good base to work upon. > > > > > > > > > > My project uses gettext, so .po/.pot format. > > > > > > > > > > I’ve written a script that moves the corrected msgstr’s to the msgid > > > > > field and the faulty msgid’s to previous_msgid. I hoped Zapata would > > > > > recognize that and keep all the translations (The translators would be > > > > > really really angry if they had to start from the beginning). > > > > > > > > > > Does anyone have an idea to swap the base strings and keep the > > > > > translations? > > > > > > > > > > My script is capable of inserting the new base strings in already > > > > > translated po-files, but I can’t upload them to Zapata anyways. > > > > > > > > > > Leo > > > > > > > > _______________________________________________ > > > > zanata-users mailing list > > > > [email protected] > > > > https://www.redhat.com/mailman/listinfo/zanata-users > > > > > > > > > > > > > > _______________________________________________ > > zanata-users mailing list > > [email protected] > > https://www.redhat.com/mailman/listinfo/zanata-users >
_______________________________________________ zanata-users mailing list [email protected] https://www.redhat.com/mailman/listinfo/zanata-users
