March 2017 - Devel - Po4a List Archives

[po4a-Bugs][314392] Installation doesn't fully respect PREFIX

by po4a-bugs＠alioth.debian.org

po4a-Bugs item #314392 was changed at 29/03/2017 14:38 by Martin Quinson You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=314392&gro... Status: Open Priority: 3 Submitted By: Renato Botelho (garga-guest) >Assigned to: Nobody (None) Summary: Installation doesn't fully respect PREFIX Category: None Group: None Resolution: None Initial Comment: I'm working to update po4a to 0.44 on FreeBSD ports tree, and I'm having issues when I set prefix to something != /usr/local. It installs some files on the PREFIX I defined and other files on /usr/local. I'm attaching a full buildlog so you can see which files are installed on /tmp/po4a-0.44 prefix and which ones are installed on /usr/local. ---------------------------------------------------------------------- >Comment By: Martin Quinson (mquinson) Date: 29/03/2017 14:38 Message: Hello everybody, I tried to fix it recently. Could you please tell me if 0.51 works better for you, and if not, what are the symptoms now? Thanks in advance, Mt. ---------------------------------------------------------------------- Comment By: Denis Barbier (barbier-guest) Date: 10/09/2013 10:15 Message: After reading Module::Build sources, I believe that my $mandir = $self->install_destination('bindoc'); may do the job, and it works here. Justin, could you please check on your system? ---------------------------------------------------------------------- Comment By: Denis Barbier (barbier-guest) Date: 10/09/2013 09:29 Message: Justin, you are right, this is what I will implement. However I would like to understand why there are such discrepancies, any hint is welcome. ---------------------------------------------------------------------- Comment By: Justin Hallett (thesin-guest) Date: 10/09/2013 02:14 Message: I just had a thought $self->install_map->{'blib/bindoc'}; works for you, but is undefined for me $self->install_path()->{'bindoc'}; works for me, but is undefined for you maybe you should set it to $self->install_map->{'blib/bindoc'}; if it's undefined then set it to $self->install_path()->{'bindoc'}; and if it's still undefined fall back to $self->install_sets($self->installdirs)->{'bindoc'}; Not the most elegant but better then what is there currently I'd think. ---------------------------------------------------------------------- Comment By: Justin Hallett (thesin-guest) Date: 10/09/2013 02:09 Message: Module::Build 0.40.07 Perl 5.12.4 I bet I know why I bet it's because I'm setting --install_path bindoc=/sw/share/man/man1 destdir=/sw/src/fink.build/root-po4a-0.45-1 I haven't looked at the debian version but maybe it's not setting bindoc? I'll login to my debian box and grab the source and check rules and see ---------------------------------------------------------------------- Comment By: Denis Barbier (barbier-guest) Date: 10/09/2013 01:22 Message: Hello, Your version does not work here on my Debian box :( With both Module::Build 0.38 and 0.4003, $mandir is then undefined. Which version do you use? ---------------------------------------------------------------------- Comment By: Justin Hallett (thesin-guest) Date: 10/09/2013 00:31 Message: of course with this method line 136 is no longer required but it doesn't hurt so I left it in mine, again I hope it helps solve this report. ---------------------------------------------------------------------- Comment By: Justin Hallett (thesin-guest) Date: 10/09/2013 00:26 Message: it seems that changing line 135 to my $mandir = $self->install_path()->{'bindoc'}; seems to work for me. Maybe this will help others? ---------------------------------------------------------------------- Comment By: Justin Hallett (thesin-guest) Date: 04/09/2013 20:01 Message: I used perl -pi -e 's,install_sets[$]\$self-(.)installdirs[$]-.(\{)(.)bindoc.,install_map-\1\2\3blib/bindoc\3,g' Po4aBuilder.pm to patch before build which gives me my $mandir = $self->install_map->{'blib/bindoc'}; on line 135 of Po4aBuilder.pm but now I get these errors, that is the right line cause I had no /usr/local but it's not not installed locales or intl man pages at all. ./Build install --install_path lib=/sw/lib/perl5 --install_path arch=/sw/lib/perl5/darwin-thread-multi-2level --install_path script=/sw/bin --install_path bin=/sw/bin --install_path bindoc=/sw/share/man/man1 --install_path libdoc=/sw/share/man/man3 --install_path binhtml=/sw/share/man/man1 --install_path libhtml=/sw/share/man/man3 destdir=/sw/src/fink.build/root-po4a-0.45-1 Use of uninitialized value $mandir in substitution (s///) at Po4aBuilder.pm line 136. Use of uninitialized value $localedir in substitution (s///) at Po4aBuilder.pm line 141. ---------------------------------------------------------------------- Comment By: Denis Barbier (barbier-guest) Date: 04/09/2013 18:11 Message: Replace l.132 of Po4aBuilder.pm my $mandir = $self->install_sets($self->installdirs)->{'bindoc'}; by my $mandir = $self->install_map->{'blib/bindoc'}; ---------------------------------------------------------------------- Comment By: Justin Hallett (thesin-guest) Date: 04/09/2013 00:34 Message: it does not, I can post my build log if it helps but 0.45 is doing the same thing. ---------------------------------------------------------------------- Comment By: Denis Barbier (barbier-guest) Date: 03/09/2013 23:54 Message: Hello, I had trouble with Module::Build, and made some changes in 0.45. Could you please check whether 0.45 fixes this bug? ---------------------------------------------------------------------- Comment By: Justin Hallett (thesin-guest) Date: 03/09/2013 23:48 Message: As the fink maintainer for po4a I can confirm this behaviour from 0.42 to 0.45, is there a patch or Build option to fix this yet? ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=314392&gro...

