Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | translate error messages raised by HSQLDB backend | ||||||
---|---|---|---|---|---|---|---|
Product: | Base | Reporter: | diaz_frederic <diaz_frederic> | ||||
Component: | code | Assignee: | AOO issues mailing list <issues> | ||||
Status: | CONFIRMED --- | QA Contact: | |||||
Severity: | Trivial | ||||||
Priority: | P3 | CC: | issues | ||||
Version: | OOO300m9 | Keywords: | oooqa | ||||
Target Milestone: | --- | ||||||
Hardware: | PC | ||||||
OS: | All | ||||||
Issue Type: | ENHANCEMENT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
diaz_frederic
2009-01-04 08:36:45 UTC
Created attachment 59123 [details]
Screenshot of the untranslated dialog box
As I can detect: This message isn't coming from OpenOffice.org. It's comming from the underlying database management. @ clu Is there a possibility to make it translatable? I have controlled it with my last KeyID-build. There is no Key for translation. Hi, This is not a wrong translation, the messages are raised from the HSQLDB engine. Franck said it's the pure HSQLDB Java code, where the translated messages come from the UI. I've asked Franck whether the messages could be added to our translation database and he said that it is planed for 3.x branch. Kind regards - Sophie so a make a feature enhancement of it and send it further to the requirements team grabbing fs->ihi: we once talked about this ... we need a possibility to include Java properties files in our translation process, which I think is yours to implement. java properties are supported Reset assigne to the default "issues@openoffice.apache.org". |