po for anything 0.25

The most important changes are: new gettextize algorithm, support for mdoc, beginning of the support for placeholders in XML, support for CDATA in XML, added po4aman-display-po to help translators of man pages to check how the translation of theirs pages looks like, and a lot of bug fixes and documentation fixes.

Milestone information

Project:
po for anything
Series:
head
Version:
0.25
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]
  (Po.pm)
  * Missing =back in the pod part.
  * consecutive escaped tabulations in the PO: only the first one was
    un-escaped. Closes: #359352
  * gettextize: do not associate the strings by their order in the POs, but by
    their order in the documents. This permits to gettextize documents
    which have the same structure, but where a string have
    multiple translations, or when different strings have the same translation.
    If multiple translations appear for a string, both strings are proposed in
    the PO. Closes: #326670
  (po4a)
  * When a master document is specified twice in a configuration file:
    - do not ignore the options specified in the first line;
    - also warn in this case since po4a may not do what the user wants.
  * Fix the documentation: po4a do not use the POT-Creation-Date field of the
    POT and PO headers. It only updates the POs with msgmerge -U.
    Closes: #360141
  (Man.pm)
  * Documentation: this module is no more beta.
  * Another fix for "when a font modifier if followed by another font
    modifier". Also add a test for this case.
  * mdoc support.
  * Do not put the header at the top of the file, but just before the .TH
    macro. This will preserve the indications on how to process the page if
    the first line contains something like: '\" t
  (Xml.pm)
  * Implement placeholders: this permits to specify that footnotes must not be
    translated inside a paragraph, but are translated separately and a
    <placeholder0> tag will be put where the footnote must be installed.
  * In tag_extract_doctype, we can't test whether the Document Type Definition
    contains an Internal Subset by searching the document for "]>" because
    this is also used for closing the CDATA Sections. This caused
    segmentation faults. Closes: #362169
  * get_string_until: add a option to search a regular expression. The
    default is to search for a fixed string. Also make sure get_string_until
    works when the serach string (or regex) contains a newline (\n).
  * When there is an Internal Subset, the Document Type Definition ends with
    "]\s*>", not necessarily "]>".
  * Add support for CDATA Sections.
  (po4aman-display-po)
  * new script to display a translated man page with a given PO.
    Thanks to Thomas Huriaux.
  (po4a.7.pod)
  * Fix a typo in the detailed example for the beginboundary field.
    Thanks to Ognyan Kulev.

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.