7 years, 9 months

1
0
0 / 0

[po4a-Bugs][315353] Feature request: add option to escape quotes in xml ouptut (for Android)

by po4a-bugs＠alioth.debian.org

po4a-Bugs item #315353 was changed at 28/03/2017 20:36 by Martin Quinson You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=315353&gro... >Status: Closed Priority: 3 Submitted By: josh dubois (duboisj-guest) Assigned to: Nobody (None) Summary: Feature request: add option to escape quotes in xml ouptut (for Android) Category: Xml.pm Group: None >Resolution: Fixed Initial Comment: Android string resources must have both single (') and double (") quotes escaped. po4a is useful for generating translations of Android string resources, but does not escape quotes, so if the translated strings include quotes, the Android build tools fail. See: http://developer.android.com/guide/topics/resources/string-resource.html A patch against: commit f78ee1444db361c298ea55a2355b6c74c5e478db Merge: b2b0cb2 d14c303 Author: Martin Quinson <martin.quinson(a)loria.fr> Date: Tue Oct 13 22:40:56 2015 +0200 Merge branch 'master' of git+ssh://scm.alioth.debian.org//git/po4a/po4a Is attached. ---------------------------------------------------------------------- >Comment By: Martin Quinson (mquinson) Date: 28/03/2017 20:36 Message: Committed as 8f77a82a. Thanks for the patch. ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=315353&gro...

7 years, 9 months

1
0
0 / 0

po4a v0.50 released, and considerations for the future

by Martin Quinson

Hello all, I think that I broke the installation abilities of the 0.49 release, so I'm releasing a new version with that problem fixed. I took the opportunity to integrate other patches laying around. There is still many others to fix, and even some patches to integrate. I will try to work on it soon. Any help would be welcome but I fully understand the difficulty of entering this code base ;) Speaking of which. po4a is a mature software, but I have the feeling that perl is a dying ecosystem. I am playing with the idea of reimplementing po4a in another language, in a hope to increase further the contributer circle. A full rewrite is a lot of work given po4a's size (about 3500 lines of perl), but the soft is well tested, which will constitute a real asset. Scala combinators would certainly be a nice technical choice to write all the parsers that we have, but I'm not sure that it would be a cleaver move to increase the developper community. Any scala fan in the room (beyond me, I mean)? Instead, I think that python is the scripting language of the future, even if I'm not really fluent in that language (yet). It seems to me that writing regulat expressions (which constitute 80% of the po4a complexity) in python is not really pleasant. A very quick googling tells me that the parsimonious package may be interesting here. But like I said, I'm not fluent in python, and any insight is welcome. That being said, my time on po4a is really scarce and I'm not fluent in python, so I will not be able to do it alone anytime soon. For now, I'd like to discuss the opportunity of a full rewrite, and the available technologies that we could leverage. At some point, I hope to find the time (or to receive the help) needed to develop some proof of concept implementations before taking a strong decision. Anyway. For now, the 0.50 release can be downloaded from https://alioth.debian.org/frs/?group_id=30267 and some other perl version will follow (I hope) to further integrate the patchs that you guys provide and fix some bugs when I manage to. Thanks for your attention, Mt. -- Learning and doing is the true spirit of free software; learning without doing gets you academic sterility, and doing without learning is all too often the way things are done in proprietary software. -- Raph Levien

