Writer/CJK Justification

Writer Project Please view the guidelines before contributing.
Popular Subcategories: The DPL extension (version 2.3.0) produced a SQL statement which lead to a Database error. The reason may be an internal error of DPL or an error which you made, especially when using DPL options like titleregexp. Query text is: SELECT DISTINCT `page`.page_namespace AS page_namespace,`page`.page_title AS page_title,`page`.page_id AS page_id, rev_user, rev_user_text, rev_comment, rev_timestamp FROM `revision` AS rev, `page` WHERE 1=1 AND `page`.page_namespace IN (14) AND `page`.page_is_redirect=0 AND `page`.page_id=rev.rev_page AND rev.rev_timestamp=( SELECT MAX(rev_aux.rev_timestamp) FROM `revision` AS rev_aux WHERE rev_aux.rev_page=rev.rev_page ) ORDER BY rev_timestamp DESC LIMIT 5 OFFSET 0 Error message is: Unknown column 'rev_user' in 'field list' (127.0.0.1) ... more Subcategories Internal Documentation: The DPL extension (version 2.3.0) produced a SQL statement which lead to a Database error. The reason may be an internal error of DPL or an error which you made, especially when using DPL options like titleregexp. Query text is: SELECT DISTINCT `page`.page_namespace AS page_namespace,`page`.page_title AS page_title,`page`.page_id AS page_id, rev_user, rev_user_text, rev_comment, rev_timestamp FROM `revision` AS rev, `page` WHERE 1=1 AND `page`.page_namespace IN (0) AND `page`.page_is_redirect=0 AND `page`.page_id=rev.rev_page AND rev.rev_timestamp=( SELECT MAX(rev_aux.rev_timestamp) FROM `revision` AS rev_aux WHERE rev_aux.rev_page=rev.rev_page ) ORDER BY rev_timestamp DESC LIMIT 5 OFFSET 0 Error message is: Unknown column 'rev_user' in 'field list' (127.0.0.1) ... more Internal Documentation API Documentation: Writer API articles Development Guide about Writer API Project Website Ongoing Efforts: The DPL extension (version 2.3.0) produced a SQL statement which lead to a Database error. The reason may be an internal error of DPL or an error which you made, especially when using DPL options like titleregexp. Query text is: SELECT DISTINCT `page`.page_namespace AS page_namespace,`page`.page_title AS page_title,`page`.page_id AS page_id, rev_user, rev_user_text, rev_comment, rev_timestamp FROM `revision` AS rev, `page` WHERE 1=1 AND `page`.page_namespace IN (0) AND `page`.page_is_redirect=0 AND `page`.page_id=rev.rev_page AND rev.rev_timestamp=( SELECT MAX(rev_aux.rev_timestamp) FROM `revision` AS rev_aux WHERE rev_aux.rev_page=rev.rev_page ) ORDER BY rev_timestamp DESC LIMIT 5 OFFSET 0 Error message is: Unknown column 'rev_user' in 'field list' (127.0.0.1) ... more Writer Efforts Projects on this Wiki: (edit list) Art Project * Application Framework Documentation Education Project * Marketing Project * Native Language Confederation * Product Releases Security Team Universal Network Objects User Experience Project Website Project Writer Project
Sw.OpenOffice.org View or edit this template.

This page is in a DRAFT stage.

Justified Alignment for CJK

The Problem:

Most documents for publications are formatted using “justified alignment”, i.e., the formatting tries to avoid an irregular right border of the text. Currently, this works by distributing the remaining space in a line to the blanks inside this line. However, this procedure does not make sense for languages which do not use blanks the way western languages do. We also have to consider the case of mixed scripts inside a text. Here is a proposal for handling “justified alignment” for CJK languages.

for Japanese text

The remaining space is to be equally distributed to “blanks” and Japanese characters. Note: A blank behind a Japanese character would lead to a double size gap.

for Chinese text

Justified alignment for Chinese to use the same method as Japanese.

for Korean text

The remaining space in a line is to be distributed only to blanks.

Help needed:

Please give feedback if my assumptions are wrong or if you know of some other special cases for other languages.