Page MenuHomeFreeBSD

WINE Section: WINE Management GUIs
Needs ReviewPublic

Authored by acpkendo_gmail.com on Nov 16 2020, 4:43 AM.
This revision needs review, but there are no reviewers specified.

Details

Reviewers
None
Summary

Adding the section describing two advanced GUI applications for managing WINE.

Diff Detail

Repository
rD FreeBSD doc repository - subversion
Lint
Lint Skipped
Unit
Unit Tests Skipped

Event Timeline

acpkendo_gmail.com created this revision.

I like your writeup of this chapter. A few comments inline for style fixes, nothing major.

chapter.xml
20 ↗(On Diff #79588)

See example 9.37 on how to pull up the "<link" part to save a bit of space in that line where the URL is. It's not wrong, just a tip.

32 ↗(On Diff #79588)

There are &lt; and &gt;'s here, which can be replaced by < and >, respectively. Is that your editor doing that? You can do a sweep over the whole document once you're done and do a search & replace for these.

38 ↗(On Diff #79588)

No indentation within <screen> tags, see section 9.5.9 of the FDP primer.

44 ↗(On Diff #79588)

Unindent this section here as well.

187 ↗(On Diff #79588)

s/avaialble/available/

See updated diff for detail.

chapter.xml
44 ↗(On Diff #79588)

The start of this <screen> section is aligned with the start of the <para> section above it (although I have indented the second line to it), is this correct now? It does look like the example in the Primer.

Final clean-up, fixed some indentation, broken brackets around the <application> tags.

A bit more indentation is needed in this file, the text itself is fine.

en_US.ISO8859-1/books/handbook/wine/chapter.xml
105

This line needs to be indented just like in the other <para> above.

109

Same here. You can also install textproc/igor to get warnings about it.

115

This should be on the same level as the tag above (the <para>) and only when it overflows the line, the one below the line with the <screen> on it does *not* need to be indented. Same for <programlisting>s.

148

More indentation isses here.

166

Indent me. :)

168

Here the indentation is OK again.