February 2018 - Devel - Po4a List Archives

by hottea

hi, dear all. I'm not sure if I have join this mail list. I don't know how to join as there isn't a how-to on the website. I hope you can receive my email. I found po4a when doing some translation, and found that there's not a complete Simplified Chinese translation for po4a, so I do the work. I create a project on transifex, a localization platform, see www.transifex.com/projects/p/po4a-translation. I wonder how could I see the final result? Where are the translation installed? If you're interested in the Simplified Chinese translation for po4a, please join the language team on transifex.com, you can also request language on transifex. ----- send from hottea's openSUSE

3 years, 10 months

2
1
0 / 1

Deprecating the po4a-build script?

by Martin Quinson

Hello, I am wondering whether some is actually using po4a-build. It seems that this binary is superseeded by po4a(1), and I don't see any po4a-build.conf file in the whole Debian archive: https://codesearch.debian.net/search?q=po4a-build.conf There is 437 mentions of this file on github, but it seems to be several copies of a file coming named 0.41-po4a-build.patch aiming at improving the performance of that script. That seems to come from gentoo, somehow (and the patch does not apply anymore). If I extend to po4a-build on github, it seems that many people are packaging po4a in various distro, but I cannot find any use of the po4a-build script. Did I miss something? I am considering deprecating this binary, ie having it displaying a big fat warning "The po4a-build script will soon be removed. Please switch to po4a(1), or report to the po4a maintainers" and pausing for five seconds. This behavior could be disabled by setting some environment variable, maybe. Then, if nobody comes back to us after 1 or 2 years, we could remove this binary. Less code to maintain, less doc to translate, less technical debt. What do you guys think? Mt. -- If you want peace, improve global education. -- Translation of "si vis pacem, para bellum" at the age of the Internet.

6 years, 9 months

2
1
0 / 0

Releasing po4a this month? New features? Translations?

by Martin Quinson

Hello, 6 months after the previous release, we have a very decent set of new features and improvements. We could always dream of more, but I think that we should release now. https://github.com/mquinson/po4a/blob/master/NEWS Do someone have something to push before the release? If not, we should still improve the translations. Preferably on weblate, as described here: https://po4a.org/getinvolved.php But if you prefer to go for pull requests, it works too. I would like to release somewhere by the end of the month, if possible. Thanks a lot, Mt. -- You have a problem and decide to use git. Now you have a forest of subtly incompatible solutions.

6 years, 10 months

5
8
0 / 0

Alioth is closing, po4a needs a new home very soon

by Martin Quinson

Hello pals, it was decided that the alioth hosting service will be soon decommissioned[1] next month, and we should move the development to another hosting service. I should have done that mail before, sorry. The git itself was already mirrored on github[2], so I will just change the README and everything to point to github instead. The web server can also be hosted on github, but this has still to be done and I'm really short on time. Any help would be welcome here. The source code of the web pages were already mirrorred on github[3], but we should take care of the hosting. The most concerning parts are this mailing list, and the issues that are reported on alioth. For the issues, I could not find any tool to move them to github and I fear that we would have to it manually. Does someone know such an automatic tool or would be willing to do the move? If we have an automatic tool, I'd like to move the closed issues also, as they contain valuable information. If not I think we should at least copy the open issues over. Again, any help would be welcome here. For the mailing lists, I have no good idea. Do you? If the list gets shut down on Feb 1st as it could, we have the IRC channel to coordinate: #po4a on oftc. I have a permanent presence on that channel so it could work as a (very) temporarily solution. But someone should come up with a better idea, I think. Again, I'm sorry for the short notice, I'm trying to do too much things at the same time these days. Bye, Mt. [1] https://wiki.debian.org/Alioth#Deprecation_of_Alioth [2] https://github.com/mquinson/po4a [3] https://github.com/mquinson/po4a-website -- Being able to break security doesn’t make you a hacker anymore than being able to hotwire cars makes you an automotive engineer. -- Eric S. Raymond.

6 years, 10 months

5
31
0 / 0

po4a is now fully relying on weblate for its translation

by Martin Quinson

Hello, thanks to the help of Michal and Jean-Baptiste, the whole po4a project is now translatable through weblate (we just added the website). This is really a great help, and I would like to publicly thank Michal for that great piece of software (weblate), and for the generous hosting on his infrastructure. Now, as he is pointing, this free hosting still cost him some money, so any donation would is welcome. Uf you're in position to do that, please help him providing this service for free: https://weblate.org/donate/ Bye, Mt. -- A language that doesn't affect the way you think about programming is not worth knowing. -- "Epigrams in Programming", by Alan J. Perlis

6 years, 10 months

1
0
0 / 0

[po4a-Bugs][311648] Integrate tightly with a package's existing po files

by po4a-bugs＠alioth.debian.org

