Re: Request for ideas how to fix #297074

2007-08-17 Thread Andrei Popescu
On Tue, Aug 14, 2007 at 07:55:36PM +0100, Marcin Owsiany wrote: > The only metadata available seems to be the Content-type field of the > header in the original po file, but I can't see how to enforce it for > the temporary file... I'm not sure if this helps, but when I have to work with ISO-885

Re: Request for ideas how to fix #297074

2007-08-15 Thread Dagfinn Ilmari Mannsåker
Adam Borowski <[EMAIL PROTECTED]> writes: > On Tue, Aug 14, 2007 at 07:55:36PM +0100, Marcin Owsiany wrote: >> 1. use an editor which can auto-detect the file encoding, e.g. vim >> AND >> 2. run poedit on a file which is in encoding A, while your locale is set >> to use encoding B. (where neither

Re: Request for ideas how to fix #297074

2007-08-15 Thread Adam Borowski
On Tue, Aug 14, 2007 at 07:55:36PM +0100, Marcin Owsiany wrote: > First, a short explanation of the use case: > > 1. User runs poedit (aka potooledit) on a partially translated po file. > 2. Poedit retrieves only the untranslated messages from the file (by >filtering it through potool -fnt) an

Re: Request for ideas how to fix #297074

2007-08-14 Thread Peter Samuelson
[Marcin Owsiany] > What happens in step 3 is that vim looks at an ascii-only file (since > msgids are in POSIX locale) and when the user inputs the translation in > her own language, the editor decides to use encoding B (since it's the > locale default). > > Then in step 5 poedit merges the origi