Release highlights and change log review for 2022.1#13479
Conversation
Qchristensen
left a comment
There was a problem hiding this comment.
All looks good, great work!
| - ``NVDA+Shift+Numpad Delete`` reports the location of the review cursor. (#13060) | ||
| - Added default bindings for toggling modifier keys to Freedom Scientific displays (#13152) | ||
| - 'Baseline' is no longer reported via the report text formatting command (NVDA+F). (#11815) | ||
| - "Baseline" is no longer reported via the report text formatting command (``NVDA+f``). (#11815) |
There was a problem hiding this comment.
NVDA+F shortcut styling has been modified here:
- Code styling (fixed width) is used (adding double backquotes around the expression)
- The F has been switched from uppercase to lowercase.
Is it general styling recommendations to write documentation? Or is it just a matter of personal preference?
I have no strong reason to advocate for one styling or the other, but it's just to know if I need to change something in the future when writing documentation.
Thanks.
There was a problem hiding this comment.
Code styling (fixed width) is used (adding double backquotes around the expression)
I think we are trying to do this consistently now.
If this formatting is missing from other entries for this release and future releases, we should try to update them.
I don't know if this convention has been documented anywhere - they are a bit of a developing standard.
The F has been switched from uppercase to lowercase.
When documenting keyboard commands, "f" is the key name by convention, "F" tends to imply "shift+f".
This comment was marked as resolved.
This comment was marked as resolved.
|
I've reviewed the changes.html file generated, and everything looks good. I have one remaining issue with the changelog: Should the "arrow" If this isn't an issue, can this be merged in to beta? |
Yes, some other ways to address this would be:
|
I'm going to use this option |
|
Hi, a suggestion: in the beginning of the changes for devs section in 2022.1, there appears to be a grammatical error – “a add-on” -> “ an add-on”. Thanks.
|
|
@josephsl 2022.1 was released a long time ago. We do not update the change log section of previous releases. |
Add release highlights for the 2022.1 release.
(squash merge)