Issue 97740 - translate error messages raised by HSQLDB backend
Summary: translate error messages raised by HSQLDB backend
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOO300m9
Hardware: PC All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: oooqa
Depends on:
Reported: 2009-01-04 08:36 UTC by diaz_frederic
Modified: 2017-05-20 10:48 UTC (History)
1 user (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---

Screenshot of the untranslated dialog box (26.95 KB, image/png)
2009-01-04 08:38 UTC, diaz_frederic
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description diaz_frederic 2009-01-04 08:36:45 UTC
Found in 3.0.0 and in 3.0.1.RC1 Base

Create a new table (in French version)
make a primary key conflict, entering
two records with the same primary key

Displayed message isn't localised in french

Comment 1 diaz_frederic 2009-01-04 08:38:54 UTC
Created attachment 59123 [details]
Screenshot of the untranslated dialog box
Comment 2 Mechtilde 2009-01-04 11:55:23 UTC
As I can detect: This message isn't coming from 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.
Comment 3 2009-01-04 15:24:03 UTC

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
Comment 4 christoph.lukasiak 2009-03-25 15:10:16 UTC
so a make a feature enhancement of it and send it further to the requirements team
Comment 5 Frank Schönheit 2009-03-25 20:41:03 UTC
Comment 6 Frank Schönheit 2009-10-07 12:49:06 UTC
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.
Comment 7 ivo.hinkelmann 2011-01-31 17:10:28 UTC
java properties are supported
Comment 8 Marcus 2017-05-20 10:48:14 UTC
Reset assigne to the default "".