-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir,
I had the same problem when I installed the new toolkit alongside the old
one in my home directory as per Pavel's blog. I solved it by installing the
new toolkit over the old one using the installation method described on the
translate web
Hello Ossama,
Ossama Khayat wrote:
[...]
The message states:
As the integration cause a lot of work do not provide sdf files that
cover less then 80 % ( UI only ) translation done. Also please add the
en-US translation to your sdf file.
But in the last reply I got from Charles-H.Schulz, he
2006/1/6, Vladimir Stefanov [EMAIL PROTECTED]:
dwb wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir,
I had the same problem when I installed the new toolkit alongside the old
one in my home directory as per Pavel's blog. I solved it by installing the
new toolkit over
dwb wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir,
I had the same problem when I installed the new toolkit alongside the old
one in my home directory as per Pavel's blog. I solved it by installing the
new toolkit over the old one using the installation method described on the
Eike Rathke írta:
I wonder how this fits. New features can possibly introduce new UI
strings. Why is the deadline for submitting translations before the
deadline for new features? Also, currently there are about 10 CWSs
targeted to 2.0.2 not integrated yet that have the UI/Translation flag
Ain Vagula wrote:
I wrote yesterday that sdf file must be generated with new toolkit
that does not create your language rows (with english strings) for
untranslated strings in sdf.
You should create sdf file from po files you had before merging m148
or m147-update.
ain
OK, I gone back
