This is too.

<row>
<entry colname="col1">22020</entry>
<entry colname="col2">Invalid trim string, '<varname><文字列></varname>'. The trim string must be exactly one character or NULL. It cannot be more than one character.</entry>
</row>

this also.
<row>
<entry colname="col1">42878</entry>
<entry colname="col2">The ORDER BY clause of a SELECT UNION statement only supports unqualified column references and column position numbers. Other expressions are not currently supported.</entry>
</row>

<row>
<entry colname="col1">42909</entry>
<entry colname="col2">The CREATE TABLE statement does not include a column list.</entry>
</row>

<row>
<entry colname="col1">42X24</entry>
<entry colname="col2">Column <varname><columnName></varname> is referenced in the HAVING clause but is not in the GROUP BY list.</entry>
</row>

<row>
<entry colname="col1">42X70</entry>
<entry colname="col2">The number of columns in the table column list does not match the number of columns in the underlying query expression in the table definition for '<varname><値gt;</varname>'.</entry>
</row>
<row>
<entry colname="col1">42X71</entry>
<entry colname="col2">Invalid data type '<varname><データ型名></varname>' for column '<varname><列名></varname>'.</entry>
</row>

<row>
<entry colname="col1">42X99</entry>
<entry colname="col2">Parameters are not allowed in a TABLE definition.</entry>
</row>

<row>
<entry colname="col1">42ZA2</entry>
<entry colname="col2">Operand of LIKE predicate with type <varname><type></varname> and collation <varname><value></varname> is not compatable with LIKE pattern operand with type <varname><type></varname> and collation <varname><value></varname>.</entry>
</row>
<row>
<entry colname="col1">42ZA3</entry>
<entry colname="col2">The table will have collation type <varname><type></varname> which is different than the collation of the schema <varname><type></varname> hence this operation is not supported .</entry>
</row>

X0X0E seems to need modification ....

<row>
<entry colname="col1">X0X0E</entry>

• <entry colname="col2">The column position '<varname><columnPosition></varname>' listed in the auto-generated column selection array was not found in the insert table. </entry>
  + <entry colname="col2">Table '<varname><tableName></varname>' does not have an auto-generated column at column position '<varname><columnPosition></varname>'.</entry>
  </row>

X0X0F also needs modification.
<row>
<entry colname="col1">X0X0F</entry>

• <entry colname="col2">Column name '<varname><columnName></varname>' listed in auto-generated column selection array not found in the insert table.</entry>
  + <entry colname="col2">Table '<varname><tableName></varname>' does not have an auto-generated column named '<varname><columnName></varname>'.</entry>

XBM03 needs translation.

<row>
<entry colname="col1">XBM03</entry>
<entry colname="col2">Supplied value '<varname><value></varname>' for collation attribute is invalid, expecting UCS_BASIC or TERRITORY_BASED.</entry>
</row>

XCL53 needs translation too.
<row>
<entry colname="col1">XCL53</entry>
<entry colname="col2">Stream is closed</entry>
</row>

XIE0N,XIE0P,XIE0Q,XIE0R needs translation.

<row>
<entry colname="col1">XIE0N</entry>
<entry colname="col2">An invalid hexadecimal string '<varname><hexString></varname>' detected in the import file.</entry>
</row>
<row>
<entry colname="col1">XIE0P</entry>
<entry colname="col2">Lob data file <varname><fileName></varname> referenced in the import file not found.</entry>
</row>
<row>
<entry colname="col1">XIE0Q</entry>
<entry colname="col2">Lob data file name cannot be null. </entry>
</row>
<row>
<entry colname="col1">XIE0R</entry>
<entry colname="col2">Import error on line <varname><lineNumber></varname> of file <varname><fileName></varname>: <varname><details></varname> </entry>
</row>

XJ045 needs modification.

<row>
<entry colname="col1">XJ045</entry>

• <entry colname="col2">Invalid or (currently) unsupported isolation level, '<varname><levelName></varname>', passed to Connection.setTransactionIsolationLevel(). The currently supported values are java.sql.Connection.TRANSACTION_SERIALIZABLE, java.sql.Connection.TRANSACTION_REPEATABLE_READ, java.sql.Connection.TRANSACTION_READ_COMMITTED, and java.sql.Connection.TRANSACTION_READ_UNCOMMITTED.</entry>
  + <entry colname="col2">Invalid or (currently) unsupported isolation level, '<varname><levelName></varname>', passed to Connection.setTransactionIsolation(). The currently supported values are java.sql.Connection.TRANSACTION_SERIALIZABLE, java.sql.Connection.TRANSACTION_REPEATABLE_READ, java.sql.Connection.TRANSACTION_READ_COMMITTED, and java.sql.Connection.TRANSACTION_READ_UNCOMMITTED.</entry>
  </row>

<row>
<entry colname="col1">XJ087</entry>
<entry colname="col2">Sum of position('<varname><位置></varname>') and length('<varname><長さ></varname>') is greater than the size of the LOB.</entry>
</row>

XJ215 needs modification.

<row>
<entry colname="col1">XJ215</entry>

• <entry colname="col2">You cannot invoke other java.sql.Clob/java.sql.Blob methods after calling the free() method.</entry>
  + <entry colname="col2">You cannot invoke other java.sql.Clob/java.sql.Blob methods after calling the free() method or after the Blob/Clob's transaction has been committed or rolled back.</entry>
  </row>

XJ216 and XJ217 needs translation.

<row>
<entry colname="col1">XJ216</entry>
<entry colname="col2">The length of this BLOB/CLOB is not available yet. When a BLOB or CLOB is accessed as a stream, the length is not available until the entire stream has been processed.</entry>
</row>
<row>
<entry colname="col1">XJ217</entry>
<entry colname="col2">The locator that was supplied for this LOB/BLOB is invalid</entry>
</row>

XK000 needs translation.

<row>
<entry colname="col1">XK000</entry>
<entry colname="col2">The security policy could not be reloaded: <varname><reason></varname></entry>
</row>

Not several but many ...

Triaged for 10.5.2. Set Urgency to Normal we should check after the 10.5 translations come in if this is still an issue.

I've verified that all the messages mentioned in this issue are present in derby/loc/messages_ja_JP.properties on trunk. It looks like they were added when the 10.3 messages were translated in DERBY-3375. Closing as duplicate.