Cleanup: Grammar: Fix uses of "for e.g."

e.g. stands for "exempli gratia" in Latin which means "for example".
The best way to make sure it makes sense when writing is to just expand
it to "for example". In these cases where the text was "for e.g.", that
leaves us with "for for example" which makes no sense. This commit fixes
all 110 cases, mostly just just replacing the words with "for example",
but also restructuring the text a bit more in a few cases, mostly by
moving "e.g." to the beginning of a list in parentheses.

Pull Request: https://projects.blender.org/blender/blender/pulls/139596
This commit is contained in:
Hans Goudey
2025-05-29 21:21:18 +02:00
committed by Hans Goudey
parent 5747f839e8
commit 91803e130f
74 changed files with 116 additions and 114 deletions

View File

@@ -110,7 +110,7 @@ bool BPY_run_string_eval(bContext *C, const char *imports[], const char *expr);
* print errors to the `stdout` and clear.
*/
struct BPy_RunErrInfo {
/** Brief text, single line (can show this in status bar for e.g.). */
/** Brief text, single line (can show this in status bar for example). */
bool use_single_line_error;
/** Report with optional prefix (when non-NULL). */

View File

@@ -39,7 +39,7 @@ PyObject *PyC_ExceptionBuffer() ATTR_WARN_UNUSED_RESULT ATTR_RETURNS_NONNULL;
/**
* A version of #PyC_ExceptionBuffer that returns the last exception only.
*
* Useful for error messages from evaluating numeric expressions for e.g.
* Useful for error messages from evaluating numeric expressions for example
* where a full multi-line stack-trace isn't needed and doesn't format well in the status-bar.
*/
PyObject *PyC_ExceptionBuffer_Simple() ATTR_WARN_UNUSED_RESULT ATTR_RETURNS_NONNULL;

View File

@@ -33,7 +33,7 @@ static PyObject *bpy_atexit(PyObject * /*self*/, PyObject * /*args*/, PyObject *
bContext *C = BPY_context_get();
/* As Python requested the exit, it handles shutting itself down. */
const bool do_python_exit = false;
/* User actions such as saving the session, preferences, recent-files for e.g.
/* User actions such as saving the session, preferences, and recent-files
* should be skipped because an explicit call to exit is more likely to be used as part of
* automated processes shouldn't impact the users session in the future. */
const bool do_user_exit_actions = false;

View File

@@ -187,7 +187,7 @@ static bool bpy_rna_context_temp_override_enter_ok_or_error(const BPyContextTemp
* Simple, no sanity checks needed.
*
* - 2) Some members are overridden.
* Check the state is consistent (that the region is part the area or screen for e.g.).
* Check the state is consistent (that the region is part the area or screen for example).
*
* - 3) Some members are overridden *but* the context members are unchanged.
* This is a less obvious case which often happens when a Python script copies the context
@@ -201,7 +201,7 @@ static bool bpy_rna_context_temp_override_enter_ok_or_error(const BPyContextTemp
*
* When error-checking unchanged context members some error checks must be skipped
* such as the check to disallow temporary screens since that could break using
* `temp_override(..)` running with the current context from a render-window for e.g.
* `temp_override(..)` running with the current context from a render-window for example.
*
* In fact all sanity checks could be disabled when the members involved remain unchanged
* however it's possible Python scripts corrupt Blender's internal windowing state so keeping
@@ -327,7 +327,7 @@ static PyObject *bpy_rna_context_temp_override_enter(BPyContextTempOverride *sel
}
/* NOTE: always set these members, even when they are equal to the current values because
* setting the window (for e.g.) clears the area & region, setting the area clears the region.
* setting the window (for example) clears the area & region, setting the area clears the region.
* While it would be useful in some cases to leave the context as-is when setting members
* to their current values.
*