ubuntu-developer-manual team mailing list archive

[Kyle Nitzsche <kyle.nitzsche@xxxxxxxxxxxxx>]

On 01/06/2011 06:58 PM, Kevin Godby wrote:
> On Thu, Jan 6, 2011 at 5:47 PM, Kyle Nitzsche
> <kyle.nitzsche@xxxxxxxxxxxxx>  wrote:
> > >  OK. Kevin, it seems the python script (thing 'o beauty though it is ;)
> > >  should be dropped. And that we deal with unescaped*problematic*  special
> > >  characters in msgstr fields in another way. Do you agree?
> Yes, I agree.  There's unfortunately no easy way to parse TeX code
> outside of TeX itself.

So, I've backed this out with two commits.

The first one included bug fixes and better output (for pride's sake ;).

The second is a full reversion.

./lang_pdfs will fail if invalid trans are present.

Bzr log entries below.

------------------------------------------------------------
revno: 65
committer: Kyle Nitzsche <kyle.nitzsche@xxxxxxxxxxxxx>
branch nick: ubuntu-developer-manual
timestamp: Thu 2011-01-06 19:09:03 -0500
message:
  revert previous work to first check for invalid unescaped chars in
  po file msgstr fields because, whether such unescaped special chars
  need to be escaped depends on a context that only LaTeX itself can
  properly determine. That is, there is no straightforward test that works
  such as I had been trying to perform.

  result: if such invalid msgstr entries appear through translation, they
  will break the build and will have to be found and fixed.
------------------------------------------------------------
revno: 64
committer: Kyle Nitzsche <kyle.nitzsche@xxxxxxxxxxxxx>
branch nick: ubuntu-developer-manual
timestamp: Thu 2011-01-06 19:06:14 -0500
message:
  improve (fix) code to find invalid unescaped special characters
------------------------------------------------------------