artifact_id;status_id;status_name;priority;submitter_id;submitter_name;assigned_to_id;assigned_to_name;open_date;close_date;last_modified_date;summary;details;"Category";"Group";"Resolution"
300874;1;"Open";4;194;"Martin Quinson";10600;"Martin Quinson";"2004-08-07 21:15";"";"2006-10-27 15:35";"Included files should be searched in the path of the master";"If you want to handle a file being in another directory, all included ones are not found because they are searched in the current directory instead of where the master file is.";"None";"None";"None"
300958;1;"Open";3;10600;"Martin Quinson";100;"Nobody";"2004-09-27 09:18";"";"2006-10-27 15:35";"Adding PO file headers to translated documents";"the po-debiandoc tool writes the PO-file header in the generated
SGML file (enclosed in <!-- ... -->, of course), so that these
useful informations are contained in this file.
It would be really nice if po4a-translate did something similar.


(Reported by Denis on the mailing list)
";"None";"None";"None"
301026;1;"Open";3;11062;"Yves Rütschlé";10156;"Jordi Vilalta";"2004-11-06 20:05";"";"2006-10-27 15:35";"po4a-update eats characters not in charset without asking";"If you translate a PO file into some language
using iso8859-1, but forget to precise the charset in the
header of the PO file, and don't give the charset to
po4a-update either, then po4a-update proceeds to remove all
accentuated characters from the file.

I am not sure what the best way to handle this would be;
presumably, one could do some heuristic (""there are many
strange characters in there, probably this isn't ascii"") and
ask for confirmation that you do actually want to filter out
strange characters. Fact is, most of the time you won't want
to.
";"None";"None";"None"
302133;1;"Open";3;10600;"Martin Quinson";10156;"Jordi Vilalta";"2005-09-03 19:31";"";"2006-10-27 15:35";"Xml module does not honor the -w flag of po4a-translate";"As the title says, the Xml module does not wrap the generated document, even if asked to by the -w flag

";"Xml.pm";"None";"None"
302134;1;"Open";3;10600;"Martin Quinson";100;"Nobody";"2005-09-03 19:36";"";"2006-10-27 15:35";"The Xml module does not normalize the document, making it difficult to use addenda";"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.";"Xml.pm";"None";"None"
311647;1;"Open";3;208976;"Michael Terry";100;"Nobody";"2009-05-03 14:04";"";"2009-05-03 14:04";"Allow marking some paragraphs/phrases as not-for-translation";"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 <!-- po4a: ignore --> or something.";"None";"None";"None"
311648;1;"Open";3;208976;"Michael Terry";14733;"Neil Williams";"2009-05-03 14:12";"";"2009-11-16 22:28";"Integrate tightly with a package's existing po files";"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.  :)";"None";"None";"None"
312737;1;"Open";3;211064;"Carsten Stupka";100;"Nobody";"2010-10-01 22:49";"";"2010-10-01 22:49";"Texinfo files get somewhat mangled by po4a";"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";"None";"None";"None"
312893;1;"Open";3;211378;"Jakub Hrozek";100;"Nobody";"2010-12-15 17:36";"";"2010-12-15 17:36";"RFE: provide an option that only recreates translated files from po and original";"Currently, the only way to use po4a to only recreate translated files from originals and .po files is calling po4a-translate. However, this has the downside of not using the config file.

Since po4a already contains --no-translations option, is it possible to also include something like --only-translations?";"None";"None";"None"