[publican-list] [Bug 571633] Publican delete the new lines on the screen Tags when creating POTs

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=571633

Douglas Silas <dhensley at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dhensley at redhat.com

--- Comment #10 from Douglas Silas <dhensley at redhat.com> 2010-04-08 15:01:51 EDT ---
I agree with the spirit of the change in comment 1. However, this change is
causing problems with the Deployment Guide. 

There are a lot of instances where <screen> is used inside <para>, and I am
fixing them (so that I can run update_pot). But because of para's complex
content model, it can be very difficult to see where this occurs.

For example, I have the following nested tags in the LDAP chapter: a <screen>
(with several <para> siblings, which are not the problem, but complicate seeing
it) inside a <listitem> inside an <itemizedlist> inside a <para>. (Don't ask me
why someone did that...).

Also, these same instances will exist in all 5.x branches of the DG, making
them all, AFAIK, unable to update their POT files.

Publican tells me which file the nesting problem occurs in, but doesn't provide
any information about where it occurred. Would it be possible to output either
a line number (of the file itself), or the content model that is causing the
problem?

Alternatively, you can find these by doing the following:

install xmlstarlet: yum install xmlstarlet

in the repo: xmlstarlet sel -t -v "//para/screen" my_chapter.xml

If screen is nested directly inside a para, the screen's content will be
output, providing you with a clue of where to look. (xmlstarlet is basically
running an XPATH query on my_chapter.xml.)

For deeper nests such as the one described above, I had to do this:

temp!Deployment_Guide.git/tmp/en-US/xml_tmp *> xmlstarlet sel -t -v
"//para/screen" Lightweight_Directory_Access_Protocol_LDAP.xml 
temp!Deployment_Guide.git/tmp/en-US/xml_tmp *> xmlstarlet sel -t -v
"//para/*/screen" Lightweight_Directory_Access_Protocol_LDAP.xml 
temp!Deployment_Guide.git/tmp/en-US/xml_tmp *> xmlstarlet sel -t -v
"//para/*/*/screen" Lightweight_Directory_Access_Protocol_LDAP.xml 

passwd: files ldap
shadow: files ldap
group: files ldap

...which finally showed the offending screen's content. If this change causes
problems in lots of books, I think that this approach to finding the problems
could be (bash-)scripted. 

Should I reopen this bug/file a new one?

Thanks,

Silas

-- 
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.