Hi Ivo,
Okay, what do I have to do to repair this file?
/bin/echo -ne \357\273\277 mytmp ; cat sbabrw.src mytmp ; mv
sbabrw.src sbabrw.src.old ; mv mytmp sbabrw.src
Please use echo from /bin and not the shell build-in one.
Okay, and here the solution for MSDEV users:
File|Save
Hi Frank,
Frank Schönheit - Sun Microsystems Germany wrote:
Hi Ivo,
Okay, what do I have to do to repair this file?
/bin/echo -ne \357\273\277 mytmp ; cat sbabrw.src mytmp ; mv
sbabrw.src sbabrw.src.old ; mv mytmp sbabrw.src
this command does not change the encoding ( use recode for
Hi Mathias,
Mathias Bauer wrote:
Ivo Hinkelmann wrote:
Hi Frank,
Frank Schönheit - Sun Microsystems Germany wrote:
Today, the process for new strings involves specifying both the germany
and the english string in the spec document, and writing them into the
.src (done by the developer).
Hi Ivo,
(and no, neither my IDE's editor nor my fallback editor (TextPad)
currently seem to recognize UTF-8 :( )
I don't know what IDE you use. My msdev opens resources files well.
Hmm, I opened dbaccess/source/ui/browser/sbabrw.src from src.m133, and
msdev showed me only garbage instead of
Ivo Hinkelmann wrote:
Hi Frank,
Frank Schönheit - Sun Microsystems Germany wrote:
Today, the process for new strings involves specifying both the germany
and the english string in the spec document, and writing them into the
.src (done by the developer). If the german string is not to be
Hi Mathias,
Usually the german text is the real one because most people creating
the UI specs are native german speakers and we usually need a native
english speaker to create useful english texts.
So IMHO we still need the german strings in the specifications. The only
alternative is to
Hi Frank,
Frank Schönheit - Sun Microsystems Germany wrote:
Hi Ivo,
Today, the process for new strings involves specifying both the germany
and the english string in the spec document, and writing them into the
.src (done by the developer). If the german string is not to be entered
at
Ivo Hinkelmann wrote:
Any objections to treat German as a usual translation language and
remove the German entries complete from all resource files in the future?
This would be great from my point of view
David
-
To
Hi Frank,
On Wed, Oct 19, 2005 at 12:42:47 +0200, Frank Schönheit wrote:
conflicts during cws resync caused by this change. In this case convert
your new / changed strings to UTF8.
Dumb question: how do I do this?
Dull answer: use an editor ;-)
For Vim it is the combination of the
Hi,
the cws encup integrated into the milestone m131 introduce two l10n
related changes:
- The German entries in resource files ( *.src / *_tmpl.hrc ) have been
converted to UTF8, thus there is no more different handling of German
and English US entries like before ( MS1252 vs. UTF8 ). You
10 matches
Mail list logo
