Mathias,
We have multiple options to avoid this in future:
1) introduce a normalization step that is triggered
when the helpcontent is built and that makes sure that
the content follows certain formatting rules
Building a source shouldn't modify it.
But perhaps it's enough to stop the build in case superfluous blanks
have been found and ask to apply a tool to the sources in question.
Then rather make a normalization step mandatory before building,
which would make it a manual process again. Waiting for the build
to break would slow down the process.
That's why I would actually like to have it automated.
2) introduce and use a status flag that marks content
as to be (re)localized and has to be set explicitly
Manual steps will fail sooner or later.
Yep. I agree.
3) introduce a filter on pootle that ensures that
insignificant changes are not reported
Perhaps a precommit hook in Mercurial can help?
We're not (yet) using hg, so I don't know what a precommit
hook would be. I trust it's something spiky and useful :-)
The best option would probably be 1). But this would mean
that when introducing the normalization step, all content
had to be normalized once initially which would bring
l10n relevant changes.
If you want to keep the white spaces in the existing code base, you
could check the diffs instead of the source: a valid diff should be
identical with a diff ignoring white space changes.
True, but in some places, whitespace are significant.
I would like to clean up to get rid of all existing
insignificant whitespaces and line breaks, or rather,
bring them into a (to be) defined state using a rule set.
The most insiginificant spaces are directly after an
opening element tag, and before a closing element tag
which may be introduced by "beautifying" editors that change
<paragraph>Bla bla <emph>blu blu</emph> foo bar.</paragraph>
into
<paragraph>Bla bla
<emph>blu blu</emph> foo bar.
</paragraph>
Frank
--
Frank Peters x66757
Learning and Publications Manager
SLS - CCLS Application Services
Office Productivity & Communication Suite
Sun Microsystems, Hamburg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
