Hi Margaret,
I'll attempt to answer your questions as best I can.
The absolute URL is the concatenation of the above URL with each of the
relative URLs. However, I notice that our site.xml file has not been
regenerated since Feb 22, so this is problematic. I will fix this.
2. Where is the CVS location for the localized properties files? I
looked at http://dev.eclipse.org/viewcvs/index.cgi/ but only found the English properties files and not the
NL directories for the folders that I navigated into.
The localized properties files are not stored in CVS. The strings are
in our MySQL database, which are then exported to the above Update Site
every night.
3. In the SQL dump (babel-database.sql) what is the
"translation_id", how is it generated? Is it unique and will it remain
the same?
The translation_id is simply an auto increment integer value.
Translated strings are kept in history forever, so when someone
provides an updated translation, the current version is markes as
inactive (is_active=0) and the current translation is inserted with
is_active = 1.
4. I noticed on your website that translations are
currently contributed by entering a bug report. Is there a more
automated process for contributing a large amount of translations
or should translated files just be attached to the bug report?
For now, that is the only mechanism to contributing large translation
sets.
I hope this helps,
Denis
Thanks,
Margaret
Morten and the Babel team,
Morten, could I impose on you to enter an Eclipse bugzilla for this new
feature that you are requesting? I'd like to see the feature
generalized to support as many of our corporate members as possible -
those that would step up to do this kind of work, that is :-) The more
detail about the Babel -> Adobe and the Adobe -> Babel you can
spec out in the bugzilla, the better. (There is a "report a bug" link
on http://babel.eclipse.org/babel/
)
In fact, even better would be for your team to grab the latest Babel
server source code (it's in CVS and we would be happy to help you and
your team get set up with it) and then write the web-apis to support
this feature as a patch. That would be best of all because then it
would definitely support your needs and it would ensure that the
feature gets implemented on the schedule you need.
- Bjorn
Morten Nilsen wrote:
Hi
Babel-dev
My name is Morten Nilsen and I manage a group of people in Adobe
Systems Inc which creates a Japanese version of Flex Builder. ...
We’d like to explore how we could automate a process whereby we access
directly your latest file sets for all localizable components (Eclipse
localizable source files .properties) for the next upcoming Eclipse
version. With direct access to the localizable source files, we can set
up our system to automatically retrieve these files, detect the changes
and send these changes out quickly for translation. We would then be
able to submit the completed translation back to the Eclipse source
tree. This could be done on an ongoing basis during the development
process.
_______________________________________________
babel-dev mailing list
babel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-dev
--
Denis Roy
Manager, IT Infrastructure
Eclipse Foundation, Inc. -- http://www.eclipse.org/
Office: 613.224.9461 x224 (Eastern time)
Cell: 819.210.6481
denis.roy@xxxxxxxxxxx
|
