Page MenuHomeFreeBSD

Improve wording in Contributing article
ClosedPublic

Authored by sevan on Aug 18 2017, 9:20 PM.
Tags
None
Referenced Files
Unknown Object (File)
Nov 22 2024, 6:00 AM
Unknown Object (File)
Nov 7 2024, 12:30 PM
Unknown Object (File)
Oct 31 2024, 9:58 PM
Unknown Object (File)
Oct 12 2024, 9:45 PM
Unknown Object (File)
Oct 12 2024, 9:45 PM
Unknown Object (File)
Oct 12 2024, 9:44 PM
Unknown Object (File)
Oct 12 2024, 9:44 PM
Unknown Object (File)
Oct 12 2024, 9:44 PM
Subscribers
None

Details

Reviewers
bcr
Commits
rD51488: Improve wording.
Summary

Bug 212992
duncam2@rpi.edu

Diff Detail

Repository
rD FreeBSD doc repository - subversion
Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 11173
Build 11554: arc lint + arc unit

Event Timeline

Can you check the change with textproc/igor? I'm not sure about the tabs at the beginning of some of the lines that were changed.

en_US.ISO8859-1/articles/contributing/article.xml
94–95

I think there is a line break necessary here, it flows over the line too much.

Add line break and rewrap.

A style nit.

en_US.ISO8859-1/articles/contributing/article.xml
97

This xlink needs to be indented and all other lines after it until the closing </link>.

More info on proper link indentation. You're getting there...

en_US.ISO8859-1/articles/contributing/article.xml
474

You can also break overlong lines (where links are definitely too long for the current line like this:

visit the Foundation <link
 xlink:href="https://www.freebsdfoundation.org">web
 site</link>

Basic rule: if you are within an overlong tag (like the link above), then you need to further indent the line until the closing (</link>) tag. Then, the current level of indentation is used like before the opening (<link>) tag. Check the examples at the bottom of this page: https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/docbook-markup-links.html

This revision is now accepted and ready to land.Mar 16 2018, 7:46 PM
en_US.ISO8859-1/articles/contributing/article.xml
474

like so?

477

This address is no longer valid and bounces. Do you have any recommendation on what it should be changed to?

This revision was automatically updated to reflect the committed changes.