po4a-Bugs item #311648 was changed at 06/02/2018 17:30 by Martin Quinson You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=311648&gro... >Status: Closed Priority: 3 Submitted By: Michael Terry (mterry-guest) Assigned to: Nobody (None) Summary: Integrate tightly with a package's existing po files Category: None Group: None Resolution: None Initial Comment: I recently converted my project's documentation to use po4a. It was great, thanks for the software. However, I wanted to avoid having two gettext domains and used a bit of Makefile magic to make it happen. You can read about it here: http://mterry.name/log/2009/05/02/translate-your-documentation/ It would be nice if there was a mode for po4a where more of that would happen automatically. * The ability to read po files without also writing to them * The option to merge the resulting pot file with another * The ability to read the language list from po/LINGUAS In addition, it would be nice if po4a shipped some m4 macros to make writing Makefile integration easier. Stuff like installing the translated man pages, etc. Together with the above, it means I could just have something like "PO4A_MAN_PAGES = one.1 two.1 three.1" and everything would just happen within my existing translation framework. The tricky part would be filtering out the messages again when making the dist tarball (see blog post above). But I'd be happy even if that weren't included, since that's pretty hacky. :) ---------------------------------------------------------------------- >Comment By: Martin Quinson (mquinson) Date: 06/02/2018 17:30 Message: Hello, this request is partially covered by existing tools, and initial requester did not comment on the remarks, almost 10 years ago. I thus doubt that there is many interest in migrating this to github. If you disagree, please reopen a bug on github. Meanwhile, I close this one. Thanks, ---------------------------------------------------------------------- Comment By: Martin Quinson (mquinson) Date: 27/03/2017 18:11 Message: Hello, what you are trying to do can be achieved by using po4a-translate and po4a-updatepo directly, I guess. I do not plan to work on implementing your proposal myself, but if you come up with a simple and well tested patch, I will certainly integrate it. Thanks, Mt. ---------------------------------------------------------------------- Comment By: Neil Williams (codehelp) Date: 16/11/2009 23:28 Message: Elements of what you requested are part of the po4a-build changes currently being tested. Rather than m4 macros, I've gone for a Makefile snippet based on how autotools and intltool handle the typical po/Makefile.in.in symlink. As for having two domains, I actually think it's useful - the script output messages and the documentation messages are orthogonal. Yes, it's nice to have both translated into the the same languages but putting all strings into one PO file (as a result of having one POT file) does have drawbacks: 1. The much larger % of strings from the documentation "swamp" the output strings, unless you use 'po4a -k 0', you risk losing the script output strings even if (it the separation had been retained) the output strings are at 100% 2. The output translations must be handled separately at runtime anyway. The script output goes into /usr/share/locale/ as binary files. The documentation output goes into /usr/share/doc/ as plain text, generally. In situations (like embedded environments) where a division is desirable, putting output and docs strings in one PO file causes aggravation. If the script output strings and doc strings are in one PO file, where does the resulting translation get installed? po4a already has ways of merging all POT content for all docs - po4a-build enhances that. po4a-build does indeed use simple KEY=VALUE config lines and does allow "everything to just happen within the existing *docs* translation framework". Take a look at po4a-build (currently in CVS, to be released as 0.37.0) and if it meets your needs, close this bug. If necessary, open new ones for features still missing. ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=311648&gro...

6 years, 10 months

1
0
0 / 0

[po4a-Bugs][312737] Texinfo files get somewhat mangled by po4a

by po4a-bugs＠alioth.debian.org

po4a-Bugs item #312737 was changed at 06/02/2018 17:08 by Martin Quinson You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=312737&gro... >Status: Closed Priority: 3 Submitted By: Carsten Stupka (cms-guest) Assigned to: Nobody (None) Summary: Texinfo files get somewhat mangled by po4a Category: None Group: None Resolution: None Initial Comment: I am unsure whether this can be considered an actual bug. I took a texinfo file from the GNU Bash reference manual and sucessfully converted it using texi2pdf. Then, I ran po4a -k0 over the original (without any localization strings) and tried to convert that file to a pdf file, which utterly fails. Makeinfo works on the file, though. But I can't really make out any differences between the original file and the unlocalized po4 output besides line breaks... (You might want to use KDiff3 instead of command line diffing) Source for missing reference files: http://www.gnu.org/software/bash/manual/bash.texi.tar.gz ---------------------------------------------------------------------- >Comment By: Martin Quinson (mquinson) Date: 06/02/2018 17:08 Message: The bug was said to be partially fixed 8 years ago, nobody answered to my request for additionnal debugging information. I'm thus closing the bug without migration (I dunno what to migrate now). Please reoppen in on github if the problem remains. Thanks for your understanding, Mt. ---------------------------------------------------------------------- Comment By: Martin Quinson (mquinson) Date: 27/03/2017 18:16 Message: Could you guys provide a minimal working example for that bug? I'd like to work on its resolution, but as is, I'm a bit clueless about what should be done. The provided example is ways too long to be really useful. Thanks in advance, Mt. ---------------------------------------------------------------------- Comment By: Denis Barbier (barbier-guest) Date: 02/10/2010 11:01 Message: Hello, thanks for your report. This is indeed a bug, I just fixed lib/Locale/Po4a/Texinfo.pm in SVN. The pdf looks fine to me now, but info generation is broken because of @ifset commands within @menu, I do not know yet how to fix it. ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=312737&gro...

