You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: designguide/naming.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ Avoid verbose or inconsistent language in the UI, as it may cause layout issues
17
17
- Use standard numerals (`0, 1, 2,…`) not spelled out ("one, two,…")
18
18
- Keep terminology consistent with existing FreeCAD concepts.
19
19
- Avoid programmer jargon in favor of simpler terminology.
20
-
- For user-facing strings add comments as needed to help provide context for translators `//: Sketcher: Command name for new line`. [More info]([Writing Source Code for Translation | Qt 6.9](https://doc.qt.io/qt-6/i18n-source-translation.html#add-comments-for-translators)).
20
+
- For user-facing strings add comments as needed to help provide context for translators `//: Sketcher: Command name for new line`. [More info in Qt docs](https://doc.qt.io/qt-6/i18n-source-translation.html#add-comments-for-translators).
21
21
- Use **third-person present tense** in tooltips: `Creates`, `Adds`, `Inserts`. Write complete sentences where appropriate.
22
22
- Tooltips should describe the action and required context. E.g., `Adds a new sketch to the active body`, not just "Add sketch".
23
23
- Avoid step-by-step instructions in tooltips. Focus on outcome: `Inserts a dimension for the selected lines`, not "Select one or more lines…".
0 commit comments