On Tue, Dec 7, 2021 at 9:38 AM Brad <[email protected]> wrote: > Thank you again Paul for your response. That’s good to know. > > You mentions several “checks” you did on the translation file. > Those checks uncovered a few errors as you mentioned. > > I’d be very interested in knowing more about that workflow and checks you > do > For example > 1-what compiler did you use? > 2-Is there any program I can download and run on my po files to find some > errors prior to submitting? > 3- when you mentioned “stricter checker” which program was that? >
msgfmt is the program in the GNU getttext suite that "compiles" vi.po into a .mo file as part of the build process. The .mo files for the several locales are shipped with Audacity. For instance, on macOS, you can right-click the program icon in Finder, then "Show Package Contents", then under Contents/Resources/vi.lproj you find audacity.mo. This compacted file form isn't legible in a browser but is read into the program at runtime. Our build process wasn't yet using the --check-format option of msgfmt, which can do more checks of consistency of formats and cause the build to fail. That was a surprising omission, which I changed for the next release. Here is a link for msgfmt details, into the big single-page documentation of all of the gettext programs. https://www.gnu.org/software/gettext/manual/gettext.html#msgfmt-Invocation I also wrote a little script at locale/diagnostics.sh in Audacity's source code tree, which prints a summary of the state of completeness of the many .poi files. That uses the msgcmp program, to compare each .po file to audacity.pot, then filter the output in certain ways. > > I’m interested and glad to “jump through said hoops” with the files I’m > working with. > > After all, not only audacity , but I’m working on several other projects > as well and plan on being a contributor for life to this and as many open > source projects as possible. > > (I’m sorta retired in my 30s and so spend a lot of my time working on > interesting projects like this) > > Any suggestions or links or any extra steps you can help me with would be > greatly appreciated. > > I will implement those with this project and any on the future. > > After all, ideally this would save you some hassle on your end. > > > I hope you’re having a great week Paul! > Thank you, Brad. Paul Licameli > > Cheers! > -brad > > > > > > On Tue, Dec 7, 2021 at 9:50 AM Paul Licameli <[email protected]> > wrote: > >> About the mixed Vietnamese and English -- I leave it to your judgment if >> that is best for the culture. I don't expect the lengths of the names to >> be problematic. >> >> Paul >> >> >> On Mon, Dec 6, 2021 at 6:23 AM Brad <[email protected]> wrote: >> >>> Thank you so much for reply. >>> Mostly I really appreciate this level of detail. I follow everything >>> you said and you explained it very well. >>> Me being a programmer since the 90’s makes me keenly aware of formatting >>> difficulties. >>> & # % are common culprits. >>> >>> Me only being on “this side of the fence” I can only see translations >>> not the programming side. >>> >>> I and the rest of us translators will give your tips our due attention. >>> >>> I will also do my best to have “before and after” examples for >>> me/us/anyone to see how to avoid formatting problems. Maybe something to >>> add to a “style guide”. >>> >>> Either way. Thank you again for your answers. >>> Yes I and all of us look forward to any other answers you can help us >>> with. >>> At your convenience of course. >>> >>> Cheers! >>> -brad >>> >>> >>> >>> On Fri, Dec 3, 2021 at 2:18 AM Paul Licameli <[email protected]> >>> wrote: >>> >>>> Brad, thank you and your team for this effort! >>>> >>>> I need to make some corrections to vi.po. Please review here: >>>> https://github.com/audacity/audacity/pull/2220/files >>>> >>>> You probably know about c-format strings using % directives, but there >>>> are also some lisp-format strings using ~ directives. When I tried to >>>> build using stricter checking of formats in the msgfmt program, I got >>>> several errors in vi.po that I tried to fix. >>>> >>>> Where the sequence *~\n* occurs, this should be preserved exactly in >>>> the translation -- but some strings had a space just after ~ which caused >>>> an error. >>>> >>>> Also, *~% *is a frequent sequence that formats as a newline, but in a >>>> few cases, I saw the English letter immediately after the % preserved in >>>> the translation, as if it were part of a c-formatting directive -- I assume >>>> that's a mistake, and I just deleted the extra letter, which would have >>>> appeared at the beginning of the next line of Vietnamese. >>>> >>>> I will answer your other questions about the effect menu later. >>>> >>>> Paul Licameli >>>> >>>> _______________________________________________ >>>> 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
