aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJonas Smedegaard <dr@jones.dk>2025-05-26 23:17:32 +0200
committerJonas Smedegaard <dr@jones.dk>2025-05-26 23:17:32 +0200
commit4b8ad9eedc5f2d4e14421902b96df6af4507575d (patch)
treee39cfd098b790f477629cf630236d8bb091ea162
parent7fc64b971a044afbb6d882c04cbc4b50f37bd051 (diff)
replace e.g. -> for example
-rw-r--r--_pandoc.qmd8
1 files changed, 4 insertions, 4 deletions
diff --git a/_pandoc.qmd b/_pandoc.qmd
index 44d701b..8a349fa 100644
--- a/_pandoc.qmd
+++ b/_pandoc.qmd
@@ -125,10 +125,10 @@ in the link target of all link elements.
Since the full AST is available,
the filter API can also be used to reorganise content,
-e.g. to redefine plain text as belonging to a link,
+for example, to redefine plain text as belonging to a link,
or vice versa,
but if content is "put into the wrong boxes"
-(for example if parsed wrongly as is done in this project),
+(for example, if parsed wrongly as is done in this project),
then the organisation of the AST
can become more of an obstacle than an optimization.
@@ -167,7 +167,7 @@ that says to include surname and year in the first text,
omit the second text,
and sort the entry in the third text by surname --
and contains hundreds of other details,
-for example on how to abbreviate a citation with 16 authors,
+for example, on how to abbreviate a citation with 16 authors,
or an entry without an author listed.
Ideally, citations can be separated
@@ -175,7 +175,7 @@ into prose (annotation), structure (bibliographic metadata)
and layout concerns (composition),
with each concern anchored at one place in the workflow.
In reality, however, automated composition sometimes fail short --
-e.g. the style chosen from Citation Style Language
+for example, the style chosen from Citation Style Language
is missing translation of some terms in your (natural) language.
The author may then need to violate the separation of concerns
(until the underlying issue is properly solved),