Bug 9520 - Markup problems in Xmark.1x
Summary: Markup problems in Xmark.1x
Alias: None
Product: Xtests
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Stuart Anderson
QA Contact:
Depends on:
Reported: 2007-01-02 10:07 UTC by Eric S. Raymond
Modified: 2007-08-21 13:23 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Eric S. Raymond 2007-01-02 10:07:30 UTC
If you are not the right person or list, tell
me and I will attempt to correct my database.

See http://catb.org/~esr/doclifter/problems.html for details on how and
why these patches were generated.  Feel free to email me with any questions.
Note: These patches do not change the mod date of any manual page.  You
may wish to do that by hand.

Problems with Xmark.1x:

Use of low-level troff hackery to set special indents or breaks can't
be translated. The page will have rendering faults in HTML, and
probably also under third-party man page browsers such as Xman, TkMan,
Rosetta, and the KDE help browser.

--- Xmark.1x-orig	2007-01-02 10:44:55.000000000 -0500
+++ Xmark.1x	2007-01-02 10:45:57.000000000 -0500
@@ -33,15 +33,17 @@
 It is possible to run the GXcopy and GXxor tests separately, as long as they
 are concatenated to the same output file:
 .BI "x11perf -display " display " -v1.3 -rop GXcopy -all > " datafile 
 .BI "x11perf -display " display " -v1.3 -rop GXxor -all >> " datafile 
 .BI "x11perf -display " display " -v1.3 -rop GXxor -all > " datafile 
 .BI "x11perf -display " display " -v1.3 -rop GXcopy -all >> " datafile 
Comment 1 Alan Coopersmith 2007-08-21 13:23:56 UTC
Thanks for the patch - committed to git master:

commit e906fe589a852e9b4af4aac6c72580494139a0b7
Author: Eric S. Raymond <esr@thyrsus.com>
Date:   Tue Jan 2 10:07:00 2007 -0800

    Bug 9520: Markup problems in Xmark.1x
    X.Org Bugzilla #9520 <https://bugs.freedesktop.org/show_bug.cgi?id=9520>

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.