Re: [poedit-users] Translation Memory interoperability between Linux and Windows 7

> From: V=E1clav Slav=EDk <[email protected]>
> Subject: Re: [poedit-users] Translation Memory interoperability between L=
inux and Windows 7
> To: [email protected]
> Date: Thursday, February 17, 2011, 7:30 PM
> =

> On Feb 17, 2011, at 18:17, Cristian Ciupitu wrote:
> > Can I use a Translation Memory created by
> > poedit-1.4.6.1-2.fc14.x86_64 on Fedora 14 with poedit 1.4.6
> > on Windows 7?
> =

> Yes.

It doesn't work for me, so I've tried to report a bug, but got "Submission =
rejected as potential spam (Maximum number of external links per post excee=
ded)". Here's my bug report:



Description of the problem:
I can not use on Windows 7 a TM (Translation Memory) that was created on Li=
nux.

Versions:
poedit-1.4.6.1-2.fc14.x86_64 on Linux
poedit-1.4.6-setup.exe on Windows

How reproducible:
Every time (with the same TM).

Steps to reproduce:
1. Create TM on Linux.
2. Copy files to Windows.
3. Start poedit on Windows and set the path to the TM.
4. Open a ''*.po'' file.
5. Right click on an entry and select the target language when asked to (''=
ro'' in my specific case).

Actual results:
[http://min.us/mvf4Z5 Database error: Invalid argument]

Expected results:
No errors.

Additional info:
* My TM for ''ro'':
  * [https://sites.google.com/site/cristianciupitu/strings.db?attredirects=
=3D0&d=3D1 strings.db]
  * [https://sites.google.com/site/cristianciupitu/translations.db?attredir=
ects=3D0&d=3D1 translations.db]
  * [https://sites.google.com/site/cristianciupitu/words.db?attredirects=3D=
0&d=3D1 words.db]
* [http://pastebin.com/587ffXmS Poedit settings (taken from the registry)]
* [http://pastebin.com/0ikskjM7 .po file]



Thank you,
Cristian


      =


---------------------------------------------------------------------------=
---
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb