Escaping strings in message catalogs?

I was just wondering why is it that message catalog file requires that
values be enclosed in single quotes and other single quotes within them
escaped according to the Smalltalk syntax? Isn't the whole purpose of the
.lbl file to make translator's life easier? Sounds like the indexer could
just read the values until the end of the line, could it not?

Thanks,

-Boris

--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

[hidden email]

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

What if a message has a carriage return embedded in the value?  Then the
indexer would only read part of the value...

Dave

Boris Popov wrote:

Wouldn't it be better to find a way to escape carriage returns?

Steve

From: Dave Stevenson [mailto:[hidden email]]
> What if a message has a carriage return embedded in the value?  Then
the
> indexer would only read part of the value...
>
> Dave
>
> Boris Popov wrote:
> > I was just wondering why is it that message catalog file requires
that
> > values be enclosed in single quotes and other single quotes within
them
> > escaped according to the Smalltalk syntax? Isn't the whole purpose
of
> the
> > .lbl file to make translator's life easier? Sounds like the indexer
> could
> > just read the values until the end of the line, could it not?
> >
> > Thanks,
> >
> > -Boris
> >

IMHO there's no need to deploy message catalogs in source form. Why not
"compile" message catalogs from XML sources at packaging time?

XML can be easily edited with various free tools available everywhere.
XML also perfectly handles international unicode characters and can even
support text formatting, which a message catalog "compiler" could easily
translate to instances of Text.

I just replaced the MessageCatalog thing with something more lean and
efficient (all catalogs loaded into memory upon application startup -
hey, it's only a few kilobytes of strings - there's no need to use
complicated caching and such).

Andre

Good point, but still a tad awkward for people who just want to do the
translation. Something we'll just have to live with for now I guess.

Thanks,

-Boris

--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

[hidden email]

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

-----Original Message-----
From: Dave Stevenson [mailto:[hidden email]]
Sent: Monday, June 12, 2006 9:57 PM
To: Boris Popov
Cc: vwnc
Subject: Re: Escaping strings in message catalogs?

What if a message has a carriage return embedded in the value?  Then the
indexer would only read part of the value...

Dave

Boris Popov wrote:

I'm hungry for more info on that!

-Boris

--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

[hidden email]

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

-----Original Message-----
From: Travis Griggs [mailto:[hidden email]]
Sent: Monday, June 19, 2006 10:23 AM
To: Boris Popov
Cc: vwnc
Subject: Re: Escaping strings in message catalogs?

On Jun 12, 2006, at 16:17, Boris Popov wrote:

> I was just wondering why is it that message catalog file requires that
> values be enclosed in single quotes and other single quotes within  
> them
> escaped according to the Smalltalk syntax? Isn't the whole purpose  
> of the
> .lbl file to make translator's life easier? Sounds like the indexer  
> could
> just read the values until the end of the line, could it not?

If you use ExtraCatalogs... that's not a problem :) Speaking from  
some experience... ExtraCatalog files are a whole heck of a lot  
easier on translators than .lbl files. AND... you don't have to  
compile .idx files. You just drop the files in and go.

--
Travis Griggs
Objologist
My Other Machine runs OSX. But then... so does this one.



-----------------------------------------
DISCLAIMER: This email is bound by the terms and conditions
described at
http://www.key.net/disclaimer.htm