po for anything

po for anything 0.21

Mainly a bugfix release. The most important change may be the ability to pass options to modules from po4a(1)'s config file.

Unfortunately, this is undocumented yet ;)

Milestone information

Project:
po for anything
Series:
head
Version:
0.21
Released:
 
Registrant:
Jordi Vilalta Prat
Release registered:
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

File Description Downloads

Release notes 

This release does not have release notes.

Changelog 

View the full changelog

  [Nicolas François]

  (TeX module)

  * Fix an issue with file excluded from inclusion:

    after a gettextization, the PO file contained two \input{x}.

  * Add a generic way to specify separators. For example, this permits

    to translate each cell separately in a tabular environment.

  * Just warn instead of dying when the documentclass cannot be found

  (Man module)

  * Add a verbose option, for "po4a -v".

  * Add comments to the PO file, and fix the testsuite accordingly.

  * Remove the with-non_breaking_spaces and with-hyphen_to_minus options

    and document the transliterations performed in pre_trans and post_trans.

  * Fix an encoding issue with non-breaking spaces.

  (Po.pm)

  * Allow multiple comment lines for a PO string.

  (po4a)

  * Add support for options/aliases in the config files.

    First try ... undocumented feature.

  [Jordi Vilalta]

  (Xml module)

  * Handle the processing instructions ( <?...?> ) simply ignoring them

  (Docbook module)

  * Wrap by default

  (Po module)

  * Handle tabs when canonizing

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.