Note: For guidelines and instructions pages linked below, log in with user name / password: drupal/drupal.
Task for this issue
Copy edit the following topic:
Title: Glossary
Section: Glossary
File name: glossary.txt
Look for:
- Typographical errors
- Spelling errors
- Grammar and usage errors
- Punctuation problems
- Formatting problems in the output. The User guide output can be found on: https://userguide_new-drupal.dev.devdrupal.org/d8guide/en/index.html (access: drupal / drupal )
Note: On other copy editing issues, we have asked to check for adherence to guidelines, but the Glossary is a special case. So in this case, it's just the above (typos, formatting, etc.). Thanks!
Also, be careful when making a patch or update for this file! The AsciiDoc formatting is very sensitive and a bit strange for the Glossary.
Note that the "single-issue" guidelines in the Editing guidelines page, as well as the entire Writing guidelines page, should have already been enforced. But it is still a good idea to at least check them quickly.
Instructions
See https://userguide_new-drupal.dev.devdrupal.org/guidelines/instructions.h... -- but skip the section on finding a task to do, since you have selected this one.
Checklist for this task
- Is a patch file provided? If only one or a few topics were edited, you can instead attach the updated source file(s).
- Is the edit complete and correct?
- Is the work free from additional edits outside the scope of the provided guidelines or task?
- Is attribution provided? See https://userguide_new-drupal.dev.devdrupal.org/guidelines/guidelines.htm...
| Comment | File | Size | Author |
|---|---|---|---|
| #16 | 2754591-add-some-suggestions-16.patch | 2.64 KB | baluertl |
| #12 | user_guide-glossary-2754591-12.patch | 6.15 KB | jojyja |
| #8 | user_guide-glossary-2754591-8.patch | 5.95 KB | jojyja |
| #3 | copy_edit_glossary_txt-2754591-3.patch | 645 bytes | swarad07 |
Comments
Comment #2
swarad07Comment #3
swarad07Hi jhodgdon ,
I went through the entire file, everything is fine. I just found one small thing, all full form of acronyms are written in italics, except for WYSIWYG. Maybe it is fine the way it is but attaching a patch in case you feel we should change it for consistency.
Comment #4
swarad07Written and edited by https://www.drupal.org/u/swarad07[Swarad Mokal] of http://www.blisstering.com[Blisstering Solutions]
Comment #6
jhodgdonGood catch! The change looks good to me. Thanks for checking that file over!
Committed to the guide, and your attribution has already been added to the "overall copy editing" section at the top of attributions.txt. (If you edit a particular topic's wording, more than a word here and there, we'll also add you to the attributions of that particular topic. For small changes, we're adding people to the "overall guide" section at the top.)
Comment #7
jojyja commentedComment #8
jojyja commentedI looked this topic over again and actually found several things that I thought needed fixing. Here's a patch.
Comment #9
jhodgdonThanks for making another pass at this one @jojyja!
These edits all look excellent, with three exceptions:
This change is not going to work.
In order to link to a glossary topic, you have to figure out the machine name of the entry. This is in square brackets, something like
[[glossary-content-type]]
Please read section 1.2.4 on making cross-links on:
https://userguide_new-drupal.dev.devdrupal.org/guidelines/formatting.html
This is an index entry. We do not want it removed.
This edit is adding an index entry saying "Vocabulary, definition" before the glossary entry for Widget. Should be
(((Widget,definition)))
perhaps?
Comment #10
jojyja commentedHi! Thanks for the feedback! I will work on them.
I'm slightly confused about #2. The line "(((Linux Apache MySQL PHP (LAMP),definition))" appears in the User Guide's front end just after Image style. Glossary.txt has another line "(((LAMP (Linux Apache MySQL PHP),definition)))" defined. So should I be retaining both?
Comment #11
jhodgdonAh, good question.
Hm.
So lines like
are index entries, and they come just before the corresponding glossary entry... OH, I see the problem. That line in the User Guide is missing the ending ) -- we need three ))) in a row, and there are only two at the end of that line.
So, that is how that line should be fixed. Oops! This is why we need someone to carefully copy edit, looking at the output as well as the source text file. :) THANKS!
Comment #12
jojyja commentedI have attached a patch featuring updates based on your feedback.
Comment #13
jhodgdonLooks perfect, thanks! Committed.
Comment #16
baluertlDuring the translation of glossary.txt I came up with the idea of some suggestions. Although a patch is provided, but here's a list for easier review and discussion:
Comment #17
jhodgdonLet's open up a new issue for this please, rather than going back to this old issue?
Comment #18
baluertlAlright, here we go: #2828339: Minor improvements for glossary.txt