Paul, Yes and I also confirmed the prior commit which enables the no-wrap option in "update_po_files.sh". Thanks a lot!
Phroneris 2021年6月13日(日) 9:41 Paul Licameli <[email protected]>: > Phroneris, I have updated audacity.pot and ja.po with un-wrapped lines at > commit 7d76e06d84499c4c26647aa7ea515a5a57d8ad4b. Otherwise content is > unchanged. > > PRL > > > On Sat, Jun 12, 2021 at 1:22 AM 森の子リスのミーコの大冒険 <[email protected]> wrote: > >> Thanks Paul, >> >> >>> So you would really prefer the long English strings always in >>> audacity.pot? And in the updated Japanese strings in ja.po that we make >>> before you fill in the blanks? >> >> >> Yes. >> Disabling those line breaks can reduce needless diff on Git and too >> complex regexp >> such as */日(("\n")?本語|本"\n"語|本語"\n").+"/* for */日本語.+"/* on Notepad++. >> >> Phroneris, what you ask can be done easily by modifying >>> locale/update_po_files.sh to use the --no-wrap option in msgmerge and >>> xgettext. >> >> >> Super! >> >> Regards, >> Phroneris >> >> >> 2021年6月12日(土) 7:44 Paul Licameli <[email protected]>: >> >>> Phroneris, what you ask can be done easily by modifying >>> locale/update_po_files.sh to use the --no-wrap option in msgmerge and >>> xgettext. >>> >>> Would anyone object to this change? >>> >>> Long strings would no longer have line breaks when the file is viewed as >>> simple text. >>> >>> PRL >>> >>> >>> On Fri, Jun 11, 2021 at 4:01 PM Paul Licameli <[email protected]> >>> wrote: >>> >>>> That’s an interesting suggestion. So you would really prefer the long >>>> English strings always in audacity.pot? And in the updated Japanese >>>> strings in ja.po that we make before you fill in the blanks? >>>> >>>> Technically it’s about the options passed to xgettext and msgmerge that >>>> the update script uses. Maybe the right options exist. I’ll research. >>>> >>>> PRL >>>> >>>> >>>> On Friday, June 11, 2021, 森の子リスのミーコの大冒険 <[email protected]> wrote: >>>> >>>>> 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 >>> >> _______________________________________________ >> 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 >
_______________________________________________ Audacity-translation mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/audacity-translation
