[publican-list] [Bug 452792] New: po files whitespace in links breaks builds
bugzilla at redhat.com
bugzilla at redhat.com
Wed Jun 25 05:47:26 UTC 2008
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/show_bug.cgi?id=452792
Summary: po files whitespace in links breaks builds
Product: Red Hat Enterprise Linux 5
Version: 5.2
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: low
Component: publican
AssignedTo: jfearn at redhat.com
ReportedBy: ccurran at redhat.com
QAContact: mhideo at redhat.com
CC: publican-list at redhat.com
Description of problem:
Chester found an issue preventing the Virtualization Guide from building
from the RT3 ticket:
I located the issue that causes this problem: it is suggested "not" to have a
space between = and " signs in a tag. This also applies to " and / signs.
The source was:
<para>To view vcpus using <command>virsh</command> refer to <xref linkend=
"form-Virtualization-Managing_guests_with_virsh-Displaying_virtual_CPU_information"
/> for more information.</para>
and being changed to:
<para>To view vcpus using <command>virsh</command> refer to <xref
linkend="form-Virtualization-Managing_guests_with_virsh-Displaying_virtual_CPU_information"/>
for more information.</para>
After modifying this, the problem is solved. However, why doesn't the spaces in
other files cause problems is still unknown.
Version-Release number of selected component (if applicable):
all probably, I've only tested the latest
How reproducible:
Unknown
Steps to Reproduce:
1. <xref linkend=
"form-Virtualization-Managing_guests_with_virsh-Displaying_virtual_CPU_information"
/> the spacing between braces seems to be the issue
2. po files break
3.
Actual results:
book breaks
Expected results:
book doesn't break
Additional info:
see https://engineering.redhat.com/rt3/Ticket/Display.html?id=23990
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the publican-list
mailing list