User talk:Xenwolf: Difference between revisions

(19 intermediate revisions by 7 users not shown)

Line 42:

== Diatonic Functions of Xenharmonic Intervals ==

Okay, so one thing I'm interested in is covering the diatonic functions of notes at various intervals' distance away from the tonic- you know, for microtonal composers who still want to work with tonality- I honestly think pages like 3/2 and 4/3 could benefit from having information on things like this. On another note, do we have information on the thirty-five 12edo proper modes? Pages documenting these modes would serve to gather variations and alternative tunings for these scales and modes into one place. For the record, I know that in my own microtonal composing, I tend not to go very far from my 12edo roots for reasons detaild in [[A recovering microtonalist's critical reaction to Why Microtonality]], yet, I also can't help but agree with Mike S in his comments in [[Microtonalists critical reaction to a recovering ~~microtonalists~~ critical reaction to Why ~~Microtonaltiy~~?]] on 7-limit and 11-limit being important- in fact, I would add the 13-limit to his list. --[[User:Aura|Aura]] ([[User talk:Aura|talk]]) 16:11, 5 September 2020 (UTC)

Okay, so one thing I'm interested in is covering the diatonic functions of notes at various intervals' distance away from the tonic- you know, for microtonal composers who still want to work with tonality- I honestly think pages like 3/2 and 4/3 could benefit from having information on things like this. On another note, do we have information on the thirty-five 12edo proper modes? Pages documenting these modes would serve to gather variations and alternative tunings for these scales and modes into one place. For the record, I know that in my own microtonal composing, I tend not to go very far from my 12edo roots for reasons detaild in [[A recovering microtonalist's critical reaction to Why Microtonality]], yet, I also can't help but agree with Mike S in his comments in [[Microtonalists' critical reaction to a recovering microtonalist's critical reaction to Why Microtonality?]] on 7-limit and 11-limit being important- in fact, I would add the 13-limit to his list. --[[User:Aura|Aura]] ([[User talk:Aura|talk]]) 16:11, 5 September 2020 (UTC)

: First, I guess that I'm not the right person to ask about ''diatonic functions of notes''. Second, as far as I know there are no pages about the 35 [[12edo]] modes, but it could as well be that I only missed it/them. Third, I didn't compose anything yet. Currently I mostly help others to put information into the wiki ... I really like listening xen music of any kind, I also like "meditating" on intervals, that's why I uploaded several sound examples, especially those in prime limits above 5. But I also know that timbre is very important. BTW: today I discovered that [[11/7]] has a very convincing sound. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 19:33, 5 September 2020 (UTC)

Line 710:

You might want to check my sandbox and comment on my latest tests. The template ''temperament data'' is something similar to infobox interval and et. The ''collapsed box'' is nothing but a general formatting device. Let me know if either of them makes anything better. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 05:59, 31 January 2021 (UTC)

: The problem occurs whenever pipe chars (<code>~~<nowiki>|</nowiki>~~</code>) are passed to a template. Replacing pipes by <code><nowiki>{{!}}</nowiki></code> each will solve the problem, see following example:

: The problem occurs whenever pipe chars (<code>|</code>) are passed to a template. Replacing pipes by <code><nowiki>{{!}}</nowiki></code> each will solve the problem, see following example:

{{User:FloraC/Collapsed box

Line 944:

I see it fit to categorize temperament redirects cuz they're eventually to be expanded to full articles. For ratios redirecting to interval names, I'm not sure. They're essentially the same concept and will never be distinct articles. So the categories are duplicate, and the maintenance load also doubles. What's your take on this? [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 12:52, 3 April 2022 (UTC)

: I find it generally useful to also make alternative names findable in categories (they are italicized to distinguish them). In the index of a book, there are sometimes short references instead of page numbers (I consider the categorization of redirects to be the wiki equivalent of this). But I'm not sure the categories are useful overall. Personally, I see them more as "fire stairs" to articles. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 18:22, 3 April 2022 (UTC)

== Step ratio terms in other languages ==

Kite has brought up what he sees as a possible issue in hard vs. soft terms ([[Talk:TAMNAMS#Hard_and_soft_in_French.2C_German.2C_etc.|here]]) when translated to European languages. Looking at the [https://en.wikipedia.org/wiki/Key_signature_names_and_translations Wikipedia page] he's linking to, there seems to be no conflict in Romance languages at least, and from my German knowledge there is no conflict between ''hart/weich'' and ''Dur/moll''. There could be other reasons literal translations of hard and soft are unsuitable, though (I don't know what [[de:Diskussion:Schrittverhältnis#Benennung|your comment]] on the German article for step ratio was pointing at). My suggestion would be to create a page for translating TAMNAMS hard and soft terms, specifically, and patiently wait for native speaker input. [[User:Inthar|Inthar]] ([[User talk:Inthar|talk]]) 14:52, 19 August 2022 (UTC)

: Concur. --[[User:Godtone|Godtone]] ([[User talk:Godtone|talk]]) 19:30, 19 August 2022 (UTC)

:: Thanks for letting me know, I replied in [[Talk:TAMNAMS#Hard and soft in French, German, etc.]]. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 20:29, 31 August 2022 (UTC)

== Maintenance bot ==

Hi Xenwolf, I notice that we sometimes do manual cleaning which could be automated by bots, such as fixing double redirects. I stumbled upon this yesterday: https://www.mediawiki.org/wiki/Manual:Pywikibot/redirect.py

Do you think there's a chance it could be installed on this wiki? Unless there's already something similar available that I don't know of yet? --[[User:Fredg999|Fredg999]] ([[User talk:Fredg999|talk]]) 16:11, 8 October 2022 (UTC)

: I don't think anything like this exists yet. The person who takes care of the server side installation is [[User:Tyler Henthorn|Tyler Henthorn]], maybe you can share your ideas with him. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 21:06, 13 October 2022 (UTC)

== In-browser sound generation ==

Hi Xenwolf!

My in-browser sound generation project ([[User:Plumtree/Sound]]) is essentially ready. Could you review [[User:Plumtree/common.js]] and [[User:Plumtree/common.css]] and, if there're no issues, include those globally?

The best option would've been [[mw:Extension:Gadgets]] for JS and [[mw:Extension:TemplateStyles]] for CSS. Alas, they aren't installed. I've asked [[User:Tyler Henthorn]] for them but his last edit was more than a year ago and it's unlikely he'll answer any time soon.

What does JS do?

* It reacts to clicks on HTML elements with class <code>sequence-audio</code>. When one is clicked, it reads its <code>data-sequence</code> attribute and plays the encoded pattern.

* If <code>data-lock</code> attribute is set, it also adds the <code>sequence-audio-playing</code> class and ignores further clicks for the duration of the sequence.

* Timbres defined by their harmonic spectra are supported. Builtins are <code>sine</code>, <code>semisine</code>, <code>flute</code>, <code>violin</code>; you can supply custom ones using <code>data-timbre-X</code> attributes.

* A sequence consists of the following elements, separated by whitespaces:

** <code>wait:DURATION</code> - adds DURATION ms to the global time shift, which starts at 0.

** <code>FREQUENCY:DURATION:GAIN:SHIFT:INSTRUMENT</code> - plays FREQUENCY for DURATION ms with GAIN with timbre specified with INSTRUMENT. It starts at global shift + SHIFT ms, and global shift isn't modified. INSTRUMENT's default is <code>sine</code>; SHIFT's default is <code>0</code>.

* For example, sequences used for interval demonstration look like this: <code>440:1000:0.1 660:1000:0.1:500 wait:2000 660:1000:0.1 440:1000:0.1:500 wait:2000 440:1000:0.1 660:1000:0.1</code>.

* Modern browsers support Web Audio API quite well and I don't expect any compatibility issues.

What does CSS handle?

* Background colour of <code>.sequence-audio-button</code> elements depending on their state.

* Cursor styles upon <code>.sequence-audio-button</code> elements so that they're interpreted as interactive.

* Additionally, <code>.white-key</code> and <code>.black-key</code> elements have the corresponding colours. Those may be used to build interactive keyboards for ETs.

Examples (all require [[User:Plumtree/common.js]] and [[User:Plumtree/common.css]] to be properly viewed):

* [[User:Plumtree/Sound]] - mostly tests of intervals.

* [[User:Plumtree/Sandbox/Interval]] - actually tests of intervals as they're going to be included into [[Template:Infobox Interval]].

* [[User:Plumtree/Audio]] - the template which is currently the main interface for this JS.

[[User:Plumtree|Plumtree]] ([[User talk:Plumtree|talk]]) 17:52, 16 October 2022 (UTC)

== Thank you for reconstructing my diagram on 10648/10647 ==

Thank you, Xenwolf, for reconstructing my diagram on the harmonisma, 10648/10647, and your helpful hint on formatting monospaced text for alignment.

Your reformatting gave me the opportunity to spot and correct my mistakes in the original diagram, which were of course my own responsibility. Thanks to your help, the corrected diagram should hopefully help readers to visualize the relationship between the 10648/10647 and the 352/351 and 364/363. [[User:Mschulter1325|Mschulter1325]] 19:38, 11 November 2022 (UTC)

: You're welcome, it was a pleasure to help. Shouldn't the chart be placed on page [[10648/10647]] itself after the corrections are made? --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 10:03, 12 November 2022 (UTC)

Yes, it's corrected, and I just put some final touches on tidying up the alignment, so it should be ready to go on the article's page. Many thanks for your assistance! [[User:Mschulter1325|Mschulter1325]] 04:20, 15 November 2022 (UTC)

== Add HEJI font to CSS ==

Hi Xenwolf,

I'd like to add a bit of code to [[MediaWiki:Common.css]] so that we can use the HEJI2Text font on the wiki (instead of relying on a bunch of SVG images, namely), but I don't have admin access so I can't do it myself. Do you think you could add it?

/* use HEJI2Text font if class="heji" */

@font-face {

font-family: HEJI2Text;

src: url(https://plainsound.org/fonts/HEJI2Text.otf);

}

.heji {

font-family: HEJI2Text;

}

</nowiki></pre>

--[[User:Fredg999|Fredg999]] ([[User talk:Fredg999|talk]]) 07:49, 3 January 2023 (UTC)

: Hi Fredg999, would you please try the additions needed within [[User:Fredg999/common.css|''your personal common.css'']] and prepare or collect some representative examples (maybe just links to pages)? This would also be a good basis to better understand the impact of this proposal on the site and for discussing individual points with other users. Best regards --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 18:06, 3 January 2023 (UTC)

:: I added a few examples to [[User:Fredg999/Sandbox#HEJI2Text testing area|''my personal Sandbox page'']]. Here is a screenshot of the result: https://drive.google.com/file/d/10ZLax9RYqQg3-mQtV9YeKPC--2VmvR43/view?usp=sharing

:: The main use case I have in mind is the [[Helmholtz-Ellis notation]] page, where we could improve the reference tables and give more examples efficiently using the HEJI font. I was thinking of adding a table that shows all symbols (a bit like the HEJI notation palette on [https://www.plainsound.org/HEJI/ Plainsound's HS CALC]), but also shows the character mapping, so that readers can learn to use the font more easily on the wiki and elsewhere.

:: Most symbols from the [[Alternative symbols for ups and downs notation]] could also be written using the HEJI font, since it provides symbols for each combination of the standard chromatic accidentals with one, two or three up or down arrows.

:: Many other pages about just intonation could benefit from HEJI symbols as well, such as interval tables on various EDO pages (for easy up/down symbols as a complement to their "text" version; e.g. [[22edo#Intervals]]), as well as the [[Overtone scale]] page, where notation would be another representation of the JI scales, alongside the solfege notations already present, for example.

:: --[[User:Fredg999|Fredg999]] ([[User talk:Fredg999|talk]]) 03:49, 4 January 2023 (UTC)

::: I added the font to [[MediaWiki:Common.css]]. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 06:52, 4 January 2023 (UTC)

:::: Thank you! --[[User:Fredg999|Fredg999]] ([[User talk:Fredg999|talk]]) 07:13, 4 January 2023 (UTC)

@@ Line 42: / Line 42: @@
 == Diatonic Functions of Xenharmonic Intervals ==
-Okay, so one thing I'm interested in is covering the diatonic functions of notes at various intervals' distance away from the tonic- you know, for microtonal composers who still want to work with tonality- I honestly think pages like 3/2 and 4/3 could benefit from having information on things like this.  On another note, do we have information on the thirty-five 12edo proper modes?  Pages documenting these modes would serve to gather variations and alternative tunings for these scales and modes into one place.  For the record, I know that in my own microtonal composing, I tend not to go very far from my 12edo roots for reasons detaild in [[A recovering microtonalist's critical reaction to Why Microtonality]], yet, I also can't help but agree with Mike S in his comments in [[Microtonalists critical reaction to a recovering microtonalists critical reaction to Why Microtonaltiy?]] on 7-limit and 11-limit being important- in fact, I would add the 13-limit to his list. --[[User:Aura|Aura]] ([[User talk:Aura|talk]]) 16:11, 5 September 2020 (UTC)
+Okay, so one thing I'm interested in is covering the diatonic functions of notes at various intervals' distance away from the tonic- you know, for microtonal composers who still want to work with tonality- I honestly think pages like 3/2 and 4/3 could benefit from having information on things like this.  On another note, do we have information on the thirty-five 12edo proper modes?  Pages documenting these modes would serve to gather variations and alternative tunings for these scales and modes into one place.  For the record, I know that in my own microtonal composing, I tend not to go very far from my 12edo roots for reasons detaild in [[A recovering microtonalist's critical reaction to Why Microtonality]], yet, I also can't help but agree with Mike S in his comments in [[Microtonalists' critical reaction to a recovering microtonalist's critical reaction to Why Microtonality?]] on 7-limit and 11-limit being important- in fact, I would add the 13-limit to his list. --[[User:Aura|Aura]] ([[User talk:Aura|talk]]) 16:11, 5 September 2020 (UTC)
 : First, I guess that I'm not the right person to ask about ''diatonic functions of notes''. Second, as far as I know there are no pages about the 35 [[12edo]] modes, but it could as well be that I only missed it/them. Third, I didn't compose anything yet. Currently I mostly help others to put information into the wiki ... I really like listening xen music of any kind, I also like "meditating" on intervals, that's why I uploaded several sound examples, especially those in prime limits above 5. But I also know that timbre is very important. BTW: today I discovered that [[11/7]] has a very convincing sound. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 19:33, 5 September 2020 (UTC)
@@ Line 710: / Line 710: @@
 You might want to check my sandbox and comment on my latest tests. The template ''temperament data'' is something similar to infobox interval and et. The ''collapsed box'' is nothing but a general formatting device. Let me know if either of them makes anything better. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 05:59, 31 January 2021 (UTC)
-: The problem occurs whenever pipe chars (<code><nowiki>|</nowiki></code>) are passed to a template. Replacing pipes by <code><nowiki>{{!}}</nowiki></code> each will solve the problem, see following example:
+: The problem occurs whenever pipe chars (<code>&#124;</code>) are passed to a template. Replacing pipes by <code><nowiki>{{!}}</nowiki></code> each will solve the problem, see following example:
 <div style="margin-left: 1.5em; padding: 0 0.5em; border: 1px solid #ddf; background-color: #fafafa">
 {{User:FloraC/Collapsed box
@@ Line 944: / Line 944: @@
 I see it fit to categorize temperament redirects cuz they're eventually to be expanded to full articles. For ratios redirecting to interval names, I'm not sure. They're essentially the same concept and will never be distinct articles. So the categories are duplicate, and the maintenance load also doubles. What's your take on this? [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 12:52, 3 April 2022 (UTC)
+: I find it generally useful to also make alternative names findable in categories (they are italicized to distinguish them). In the index of a book, there are sometimes short references instead of page numbers (I consider the categorization of redirects to be the wiki equivalent of this). But I'm not sure the categories are useful overall. Personally, I see them more as "fire stairs" to articles. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 18:22, 3 April 2022 (UTC)
+== Step ratio terms in other languages ==
+Kite has brought up what he sees as a possible issue in hard vs. soft terms ([[Talk:TAMNAMS#Hard_and_soft_in_French.2C_German.2C_etc.|here]]) when translated to European languages. Looking at the [https://en.wikipedia.org/wiki/Key_signature_names_and_translations Wikipedia page] he's linking to, there seems to be no conflict in Romance languages at least, and from my German knowledge there is no conflict between ''hart/weich'' and ''Dur/moll''. There could be other reasons literal translations of hard and soft are unsuitable, though (I don't know what [[de:Diskussion:Schrittverhältnis#Benennung|your comment]] on the German article for step ratio was pointing at). My suggestion would be to create a page for translating TAMNAMS hard and soft terms, specifically, and patiently wait for native speaker input. [[User:Inthar|Inthar]] ([[User talk:Inthar|talk]]) 14:52, 19 August 2022 (UTC)
+: Concur. --[[User:Godtone|Godtone]] ([[User talk:Godtone|talk]]) 19:30, 19 August 2022 (UTC)
+:: Thanks for letting me know, I replied in [[Talk:TAMNAMS#Hard and soft in French, German, etc.]]. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 20:29, 31 August 2022 (UTC)
+== Maintenance bot ==
+Hi Xenwolf, I notice that we sometimes do manual cleaning which could be automated by bots, such as fixing double redirects. I stumbled upon this yesterday: https://www.mediawiki.org/wiki/Manual:Pywikibot/redirect.py
+Do you think there's a chance it could be installed on this wiki? Unless there's already something similar available that I don't know of yet? --[[User:Fredg999|Fredg999]] ([[User talk:Fredg999|talk]]) 16:11, 8 October 2022 (UTC)
+: I don't think anything like this exists yet. The person who takes care of the server side installation is [[User:Tyler Henthorn|Tyler Henthorn]], maybe you can share your ideas with him. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 21:06, 13 October 2022 (UTC)
+== In-browser sound generation ==
+Hi Xenwolf!
+My in-browser sound generation project ([[User:Plumtree/Sound]]) is essentially ready. Could you review [[User:Plumtree/common.js]] and [[User:Plumtree/common.css]] and, if there're no issues, include those globally?
+The best option would've been [[mw:Extension:Gadgets]] for JS and [[mw:Extension:TemplateStyles]] for CSS. Alas, they aren't installed. I've asked [[User:Tyler Henthorn]] for them but his last edit was more than a year ago and it's unlikely he'll answer any time soon.
+What does JS do?
+* It reacts to clicks on HTML elements with class <code>sequence-audio</code>. When one is clicked, it reads its <code>data-sequence</code> attribute and plays the encoded pattern.
+* If <code>data-lock</code> attribute is set, it also adds the <code>sequence-audio-playing</code> class and ignores further clicks for the duration of the sequence.
+* Timbres defined by their harmonic spectra are supported. Builtins are <code>sine</code>, <code>semisine</code>, <code>flute</code>, <code>violin</code>; you can supply custom ones using <code>data-timbre-X</code> attributes.
+* A sequence consists of the following elements, separated by whitespaces:
+** <code>wait:DURATION</code> - adds DURATION ms to the global time shift, which starts at 0.
+** <code>FREQUENCY:DURATION:GAIN:SHIFT:INSTRUMENT</code> - plays FREQUENCY for DURATION ms with GAIN with timbre specified with INSTRUMENT. It starts at global shift + SHIFT ms, and global shift isn't modified. INSTRUMENT's default is <code>sine</code>; SHIFT's default is <code>0</code>.
+* For example, sequences used for interval demonstration look like this: <code>440:1000:0.1 660:1000:0.1:500 wait:2000 660:1000:0.1 440:1000:0.1:500 wait:2000 440:1000:0.1 660:1000:0.1</code>.
+* Modern browsers support Web Audio API quite well and I don't expect any compatibility issues.
+What does CSS handle?
+* Background colour of <code>.sequence-audio-button</code> elements depending on their state.
+* Cursor styles upon <code>.sequence-audio-button</code> elements so that they're interpreted as interactive.
+* Additionally, <code>.white-key</code> and <code>.black-key</code> elements have the corresponding colours. Those may be used to build interactive keyboards for ETs.
+Examples (all require [[User:Plumtree/common.js]] and [[User:Plumtree/common.css]] to be properly viewed):
+* [[User:Plumtree/Sound]] - mostly tests of intervals.
+* [[User:Plumtree/Sandbox/Interval]] - actually tests of intervals as they're going to be included into [[Template:Infobox Interval]].
+* [[User:Plumtree/Audio]] - the template which is currently the main interface for this JS.
+[[User:Plumtree|Plumtree]] ([[User talk:Plumtree|talk]]) 17:52, 16 October 2022 (UTC)
+== Thank you for reconstructing my diagram on 10648/10647 ==
+Thank you, Xenwolf, for reconstructing my diagram on the harmonisma, 10648/10647, and your helpful hint on formatting monospaced text for alignment.
+Your reformatting gave me the opportunity to spot and correct my mistakes in the original diagram, which were of course my own responsibility. Thanks to your help, the corrected diagram should hopefully help readers to visualize the relationship between the 10648/10647 and the 352/351 and 364/363. [[User:Mschulter1325|Mschulter1325]] 19:38, 11 November 2022 (UTC)
+: You're welcome, it was a pleasure to help. Shouldn't the chart be placed on page [[10648/10647]] itself after the corrections are made? --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 10:03, 12 November 2022 (UTC)
+Yes, it's corrected, and I just put some final touches on tidying up the alignment, so it should be ready to go on the article's page. Many thanks for your assistance! [[User:Mschulter1325|Mschulter1325]] 04:20, 15 November 2022 (UTC)
+== Add HEJI font to CSS ==
+Hi Xenwolf,
+I'd like to add a bit of code to [[MediaWiki:Common.css]] so that we can use the HEJI2Text font on the wiki (instead of relying on a bunch of SVG images, namely), but I don't have admin access so I can't do it myself. Do you think you could add it?
+<pre><nowiki>
+/* use HEJI2Text font if class="heji" */
+@font-face {
+   font-family: HEJI2Text;
+   src: url(https://plainsound.org/fonts/HEJI2Text.otf);
+}
+.heji {
+   font-family: HEJI2Text;
+}
+</nowiki></pre>
+--[[User:Fredg999|Fredg999]] ([[User talk:Fredg999|talk]]) 07:49, 3 January 2023 (UTC)
+: Hi Fredg999, would you please try the additions needed within [[User:Fredg999/common.css|''your personal common.css'']] and prepare or collect some representative examples (maybe just links to pages)? This would also be a good basis to better understand the impact of this proposal on the site and for discussing individual points with other users. Best regards --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 18:06, 3 January 2023 (UTC)
+:: I added a few examples to [[User:Fredg999/Sandbox#HEJI2Text testing area|''my personal Sandbox page'']]. Here is a screenshot of the result: https://drive.google.com/file/d/10ZLax9RYqQg3-mQtV9YeKPC--2VmvR43/view?usp=sharing
+:: The main use case I have in mind is the [[Helmholtz-Ellis notation]] page, where we could improve the reference tables and give more examples efficiently using the HEJI font. I was thinking of adding a table that shows all symbols (a bit like the HEJI notation palette on [https://www.plainsound.org/HEJI/ Plainsound's HS CALC]), but also shows the character mapping, so that readers can learn to use the font more easily on the wiki and elsewhere.
+:: Most symbols from the [[Alternative symbols for ups and downs notation]] could also be written using the HEJI font, since it provides symbols for each combination of the standard chromatic accidentals with one, two or three up or down arrows.
+:: Many other pages about just intonation could benefit from HEJI symbols as well, such as interval tables on various EDO pages (for easy up/down symbols as a complement to their "text" version; e.g. [[22edo#Intervals]]), as well as the [[Overtone scale]] page, where notation would be another representation of the JI scales, alongside the solfege notations already present, for example.
+:: --[[User:Fredg999|Fredg999]] ([[User talk:Fredg999|talk]]) 03:49, 4 January 2023 (UTC)
+::: I added the font to [[MediaWiki:Common.css]]. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 06:52, 4 January 2023 (UTC)
+:::: Thank you! --[[User:Fredg999|Fredg999]] ([[User talk:Fredg999|talk]]) 07:13, 4 January 2023 (UTC)