Issue 102777

Summary: HSQLDB messages are not localized
Product: Base Reporter: mori_goodday <morikawa>
Component: codeAssignee: AOO issues mailing list <issues>
Status: ACCEPTED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: foral, issues, ivo.hinkelmann, shinji.enoki
Version: OOo 3.1 RC2   
Target Milestone: ---   
Hardware: Unknown   
OS: Linux, all   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Issue Depends on: 100845    
Issue Blocks:    
Description Flags
sample of message
snap shot of message
hsqldb java properties files for translation none

Description mori_goodday 2009-06-15 07:53:05 UTC
The message when the cursor is moved to the next record without inputting  a
primary key, the message is not understood easily (The example: SET é …ç›®å=?).
we usually use "Index or primary key cannot contain a Null value." in Japanese"
インデックスã¾ãŸã¯ä¸»ã‚­ãƒ¼ã«ã¯ã€Null 値を使用ã§ãã¾ã›ã‚“。 "
Comment 1 mori_goodday 2009-06-15 07:54:04 UTC
Created attachment 62991 [details]
sample of message
Comment 2 maho.nakata 2009-07-14 05:58:51 UTC
reassign per request
Comment 3 mori_goodday 2009-07-14 06:10:32 UTC
OS:  Debian GNU/Linux
Version: 5.0.1 Package:OOo_3.1.0rc2_20090427_Linuxintel_install_ja_deb.tar.gz
Application : Base
100% reproducible

I get error message when i did not put any value in primary key column.
the error message is not translated.
I think it's better to show the message in Japanese.
For Example,"インデックスã¾ãŸã¯ä¸»ã‚­ãƒ¼ã«ã¯ã€Null 値ã¯å…¥åŠ›ã§ãã¾ã›ã‚“。" .
Please see attached file issue102777.JPG 

How to see this message:
1.Create a table with a primary key.
2.Insert one record into the table without puttingany value in primary key column.
3.Move cursor to the next record without inputting  a primary key.
4.The message is showed.
Comment 4 mori_goodday 2009-07-14 06:13:18 UTC
Created attachment 63531 [details]
snap shot  of message
Comment 5 naoyuki 2009-07-16 06:25:26 UTC
This message comes from HSQLDB database engine.
That means we need to localize external project HSQLDB to fix this problem.

Proposed process:
1. put the attached hsqldb java properties files (hsqldb_props.tar.bz2) into Pootle
2. announce dev@l10n list to translate 
3. nl communities translate them
4. contribute them to hsqldb community
5. make patch for OOo build if hsqldb community integration plan does not meed
OOo schedule

Step 1 depends on 100845
Comment 6 naoyuki 2009-07-16 06:28:52 UTC
Created attachment 63578 [details]
hsqldb java properties files for translation