7 years, 9 months

1
0
0 / 0

[po4a-Bugs][314919] Fix a couple of bugs in asciidoc module

by po4a-bugs＠alioth.debian.org

po4a-Bugs item #314919 was changed at 27/03/2017 18:16 by Martin Quinson You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=314919&gro... >Status: Closed Priority: 3 Submitted By: Alexander Golubev (fat-zer-guest) Assigned to: Nobody (None) Summary: Fix a couple of bugs in asciidoc module Category: None Group: None Resolution: Fixed Initial Comment: Here is a fix of couple of bugs: The first one was recently mentioned on the mail list: https://lists.alioth.debian.org/pipermail/po4a-devel/2015-January/002287.... And Can be triggered by the last part of the test in the patch ---- Block image macro without alt text: image::foo.png[] ---- The second one is about missing translations for image Alt text in statements like next: ---- image::foo.png["Block image with external title"] ---- The rest part of the test-case just ensures that the patch doesn't break neighboring stuff like asciidoc's styles. ---------------------------------------------------------------------- Comment By: Martin Quinson (mquinson) Date: 27/03/2017 17:56 Message: This is fixed in f90ae3b68a89bae2f76627beb4b5cad204703678. Thanks for the patch, and sorry for the delay. ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=314919&gro...

7 years, 9 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 27/03/2017 18:16 by Martin Quinson You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=312737&gro... Status: Open 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: 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...

7 years, 9 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 27/03/2017 18:11 by Martin Quinson You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=311648&gro... Status: Open 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: 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...

7 years, 9 months

1
0
0 / 0

[po4a-Bugs][315040] [patch] fix path to man pages when '--install_path man' is specified

by po4a-bugs＠alioth.debian.org

po4a-Bugs item #315040 was changed at 27/03/2017 18:06 by Martin Quinson You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=315040&gro... >Status: Closed Priority: 3 Submitted By: John Hein (gettowork-guest) Assigned to: Nobody (None) Summary: [patch] fix path to man pages when '--install_path man' is specified Category: None Group: None >Resolution: Fixed Initial Comment: If you call Build.PL with --install_path bindoc=/some/different/path, that path will not be where man pages go when you run 'Build install'. Instead it uses the man page installation directory from the default perl configuration. '--install_path lib' and '--install_path bin' work as expected. But the bindoc specification is used in Po4aBuilder.pm's ACTION_install to override Module::Build's normal handling for some man pages. However, the man pages do not go to the install_path for bindoc specified by the command line --install_path option. The attached patch attempts to fix the situation by using the 'install_path' set of directories when processing the mandir location. To repeat the observed problem, try configuring by using something like the following: perl Build.PL --destdir=/tmp --install_path lib=/some_nonexistent_temp_dir/lib/perl/site_perl --install_path bin=/some_nonexistent_temp_dir/bin --install_path script=/some_nonexistent_temp_dir/bin --install_path bindoc=/some_nonexistent_temp_dir/man/man1 --install_path libdoc=/some_nonexistent_temp_dir/lib/perl/site_perl/man/man3 --install_path man=/some_nonexistent_temp_dir/lib/perl/site_perl/man Then install using: perl Build --destdir=/tmp Notice that some of the man pages are not installed under /tmp/some_nonexistent_temp_dir ---------------------------------------------------------------------- >Comment By: Martin Quinson (mquinson) Date: 27/03/2017 18:06 Message: I commited your patch in 894e0930 thus closing. Many thanks for your work, and sorry for the extra delay. Mt. ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=315040&gro...

7 years, 9 months

1
0
0 / 0

[po4a-Bugs][314748] Text.pm: add an option to force no wrap lines in translated text

