moz2po inserts unneeded spaces about translate

[davidfraser]

\ Bug #80 has been marked as a duplicate of this bug. *

[davidfraser]

Hmmm, not sure what the best thing to do here is, so will look at this later.
Thanks for reporting.

[dwaynebailey]

Created [attachment 35](http://bugs.locamotion.org/attachment.cgi?id=35)

Mozilla DTD with spaces

This is a cut down version of update.dtd from Mozilla Firefox 1.5. It contains
only pretty printed entries that have uneeded spaces, everything else has been
deleted.

[dwaynebailey]

There is also a second problem. Items that are converted seem to be using CRLF
within the entity so when we transfer this to PO we have ^M characters carried
over. These should be removed.

I haven’t created a seperate bug report as this can probably be fixed with the
same effort to fix the preceding spaces.

[dwaynebailey]

Created a test and patch. Committed to CVS. This solves the starting
whitespace but not the line endings problem.

[dwaynebailey]

See Bug #79 for the line ending problem.

[dwaynebailey]

That was Bug #86 for the line ending problem!

[dwaynebailey]

This needs some more thinking in terms of the followin:
- spaces at the start of the string (test committed to 0.8 branch)
- how to wrap subsequent strings together (my guess is we convert the newline
and subsequent whitespace into a single whitespace character)

So reopening this bug

[dwaynebailey]

Comitted a fix to CVS with tests. We now do the following:
- Single line elements are left untreated
- Multiline
\* Space at the start of the first line are preserved
\* Whitespace at the start of all subsequent lines is removed
\* All lines except the last have one whitespace character
(ensures that when join lines we don’t join words inadvertantly.)

[dwaynebailey]

Comitted a test to 0.8 branch test_po2dtd.py v 1.7.2.3 to validate merging
translations back into a pretty printed entity