Issue 38029 - Mail Merge does not work with Japanese database records
Summary: Mail Merge does not work with Japanese database records
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.1.3
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: h.ilter
QA Contact: issues@sw
URL:
Keywords: needmoreinfo, oooqa
Depends on:
Blocks:
 
Reported: 2004-11-28 21:29 UTC by jrumney
Modified: 2005-02-11 10:50 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description jrumney 2004-11-28 21:29:00 UTC 
I have a postgresql database configured with a native encoding of UTF-8. The
database contains address records in English and Japanese. Other applications
are able to read all records via JDBC, so I know there are no encoding problems
with the data.

I attempted to create a Label Sheet for the addresses, with a JDBC Data Source,
and using "MS PGothic" as the font. Japanese characters are displayed as empty
boxes, as would be expected if the font did not contain those characters. The
number of empty boxes is correct, so I do not expect the problem to be encoding
problems with the upstream Data Source component.
Comment 1 jrumney 2004-11-29 00:21:46 UTC 
Further information. When the labels are printed directly to the printer, the
Japanese text is printed correctly. The bug only shows when printing to a file
and opening the resulting file.
Comment 2 michael.ruess 2004-11-29 10:14:21 UTC 
Reassigned to HI.
Comment 3 lohmaier 2004-11-29 21:14:18 UTC 
Could you please attach one sample of the produced mail-merge?
I think it is a font problem. Font-replacement doesn't work within fields, so
when the field has a western font applied that doesn't contain the japanese
characters, you will see the boxes.
Comment 4 haxwell 2005-02-10 22:23:47 UTC 
There has been no reply from the submitter for the requested details of this
issue over the past 2-3 months. Resolving this issue invalid.

jrumney, if you still notice this issue in a recent build (1.1.4 or higher) of
OOo, please reopen this issue. A step by step listing of what you did to
reproduce it would be very helpful, but is not necessary.
Comment 5 h.ilter 2005-02-11 10:50:20 UTC 
HI->jrumney: Please attach a bugdoc to verofy next time.