by po4a-bugs＠alioth.debian.org

po4a-Bugs item #314748 was changed at 27/03/2017 18:02 by Martin Quinson You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=314748&gro... >Status: Closed Priority: 3 Submitted By: Alexander Golubev (fat-zer-guest) Assigned to: Nobody (None) Summary: Text.pm: add an option to force no wrap lines in translated text Category: None Group: None >Resolution: Fixed Initial Comment: subj; such option may be useful when e.g. translating a docbook witch includes shell scripts directly to it self and the translator wants to get the same structure on output. ---------------------------------------------------------------------- >Comment By: Martin Quinson (mquinson) Date: 27/03/2017 18:02 Message: Hello, I commited your patch, thus closing. Many thanks for that. Next time, I'll try to be a bit more reactive... Bye, Mt. ---------------------------------------------------------------------- Comment By: Alexander Golubev (fat-zer-guest) Date: 12/07/2014 03:14 Message: Here is the promised patch. I haven't done any unittest's yet because the Text module has no such yet. ---------------------------------------------------------------------- Comment By: Alexander Golubev (fat-zer-guest) Date: 11/07/2014 18:46 Message: > Also, I have a doubt about the fact that --auto accepts a comma separated list of tags that should be wrapped. It seems to me that your patch accepts a boolean option where wrap is completely disabled or not, am I wrong? If so, tests cases would be welcome. If I'm right please update the doc. The patch accept 1 option --wrap with one of 3 parameters: auto : wrap lines, the current behavior force_no : no line wrapping: the lines in the translation will be broken on the same place as they were in the source. no : even I don't clearly understand that's that option does =) it supposed to broke lines in special formats: asciidoc, control, debianchangelog, etc only if there are some special conditions. Although, I'm not really into those formats so I don't really know how that supposed to be done... So IMO it would be better to stay only with 1 boolean option "--no-wrap" or "--force-no-wrap" to behave like the "--wrap=forse_no" in the current patch. I'll prepare the new patch in a day... ---------------------------------------------------------------------- Comment By: Martin Quinson (mquinson) Date: 09/07/2014 02:44 Message: I would feel better if you could provide a little test case in the t/ directory to ensure that it works as expected (and that it still does in the future). Also, I have a doubt about the fact that --auto accepts a comma separated list of tags that should be wrapped. It seems to me that your patch accepts a boolean option where wrap is completely disabled or not, am I wrong? If so, tests cases would be welcome. If I'm right please update the doc. In any case, many thanks for the report and for the patch! ---------------------------------------------------------------------- Comment By: Alexander Golubev (fat-zer-guest) Date: 07/07/2014 16:20 Message: Here is a proposed patch... But somebody should review it... ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=314748&gro...

7 years, 9 months

1
0
0 / 0

[po4a-Bugs][315075] po4a 0.46 breaks formatting of man pages

by po4a-bugs＠alioth.debian.org

