[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sqwebmail
Subject:    Re: [sqwebmail] Re: Sqwebmail roadmap
From:       Marcin Owsiany <porridge () expro ! pl>
Date:       2004-04-22 21:17:23
Message-ID: 20040422211723.GB23499 () mail1 ! expro ! pl
[Download RAW message or body]

On Wed, Apr 21, 2004 at 06:44:13PM -0400, Sam Varshavchik wrote:
> However this means that the translatable strings may span multiple physical 
> lines, and have random arbitrary whitespace in the middle.
> 
> This cannot be handled by gettext directly.

See for example:
http://www.debian.org/doc/user-manuals.en.html#install

The text about CVS access looks like this in the source:

<define-tag inbfdcvs>
  <p><gettext domain="doc">CVS sources working copy: set <code>CVSROOT</code>
  to <kbd>:ext:<var>userid</var>@cvs.debian.org:/cvs/debian-boot</kbd>,
  and check out the <kbd>boot-floppies/documentation</kbd> module.</gettext>
                                                                                      \
  <p><a href="http://cvs.debian.org/boot-floppies/documentation/?cvsroot=debian-boot">
  <gettext domain="doc">CVS via web</gettext></a>
</define-tag>

As you can see <gettext> spans whole first paragraph, which contains the
indenting whitespace. This looks like this in the po file:

msgid ""
"CVS sources working copy: set <code>CVSROOT</code>\n"
"  to <kbd>:ext:<var>userid</var>@cvs.debian.org:/cvs/debian-boot</kbd>,\n"
"  and check out the <kbd>boot-floppies/documentation</kbd> module."

The translators just ignore whitespace.

The only drawback would be that the strings will become 'fuzzied' if someone
changes the indents. Though one could work around that with some
preprocessing...

Marcin
-- 
Marcin Owsiany
porridge@expro.pl


[prev in list] [next in list] [prev in thread] [next in thread]