Date:  Tue, 04 Dec 2007 15:13:17 +0100
From:  Jes Kasper Klittum <jes (at mark) enavn.com>
Subject:  [coba-e:11358] Re: Translating BlueQuartz problems
To:  coba-e (at mark) bluequartz.org
Message-Id:  <4755607D.1000801 (at mark) enavn.com>
In-Reply-To:  <87024F6F-1A87-4B26-8060-E49735D03FAB (at mark) iweb.dk>
References:  <4753E4A3.5030909 (at mark) enavn.com> <B0A5506A-5392-4E92-9F47-A8ED6075148C (at mark) iweb.dk> <200712040256.17835.bq (at mark) solarspeed.net> <0EDD4757-EBFF-4AED-91EC-170170EC02FD (at mark) iweb.dk> <47554A8D.1010101 (at mark) enavn.com> <87024F6F-1A87-4B26-8060-E49735D03FAB (at mark) iweb.dk>
X-Mail-Count: 11358

Hello blues,

René MÍsted skrev:

> Hi Jes,
> I did make it work (sort of), although æøå isn't working properly. 
> (Netværkstjenester => Netværkstjenester)
> Here's what i did:
> cd to directory containing po-files.
> # for i in $(ls | sed -e 's/.po//g'); do msgfmt $i.po -o 
> /usr/share/locale/da/LC_MESSAGES/base-$i.mo; done
> 
> Notice the base-*.mo
> The english & japanese was named base-*.mo so I thought that must be the 
> proper naming convention.
> 
> You might get error like this:
> msgfmt: cce.po: warning: Charset "CHARSET" is not a portable encoding name.
>                          Message conversion to user's charset might not 
> work.
> 
> What I did was replacing 'CHARSET' with 'iso-8859-1'
> # perl -pi -e 's/CHARSET/iso-8859-1/g' *


I see, why are the .po files supplied by Solarspeed not named f.ex, 
base-user.po ? All of them are named without base-?

-- 
Med venlig hilsen,

Jes Kasper Klittum

enavn ApS [ Administration ]
Ringstedgade 11 A
4700 NëÔtved
-------------
enavn ApS [ Datacenter ]
Århusgade 88
2100 KÃenhavn ŽØ


Tel.: +45 88205000
Fax:  +45 88205010
support (at mark) enavn.dk

	
11358_2.x-vcard (attatchment)(tag is disabled)