po4a-Bugs item #315075 was changed at 27/03/2017 18:00 by Martin Quinson You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=315075&gro... >Status: Closed Priority: 3 Submitted By: Luiz Fernando Rangheti (elchevive-guest) Assigned to: Nobody (None) Summary: po4a 0.46 breaks formatting of man pages Category: None Group: None >Resolution: Wont Fix Initial Comment: Hi, I package po4a for openSUSE and in the last update, 0.46 it breaks the formatting of man pages. You can see more information on the comments here: https://build.opensuse.org/request/show/308224 Regards, Lui ---------------------------------------------------------------------- >Comment By: Martin Quinson (mquinson) Date: 27/03/2017 18:00 Message: Hello, this was discussed here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786525 I'm sorry for that change and will be more careful in the future. But I wont revert that change either, sorry. Bye, Mt. ---------------------------------------------------------------------- Comment By: Luiz Fernando Rangheti (elchevive-guest) Date: 18/01/2017 16:21 Message: Hi, Whit man-db-2.7.6 the problem is gone! ---------------------------------------------------------------------- Comment By: Alexander Golubev (fat-zer-guest) Date: 05/01/2017 03:45 Message: * meant >=sys-apps/man-db-2.7.6 ---------------------------------------------------------------------- Comment By: Alexander Golubev (fat-zer-guest) Date: 05/01/2017 02:04 Message: >=mandb-1.6.1 fixed this in their own man module: http://git.savannah.gnu.org/cgit/man-db.git/commit/?id=f8034f54218d002d35... ---------------------------------------------------------------------- Comment By: Luiz Fernando Rangheti (elchevive-guest) Date: 20/09/2016 14:49 Message: Any progress? I'd like to update po4a in openSUSE to 0.48 but I'm stuck with 0.45 ---------------------------------------------------------------------- Comment By: Martin Quinson (mquinson) Date: 30/06/2015 01:39 Message: @Robert: Any progress on this maybe? I'm myself not very confident with the Man module and your help is really welcome. Also, do you know why man-db is using its own module? Should we try to merge our efforts maybe? Many many thanks for your help. ---------------------------------------------------------------------- Comment By: Robert Luberda (robert) Date: 01/06/2015 01:41 Message: My initial patch handles only '\t' as column separator, while man-db package uses '@'. I am working on a fix for this. However man-db package uses its own Manext.pm module which implements handling of textblocks in its own way, and I am afraid that this man-db's module will need to be changed as well. ---------------------------------------------------------------------- Comment By: Alexander Golubev (fat-zer-guest) Date: 25/05/2015 14:59 Message: I can confirm it on gentoo. And that the bug was introduced with the release. Compare: === mandb.8.original === .TS tab (@); l l l l. Name@Type@Async@Filename _ Berkeley db@T{ Binary tree T}@Yes(a)\fIindex.bt\fR GNU gdbm v >= 1.6@T{ Hashed T}@Yes(a)\fIindex.db\fR GNU gdbm v < 1.6@T{ Hashed T}@No(a)\fIindex.db\fR UNIX ndbm@T{ Hashed T}@No(a)\fIindex.(dir|pag)\fR .TE === mandb.8.ru [0.45] === .TS tab (@); l l l l. Название@Тип@Асинхронность@Имя файла _ Berkeley db@T{ двоичное дерево T}@Да(a)\fIindex.bt\fP GNU gdbm v >= 1.6@T{ Хэш T}@Да(a)\fIindex.db\fP GNU gdbm v < 1.6@T{ Хэш T}@Нет(a)\fIindex.db\fP UNIX ndbm@T{ Хэш T}@Нет(a)\fIindex.(dir|pag)\fP .TE === mandb.8.ru [0.46] === .TS tab (@); l l l l. Название Тип Асинхронность Filename _ Berkeley db T{ двоичное дерево T} Да \fIindex.bt\fP GNU gdbm v >= 1.6 T{ Хэш T} Да \fIindex.db\fP GNU gdbm v < 1.6 T{ Хэш T} Нет \fIindex.db\fP UNIX ndbm T{ Хэш T} Нет \fIindex.(dir|pag)\fP .TE ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=315075&gro...

7 years, 9 months

1
0
0 / 0

[po4a-Bugs][314919] Fix a couple of bugs in asciidoc module

by po4a-bugs＠alioth.debian.org

po4a-Bugs item #314919 was changed at 27/03/2017 17:56 by Martin Quinson You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=314919&gro... Status: Open Priority: 3 Submitted By: Alexander Golubev (fat-zer-guest) Assigned to: Nobody (None) Summary: Fix a couple of bugs in asciidoc module Category: None Group: None >Resolution: Fixed Initial Comment: Here is a fix of couple of bugs: The first one was recently mentioned on the mail list: https://lists.alioth.debian.org/pipermail/po4a-devel/2015-January/002287.... And Can be triggered by the last part of the test in the patch ---- Block image macro without alt text: image::foo.png[] ---- The second one is about missing translations for image Alt text in statements like next: ---- image::foo.png["Block image with external title"] ---- The rest part of the test-case just ensures that the patch doesn't break neighboring stuff like asciidoc's styles. ---------------------------------------------------------------------- >Comment By: Martin Quinson (mquinson) Date: 27/03/2017 17:56 Message: This is fixed in f90ae3b68a89bae2f76627beb4b5cad204703678. Thanks for the patch, and sorry for the delay. ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=314919&gro...

7 years, 9 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 March 2017