Would it also be possible to get a dump of the actual English files?
By aligning the previous translations I was able to get a leverage of
just over 60% (150k total, 96k leveraged) against a set of English
properties files extracted from a RCP build of one of our products.
However this file list does not match what you have in the database and
there may be files in this set that do not really require translation.
mori wrote:
Hi Denis,
The information which you sent me was useful. Our tool is almost ready to
use.
Therefore, for the confirmation, I would like to have some samples.
Already some translation strings are on the server. May I have a dump of
them?
e.g. mysqldump
Regards,
---------+---------+---------+---------+---------+---------+------
Motoki MORI
VALWAY Technology Center
NEC Soft, Ltd.
mori-m@xxxxxxxxxxxxxxxxx
TEL:+81-3-5534-2619 FAX:+81-3-5534-2620
-----Original Message-----
From: mori [mailto:mori-m@xxxxxxxxxxxxxxxxx]
Sent: Thursday, February 07, 2008 12:46 PM
To: 'Babel committers mailing list'
Subject: RE: [babel-dev] Ask information for Japanese language pack
Hello Mr. Denis Roy,
Thanks a lot. I will check it.
Regards,
---------+---------+---------+---------+---------+---------+------
Motoki MORI
VALWAY Technology Center
NEC Soft, Ltd.
mori-m@xxxxxxxxxxxxxxxxx
TEL:+81-3-5534-2619 FAX:+81-3-5534-2620
-----Original Message-----
From: babel-dev-bounces@xxxxxxxxxxx
[mailto:babel-dev-bounces@xxxxxxxxxxx] On Behalf Of
Denis Roy
Sent: Wednesday, February 06, 2008 1:58 AM
To: Babel committers mailing list
Subject: Re: [babel-dev] Ask information for Japanese language pack
Hi Motoki MORI,
You can find the current Babel database structure here:
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.babel/server/babel-setu
p.sql?root=Tech
nology_Project&revision=1.13&content-type=text%2Fplain
We use SuSE Linux and MySQL 5.0.18
For 3.3.1 translations , you will need to know specific information from
the files and strings tables. The 3.3.1 .properties files have not been
imported in the server yet, so I can not provide this information
immediately.
- Each .properties file corresponds to one row in the 'files' table.
- Each entry in the .properties file corresponds to one row in the
'strings' table.
- Each string can be translated by adding a row in the 'translations'
table. For instance,
| translation_id | string_id | language_id | version | value
| 3614 | 903 | 2 | 1 |
&Sauvegarder
string_id 903 =
| string_id | file_id | name | value
| 903 | 27 | action.save.label | &Save
file_id 27 =
eclipse | 3.4 |
org.eclipse.compare/compare/org/eclipse/compare/contentmergeviewer/TextMerge
ViewerRe
sources.properties
Once all the files and strings for Eclipse 3.3.1 have been imported, I
will provide you with all the file_id and string_id values you need for
the translations. Importing your Japanese translations could be as
simple as giving me a file containing SQL 'INSERT INTO translations'
commands.
Would this work?
Denis
mori wrote:
Hello, Chris,
This is Motoki MORI again.
We (Eclipse Japan Working Group) want to have the Japanese language
packs 3.3 at the end of March.
.
For that purpose, we discussed the procedure in the attached file.
We would like to register our Japanese messages on the server and
review
and edit them.
In order to develop the registration tool 2) by ourselves, we need
some
information.
Information about BABEL server DB
- OS
- DB Application and version
- Table structure
And we would like ask your help to execute the tool on the server.
At last, we hope that Japanese Language pack will be available on the
Eclipse’s site at the end of March.
Regards,
---------+---------+---------+---------+---------+---------+------
Motoki MORI
VALWAY Technology Center
NEC Soft, Ltd.
mori-m@xxxxxxxxxxxxxxxxx
TEL:+81-3-5534-2619 FAX:+81-3-5534-2620
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the
individual
or entity named in this message. If you are not the intended
recipient,
and have received this message in error, please immediately return
this
by email and then delete it.
------------------------------------------------------------------------
_______________________________________________
babel-dev mailing list
babel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-dev
_______________________________________________
babel-dev mailing list
babel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-dev
_______________________________________________
babel-dev mailing list
babel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-dev
|
