Ain,
oh, some things more:
like: <emph>Clipboard</emph> centered
with whitespaces or whatever, a lot of such strings in options module.
one more: <emph>Pasting into another </emph>
<emph>document</emph> :here is the end
Is this really necessary?
Whitespace and linebreak handling of content is a royal pain
in both cvs/svn and apparently the localization process. Positioning
and number of whitespaces should be irrelevant to the content and
should not show up as localization relevant change. The same is true
for line breaks.
On Sat, Feb 7, 2009 at 20:08, Ain Vagula <avag...@gmail.com> wrote:
- in last commits shortcuts that previously were metakey+key are
changed to metakey-key. why? it is again one PITA for translators. I
cannot see any systematical behaviour here because 90% of help uses +
and now 10% uses -.
- please keep whitespaces (and any other separators) out of the tags.
do not write <tag>whatever </tag>, write <tag>whatever</tag>, in
This is most often due to OOo placing the styles falsely.
different languages word sequence changes and in many cases tag goes
to the end of the sentence or before comma. so translator has to
remove whitespaces, because whitespace before period or comma is
really ugly.
Your comments and complaints are all valid. I suggest that
we try to include a normalizing process for help files before they
get committed. That normalization process would ensure
that linebreaks and whitespaces are placed in a standardized
fashion. It could also automatically turn "<tag>word </tag>"
into "<tag>word</tag> ".
Any suggestion how we could implement this?
Frank
--
Frank Peters
Documentation Project Co-Lead
The OOo Documentation Project:
SIGN UP - PARTICIPATE - CONTRIBUTE
IT'S FREE! NO OBLIGATIONS!
http://documentation.openoffice.org
http://wiki.services.openoffice.org/wiki/Documentation
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@documentation.openoffice.org
For additional commands, e-mail: dev-h...@documentation.openoffice.org
