| Message ID | cover.1672465269.git.gemmaro.dev@gmail.com |
|---|---|
| Headers | show |
| Series | gnu: po4a: Update to 0.68 | expand |
Pushed to master as 62ee1c4b47c6e1e62314223d62a5d54162a23fa8 - a1f9eba892784069e34338e01237a74b8a3bd8a2, thank you! I made some changes, but the series was really good overall! The main change is that I integrated your copyright to the first patch that modified the file. I've left updating the process to later. We'll want to do it though, the new interface looks really cool for our use-case, especially because it supports using a single pot for multiple files (think guix.texi and contributing.texi that currently raise a warning). I'm happy to help if you want to try, otherwise I'll probably do it sometime :) Le Sat, 31 Dec 2022 14:56:13 +0900, gemmaro <gemmaro.dev@gmail.com> a écrit : > Hello Guix, > > This patch updates po4a to 0.68. It also includes additional > dependencies required with the update. > > I have tried running "make as-derivation" with the following > suggestion. Then I observed warnings that po4a should be used > instead of po4a-translate. I don't think there were any other errors > related to po4a. > https://lists.gnu.org/archive/html/guix-patches/2021-07/msg00030.html > > Another side effect that comes to mind is that if the po4a parser has > changed, it is possible that some of the entries in the translations > will be fuzzy. > > I wrote this patch for my personal Markdown translation needs. And > it appears to be working well for this format. > > Regards, > gemmaro > > gemmaro (6): > gnu: Add perl-text-charwidth > gnu: Add perl-xs-parse-keyword > gnu: Add perl-text-wrapi18n > gnu: Add perl-syntax-keyword-try > gnu: po4a: Update to 0.68 > Update copyright > > gnu/packages/gettext.scm | 49 +++++++++++--------- > gnu/packages/perl.scm | 96 > ++++++++++++++++++++++++++++++++++++++++ 2 files changed, 125 > insertions(+), 20 deletions(-) > > > base-commit: 8e883dc8210d4a7c3f09961994685ed54942fd73
(Sorry, I had the wrong address and will resend.) Hello, Julien Lepiller <julien@lepiller.eu> writes: > Pushed to master as 62ee1c4b47c6e1e62314223d62a5d54162a23fa8 - > a1f9eba892784069e34338e01237a74b8a3bd8a2, thank you! > > I made some changes, but the series was really good overall! The main > change is that I integrated your copyright to the first patch that > modified the file. > > I've left updating the process to later. We'll want to do it though, > the new interface looks really cool for our use-case, especially > because it supports using a single pot for multiple files (think > guix.texi and contributing.texi that currently raise a warning). > > I'm happy to help if you want to try, otherwise I'll probably do it > sometime :) Thank you very much! Actually, I am new to both Guix and Guile Scheme, but if I can be of any help, I would be happy to try to contribute. Two points of concern at this time are as follows: * My current understanding of Guix's internationalization process is that translations are updated on Weblate and that translated documents are generated with po4a. It seems that the current file structure and options should not be changed significantly after the change. * A configuration file must be given to the integrated po4a command. In the long run, there might be a room to consider how this configuration file should be managed, i.e., whether it should be automatically generated by Guile or updated manually. (At this point, the file structure is simple enough that the latter might be enough.) Anyway, I will try to think about how to update the process. Sincerely, gemmaro