6 years, 10 months

1
0
0 / 0

[po4a-Bugs][311647] Allow marking some paragraphs/phrases as not-for-translation

by po4a-bugs＠alioth.debian.org

po4a-Bugs item #311647 was changed at 06/02/2018 17:02 by Martin Quinson You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=311647&gro... >Status: Closed Priority: 3 Submitted By: Michael Terry (mterry-guest) Assigned to: Nobody (None) Summary: Allow marking some paragraphs/phrases as not-for-translation Category: None Group: None Resolution: None Initial Comment: It would be nice if I could mark some paragraphs as untranslatable. For example, say I have a docbook flie that lists a number of file paths as part of the documentation. These paths (like ~/.cache) show up to be translated, but I don't want them to be. Maybe some format-specific comment that po4a understands? In the docbook example, the paragraph being preceded by  or something. ---------------------------------------------------------------------- >Comment By: Martin Quinson (mquinson) Date: 06/02/2018 17:02 Message: Migrated as https://github.com/mquinson/po4a/issues/77 thus closing. ---------------------------------------------------------------------- Comment By: Martin Quinson (mquinson) Date: 30/03/2017 22:30 Message: Just to be sure: in which modules would you need this feature, Michael? Implementing it in Sgml may be particularly challenging so I'd prefer not to do that if you don't really need it. Is it enough if it works in Man? Thanks for your patience, Mt ---------------------------------------------------------------------- Comment By: Martin Quinson (mquinson) Date: 30/03/2017 22:25 Message: Just for the record, this feature is now implemented in the man module (see section "Hiding text from po4a" from Locale::Po4a::Man(3pm)) ---------------------------------------------------------------------- Comment By: Michael Terry (mterry-guest) Date: 29/07/2010 20:14 Message: That would be fine. I'd also be interested in similar syntax for man pages too. ---------------------------------------------------------------------- Comment By: Denis Barbier (barbier-guest) Date: 29/07/2010 15:39 Message: You are right, that would be nice. The parser can cope with comments only if they are embedded within a paragraph, which means that in XML one has to write <para>Foo bar</para> to have this comment printed into PO files. One could indeed define special comments, e.g. <para>Foo bar</para> to have a paragraph copied verbatim into translated documents. Note that these comments will not be removed from translated documents, I believe that this is fine. You can test by editing Locale/Po4a/Xml.pm like this: replace if ($translate ne "") by if ($translate ne "" && !(defined($comments) && $comments =~ m/^\s*po4a:\s*ignore/s)) I will commit this change unless you report problems with it. ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=311647&gro...

6 years, 10 months

1
0
0 / 0

[po4a-Bugs][302134] The Xml module does not normalize the document, making it difficult to use addenda

by po4a-bugs＠alioth.debian.org

po4a-Bugs item #302134 was changed at 06/02/2018 16:56 by Martin Quinson You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=302134&gro... >Status: Closed Priority: 3 Submitted By: Martin Quinson (mquinson) Assigned to: Nobody (None) Summary: The Xml module does not normalize the document, making it difficult to use addenda Category: Xml.pm Group: None Resolution: None Initial Comment: For the addenda to work, it is better to have short lines (so that the translator can choose between which ones to put there addenda). The Sgml module does so since the bug #263300, in Debian. Thanks for your time, Mt. ---------------------------------------------------------------------- >Comment By: Martin Quinson (mquinson) Date: 06/02/2018 16:56 Message: Migrated as https://github.com/mquinson/po4a/issues/76 thus closing. ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=302134&gro...

6 years, 10 months

1
0
0 / 0

[po4a-Bugs][302133] Xml module does wrap the document, even when passing --width to po4a-translate

by po4a-bugs＠alioth.debian.org

po4a-Bugs item #302133 was changed at 06/02/2018 16:54 by Martin Quinson You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=302133&gro... >Status: Closed Priority: 3 Submitted By: Martin Quinson (mquinson) Assigned to: Jordi Vilalta (jvprat-guest) Summary: Xml module does wrap the document, even when passing --width to po4a-translate Category: Xml.pm Group: None Resolution: None Initial Comment: As the title says, the Xml module does not wrap the generated document, even if asked to by the -w flag ---------------------------------------------------------------------- >Comment By: Martin Quinson (mquinson) Date: 06/02/2018 16:54 Message: Migrated as https://github.com/mquinson/po4a/issues/75 thus closing. ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=302133&gro...

6 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Devel February 2018