Hi,
I use PoEdit for ordinary translations and searches.
I also use Notepad++ to look into raw text of po files and search/replace
complicated things with regular expressions.
And I manage my work ("ja.po" and some personal l10n notes) with Git:
https://github.com/Phroneris/audacity
On this occasion, let me request: No internal string wrap!
Inside po files as plain text, very long lines in each entry are split into
more lines automatically.
PoEdit does this by default when saving. I guess the software used in
"update_po_files.sh" does the same.
TBH this auto-wrap is not just needless but rather obstructive to both
regex searches and Git uses,
so the first thing I do after obtaining updated "ja.po" is revoke it
<https://github.com/Phroneris/audacity/commit/0d85e2048892c1a35a154105babe42180f0f5dfc>
by
re-saving through my PoEdit,
whose "Wrap at:" and "Preserve formatting of existing files" options I
turned off from preferences.
Therefore, things to me get convenient if po files are generated *without*
auto-wrap when doing "update .pot and .po".
Unless it's necessary for some technical reasons...
Regards,
Phroneris
2021年6月11日(金) 0:16 Paul Licameli <[email protected]>:
> Dear translators,
>
> It is my responsibility again to merge your contributions into Audacity's
> GitHub repository. It has been over three years since I last did this.
>
> I know how to regenerate the .pot and .po files, and take your updates,
> check their completeness, and merge them.
>
> But I am not familiar with the actual process of editing the .po files
> that you do or the special programs that do it.
>
> Which ones do you prefer?
>
> I know of (but an not familiar with) Poedit and Linguist. And of course
> simply using a text editor can work. There is an emacs mode too.
>
> If there is any way I might prepare the .pot and .po files to be more
> convenient for your use, let me know.
>
> In recent versions of Audacity we have begun more use of disambiguating
> contexts, so that one English string might translate in multiple ways. Let
> me know if there are more examples where we should do that, as Sampo
> Hippeläinen lately did for "Recording".
>
> PRL
>
>
> _______________________________________________
> Audacity-translation mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/audacity-translation
>
_______________________________________________
Audacity-translation mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/audacity-translation
