Bug 745370

Summary: <xref linkend=*/> does not show correct Japanese character in PDF
Product: [Community] Publican Reporter: Noriko Mizumoto <noriko>
Component: publicanAssignee: PnT DevOps Devs <hss-ied-bugs>
Status: CLOSED DUPLICATE QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.8CC: rglasz, rlandman+disabled, rlandman
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-29 23:50:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Noriko Mizumoto 2011-10-12 06:54:23 UTC
Version: publican-2.8-1.el6eng.x86_64

<xref linkend=*/> is appeared with small boxes instead of correct Japanese characters. This occurs only in PDF rendering, HTML shows correctly.

Here is example pdf can be found at;
http://docs.redhat.com/docs/ja-JP/Red_Hat_Enterprise_Virtualization_for_Servers/2.2/html/Installation_Guide/index.pdf

Chapter2/System Requirement/2nd para/English version:
"It is assumed that the requirements for your specific implementation of the Red Hat Enterprise Virtualization system have been defined by your solution architect. Therefore, the solution planning stage is not covered by this document. However, be aware that the following must be considered when designing the system: total number of virtual machines to be used, storage requirements, network capacity, total CPU and memory requirements. Additional notes regarding system planning are provided in Appendix A, Planning the System Architecture. "

In Japanese version, the link of 'Appendix A, Planning the System Architecture' shows little boxes.

Comment 2 Ruediger Landmann 2013-07-29 23:50:04 UTC
This was a problem in Publican itself, not the Red Hat brand; fixed now.

*** This bug has been marked as a duplicate of bug 628786 ***