Xenharmonic Wiki talk:Conventions: Difference between revisions

ArrowHead294 (talk | contribs)
Dunnow
Tag: Manual revert
 
(14 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== [[List model]] ==
{{High priority}}


== List model ==
Can we talk about [[Xenharmonic Wiki:Conventions#Lists]]? Why is it discouraged to use standard Wikitext lists?? Can we have a vote or something? —[[User:Keenan Pepper|Keenan Pepper]] ([[User talk:Keenan Pepper|talk]]) 18:57, 30 September 2018 (UTC)
Can we talk about [[Xenharmonic Wiki:Conventions#Lists]]? Why is it discouraged to use standard Wikitext lists?? Can we have a vote or something? —[[User:Keenan Pepper|Keenan Pepper]] ([[User talk:Keenan Pepper|talk]]) 18:57, 30 September 2018 (UTC)
:[[FREEZE]] used the truly standard list model. We should all trust [[FREEZE]]. [[User:PiotrGrochowski|PiotrGrochowski]] ([[User talk:PiotrGrochowski|talk]]) 19:00, 30 September 2018 (UTC)
:[[FREEZE]] used the truly standard list model. We should all trust [[FREEZE]]. [[User:PiotrGrochowski|PiotrGrochowski]] ([[User talk:PiotrGrochowski|talk]]) 19:00, 30 September 2018 (UTC)
Line 83: Line 84:


:: On readability (I realized this when I tried unifying the style in the page ''Prime EDO''): if you read a larger text block, you'll notice how the capital style break the flow of text and results in worse readability. You know why small capitals are common in novels? It's to avoid capital letters so as to ease reading. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 16:33, 18 July 2021 (UTC)
:: On readability (I realized this when I tried unifying the style in the page ''Prime EDO''): if you read a larger text block, you'll notice how the capital style break the flow of text and results in worse readability. You know why small capitals are common in novels? It's to avoid capital letters so as to ease reading. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 16:33, 18 July 2021 (UTC)
:: I'm starting to think "edo" and "n-edo" represent a good compromise, especially considering [[User:FloraC|FloraC]]'s argument. I'm also thinking of a compromise: presenting "EDO or edo" in that order on the [[EDO]] page to insist on the fact that it's an acronym, but choosing "edo" and "n-edo" as a convention for readability on the Wiki. That might seem contradictory, but it allows one to pass from the full term to the acronym to the anacronym more smoothly, from my point of view. [[User:Fredg999|Fredg999]] ([[User talk:Fredg999|talk]]) 18:10, 19 July 2021 (UTC)
== Math conventions ==
There are currently no real conventions for mathematical notation. Since a lot of math pages involve linear algebra, I propose the following:
: Open up any introductory linear algebra textbook. Follow the notation that is used there.
In practice this means:
* Matrices are uppercase Roman letters: <math>M</math>.
* Vectors (whether column or row) are usually lowercase Roman letters: <math>u</math>.
* When there is potential confusion with scalars, they can be made boldface: <math>\mathbf{u}</math>, or get an arrow: <math>\overrightarrow{u}</math>.
* Inner product can be notated: <math>u^\mathsf{T}v</math> or <math>\left\langle u,v \right\rangle</math>.
* The p-norm is: <math>\| u \|_p</math>, when no p is given, 2-norm is assumed.
* When writing a column vector inside text, just transpose it: <math>w =\begin{bmatrix}
w_1 & w_2 & w_3
\end{bmatrix}^{\mathsf{T}}</math>.
The wiki has Mathjax support, use it!
: EDIT: This also means getting rid of bra-ket notation, by the way. They are used to denote quantum states in complex Hilbert spaces. We are not doing quantum physics here so let's stop pretending.
- [[User:Sintel|Sintel]] ([[User talk:Sintel|talk]]) 20:00, 18 December 2021 (UTC)
== 2 or 3 digits ==
Giving two options for the number of digits isn't really useful if we want consistency... I just changed the [[15edo#Commas]] table's values to 3 digits because I had checked [[17edo#Commas]] and that table used 3 digits, but apparently that one was the exception, not the reverse? Would it make sense to use 3 digits everywhere? Of course it's not urgent, but I'd rather stick to one standard rather than two, so that at least when we're making decisions, they're not arbitrary or random. --[[User:Fredg999|Fredg999]] ([[User talk:Fredg999|talk]]) 02:25, 7 July 2023 (UTC)
: I would be in favour of using 3 digits everywhere. --[[User:BudjarnLambeth|BudjarnLambeth]] ([[User talk:BudjarnLambeth|talk]]) 02:38, 7 July 2023 (UTC)
== Template:` and Template:`s ==
> <nowiki>{{`}}</nowiki> and <nowiki>{{`s}}</nowiki> can be used to additionally prevent the last letter from intersecting the apostrophe or quote.
Is there really a point in this? We're not typesetting newspapers. Plus, <code><nowiki>{{`s}}</nowiki></code> is simply equivalent to <code><nowiki>{{`}}</nowiki>s</code>, no? —[[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 20:50, 26 January 2026 (UTC)
: I made <nowiki>{{`s}}</nowiki> since I thought <nowiki>{{`}}s</nowiki> was a little awkward compared to having them together.
: Also, placing an apostrophe after certain letters, such as f or T, can cause the apostrophe to interfere with the letter. Compare:
:: ''f''{{'s}} (<code><nowiki>''f''{{'s}}</nowiki></code>, no space)
: and
:: ''f''{{`s}} (<code><nowiki>''f''{{`s}}</nowiki></code>, with space)
: I know we're not typesetting newspapers and whatnot, but I think this little tweak is worth it. [[User:ArrowHead294|<math>\overrightarrow{\,\,\scriptsize\text{ArrowHead294}\,\,\,}</math>]] [[User talk:ArrowHead294|(speak to me)]] 00:40, 28 January 2026 (UTC)
:: Yeah, but the <code>s</code> in <code><nowiki>{{`s}}</nowiki></code> is semantically meaningless for the markup language and is part of the content text instead. —[[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 05:25, 28 January 2026 (UTC)
Return to the project page "Conventions".