Glossary cleanup #45889
Labels
No Label
Meta
Good First Issue
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Eevee & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds, Tests & Devices
Module
Python API
Module
Rendering & Cycles
Module
Sculpt, Paint & Texture
Module
User Interface
Module
VFX & Video
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Information from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-manual#45889
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Many of the definitions in the glossary are phrased inconsistently.
Perhaps a "template" style should be decided on for glossary entries to ensure consistency?
I've split this up into subtasks:
Changed status to: 'Open'
Added subscriber: @gandalf3
Added subscriber: @GregZaal
Added subscriber: @ideasman42
Changed status from 'Open' to: 'Archived'
@gandalf3, re "Many of the definitions in the glossary are phrased inconsistently."
This is too vague, I rather keep tasks here tangible - so its obvious when its resolved and we can close.
Please list which descriptions need edits.
@ideasman42
There doesn't appear to be a standard or any particular style which is adhered to. This doesn't really make any of the writing styles wrong, just different from one another.
I think it would be good to decide on some template/guidelines to follow, then change all of them to match that.
For example, perhaps prepending "it's" or "is" should be discouraged. IMO this is redundant and adds noise right at the start of the definition.
Aside from this, there are also many many specific cases where something is very wrong/inaccurate/otherwise bad. For instance:
Collapse, Subdivision surface: Not sure these really need a glossary entry?
Topology: Duplicate entries, just needs cleanup
Actuator, Boolean, Constraint and many more: Rather awkward and in some cases misleading definitions
Changed status from 'Archived' to: 'Open'
Splitting up into subtasks
Sorry about the email spam, but I've now arranged this task into three tasks and edited the description to reflect this.
@ideasman42 Is this better?
Changed status from 'Open' to: 'Resolved'
As each subtask has now been taken care of, think this is resolved.