![]() |
Template:Music is permanently
protected from editing because it is a
heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by
consensus, editors may use {{
edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's
documentation to add usage notes or
categories.
Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases. |
Per the discussion on Wikipedia:Manual of style (music), I've put what was at Accidental here; moved the user box to Template:User Instruments List (discuss at Template talk:User Instruments List) and moved the newly created "Music portal" navigation box to Template:Music portal. -- Myke Cuthbert (talk) 15:49, 10 July 2007 (UTC)
What do you think about supporting {{music|#}}
and {{music|b}}
(using the number sign "#" and letter "b") as alternatives to {{music|sharp}}
and {{music|flat}}
?--
Dbolton
21:56, 10 July 2007 (UTC)
{{music|#}}
and {{music|b}}
, but added support for Unicode flats and sharps, i.e. {{music|♯}}
and {{music|♭}}
. This should make it more convenient if you are converting a page of Unicode sharps and flats.--
Dbolton
17:02, 16 July 2007 (UTC)Perhaps page protection would be appropriate for this page if most important changes have been made now? I'm sure it will have very extensive usage at some point in the near future. ck lostsword• T• C 14:33, 20 July 2007 (UTC)
This is a very cool template and I applaud your efforts. My only problem is in the "sample text" under the heading "Notes and rests". That looks like a clear place where prose should be used, not characters. It's bad style to write in that way, even if one can. Can someone please think of a better example of their use? I'll ponder it as well, but nothing is immediately coming to mind. Mak (talk) 16:04, 20 July 2007 (UTC)
Has anyone else noticed a change in behavior on Firefox? Now all the music symbols that don't use this template are displaying as "?" on my system instead of the proper flats and sharps. Is it just my system? I certainly didn't uninstall any fonts. -- Myke Cuthbert (talk) 04:02, 28 December 2007 (UTC)
Are rendering squares in Internet Explorer 6.0. OK in Mozilla 3.0 Fefogomez ( talk) 13:52, 9 July 2008 (UTC)
I suggest we add support for the diminished symbols (°) and (ø).
I believe this would require adding the following lines to the code, but I am afraid of breaking it.
| dim = ° | dimslash = <sup>ø</sup>
Jake the Editor Man ( talk) 17:14, 25 September 2008 (UTC)
°
and <sup>ø</sup>
. Plain Unicode text is clearer for editors to read and understand. --
Dbolton (
talk)
16:58, 26 September 2008 (UTC)The SVG images don't scale with different font sizes. I suggest that EM be used instead of PX as the unit of measurement. SharkD ( talk) 19:12, 2 January 2009 (UTC)
Perhaps a more realistic request: can we get symbols for common time and cut time? Something along the lines of {{Music|Cut}}? I was looking at Marty's book on Mozart's tempo indications and he uses those symbols within the text a lot. James470 ( talk) 04:49, 26 August 2009 (UTC)
Can someone add the Arabic half-flat and -sharp symbols (
and
)? The addition would be
| halfb | halfflat = [[File:Arabic music notation half flat.svg|9px]] | half# | halfsharp = [[File:Arabic music notation half sharp.svg]]
151.203.246.40 ( talk) 19:56, 30 October 2009 (UTC)
If we include the demiflat and demisharp symbols, shouldn't the sesquiflat (
, [[Image:Llpd+1½.svg|x16px]]) and sesquisharp (
, [[Image:Llpd-1½.svg|x16px]]) symbols be represented also? As with the demiflat, there is an alternative version of the flat sign with slashes (
, [[Image:Llpd-1½_var.svg|x16px]]). -
NDCompuGeek (
talk)
20:46, 15 November 2009 (UTC)
User ESSch added the Russion names of the symbols in the table. Since this is a template in the English WP, this serves no purpose and should be removed. − Woodstone ( talk) 01:56, 13 January 2010 (UTC)
To John Cardinal for making the documentation easier to read and more beautiful. And to Ford Prefect 42 for the addition of time signatures. -- Michael Scott Cuthbert (talk) 16:26, 6 March 2010 (UTC)
If one goes to the image description page for File:Figure_rythmique_noire_hampe_haut.svg one finds that it has been marked as superseded by File:Quarter note with upwards stem.svg due to the fact that the sides are cut off. However, since all the notehead images used here have their sides cut off File:Quarter note with upwards stem.svg doesn't fit in and unless there are similar replacements for all it should not be used in this context. Hyacinth ( talk) 08:37, 3 April 2010 (UTC)
Would it be terribly difficult to make
., such as for use in
Symphony for Classical Orchestra? Or should I just kludge it with
. ?
James470 (
talk)
02:55, 1 August 2010 (UTC)
Edokter ( talk | contribs) has been making changes to this template that I feel merit discussion here. See the page history. Lanthanum-138 ( talk) 12:29, 29 March 2011 (UTC)
Why are the scale degrees above where text lies and at a smaller font, especially when this makes it difficult to use them with any other variants of the music template such as accidentals, and while the math symbols with carets are below text lies? For example:
Hyacinth ( talk) 15:21, 3 July 2011 (UTC)
I have adjusted the 9 image (as earlier images: at 200px height, it has 6px margin). Is this OK (before/after):
Doesn't that defeat the purpose of the template? If one is just going to use Δ one could simply use it without the template. Hyacinth ( talk) 22:15, 14 May 2012 (UTC)
You are invited to participate in an RfC at Wikipedia talk:Requests for mediation/The Beatles on the issue of capitalising the definite article when mentioning that band's name in running prose. This long-standing dispute is the subject of an open mediation case and we are requesting your help with determining the current community consensus. Thank you for your time. For the mediators. ~ GabeMc ( talk| contribs) 22:59, 22 September 2012 (UTC)
I updated the Time Signatures to be serif and bold to better match real time signatures. I have a "pull request" on the underlying Lua code to make the numbers touch each other; when that request is completed, the template should automatically update to be even more accurate. -- Michael Scott Cuthbert (talk) 19:38, 27 January 2015 (UTC)
{{su|a=c|p=3|b=4|lh=0.85em}}
which gives: 3 {{Music|time_plain|3|4}}
would do that. --
Michael Bednarek (
talk)
04:20, 13 July 2016 (UTC)
Hyacinth, your recent edits to this template have created {{ error}} transclusions in three articles:
Can you fix these? Thanks, Wbm1058 ( talk) 16:31, 9 December 2015 (UTC)
I noticed that the # and b signs produced by this template have considerable white space around them, making combinations like F# and Bb look like F # and B b (here not using the template to show different behaviours stably). So I modified the template with some negative margin. Other editors notified me that this does not work out correctly in all cases. Anyone suggestions how to solve this issue? − Woodstone ( talk) 18:45, 2 May 2012 (UTC)
I would like to revive this issue. The spacing of this template, at least in case of # and b, is incorrect and produces ugly excessive white space before and after the accidental.
I have tried to solve this issue a long time ago, but met resistance. Who can help to find a good solution? Woodstone ( talk) 14:25, 9 January 2017 (UTC)
I think I've found a way to give those who have these problems (as I do, in fact) the means of overcoming them by using style sheets to correct the spacing. If the flat, natural, and sharp symbols in the template were to be enclosed in <span id="music-flat"> … </span>, <span id="music-natural"> … </span>, and <span id="music-sharp"> … </span> pairs, respectively, then anyone whose browsers put extra spaces around these characters could remove them by putting lines of the form
in a css style sheet, as I have done in my
common.css.
I have modified the
music template sandbox to incorporate these suggestions and test them. As far as I can tell, they work as expected, and will cause no problems for anyone without the adjustment instructions in any of their style sheets. Here are some expressions displayed using both the current music template and the music sandbox template, as modified:
Without the adjustment instructions in a style sheet, the first and second expressions in each of these pairs should render identically. With the above instructions included in a style sheet, however, the flat, natural and sharp symbols in the second expression of each of these pairs should be shifted 3 pixels to the left, and the text following those symbols 6 pixels to the left. That's certainly how it works for me, at least.
Before implementing these suggestions in the template proper, I thought it best to run them past the denizens of this talk page in case there's something I might be missing.
David Wilson (
talk ·
cont)
18:19, 27 November 2017 (UTC)
html[data-useragent*='unique-string']
, where "unique-string" is a substring of your browser's user-agent string. See my my
common.css file for the code that works for me on my IPad Pro. For your Android phone the string "Android" is probably good enough to work, I have now made the proposed changes to the template proper.
David Wilson (
talk ·
cont)
13:50, 28 November 2017 (UTC)
Seeing the actual change made, I now realise it's not technically correct. The attribute "id" is supposed to have a unique value within the whole page. So if the are more occurrences of one of the symbols, this is violated. You should have used a "class" instead. Sorry for not noticing it earlier. − Woodstone ( talk) 06:36, 29 November 2017 (UTC)
Moving this section to the bottom, since most of the discussion happened after the above sections were posted. -- SarekOfVulcan (talk) 16:38, 30 November 2017 (UTC)
Just for comparison, here's the straight text use of the flat symbol, compared with the template (no CSS), and I just copied the results of the template and pasted it back into the wikitext, to make sure it was an accurate comparison. I'll include a screenshot of how it renders in Chrome on Windows 10 as well.
-- SarekOfVulcan (talk) 16:38, 30 November 2017 (UTC)
Can we include the Helmholtz-Ellis notation as well? For example:
--
kupirijo (
talk)
10:41, 26 September 2019 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Would it be possible to add the following accidentals to the template: https://www.smufl.org/version/latest/range/arelEzgiUzdilekAeuAccidentals/ . This is to be able to improve the wikipedia article Turkish makam. Thank you. -- kupirijo ( talk) 08:40, 14 January 2020 (UTC) kupirijo ( talk) 08:40, 14 January 2020 (UTC)
As noted in a previous thread, there is a problem with the flat character, no matter which method you use to make it {{music|flat}} or {{music|b}} or {{flat}} or just entering the unicode symbol: it adds extra space before and after the flat sign. Sharp doesn't have this problem. Example: G♭ minor, G♯ minor. Makes displays look really crappy. I'm surprised nobody's corrected this in all these years. What's up?
Another oddity I've noticed: I tried just typing the actual unicode symbols in an article, which works, but the symbols' font is too large and creates extra space between lines. Obviously the wiki code for these templates reduces the font size. I'm using Safari on an iPad, BTW. Using the entity method ♭ or ♯ (or their equivalent decimal numbers), produces the same problem (at least on iPad Safari).
What worries me, though, about the use of all these templates or even entering the unicode symbol, is that both these characters, flat and sharp, no matter what method you use to produce them, are HTML 5.0. If you have an older 4.0 compliant browser, as many readers do, the symbol will display as a question mark or a square or blob or somesuch thing. I would therefore suggest refrain from using ANY of these flat or sharp templates at all and just type the WORD: G-flat minor. The convention is to put a dash between the letter key and the word "flat" or "sharp", with no spaces (per MOS). I see people do mass changes on pages that have the word spelled out, changed to the symbol template (everybody using {{music|sharp}}, not {{sharp}}). Doing such mass changes and using these templates is a bad idea IMO, for compatibility. Plain English text avoids all these problems. LisztianEndeavors ( talk) 23:19, 28 January 2020 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
"h-minor" is wrong. "b-minor" is right. MFSHK ( talk) 08:10, 19 November 2020 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Could the double-sharp and double-flat symbols be replaced by the actual Unicode characters 𝄪 and 𝄫 rather than images? Using images makes it difficult to link and copy-paste, and the actual Unicode characters have been in Unicode since way back in 2001 (Unicode 3.1). Double sharp ( talk) 15:15, 29 November 2021 (UTC)
{{
edit template-protected}}
template again.
P.I. Ellsworth -
ed.
put'r there
19:44, 29 November 2021 (UTC)I can't see any reason not to use 𝄪
(double sharp 𝄪) and 𝄫
(double flat 𝄫) instead of the images
and
, but my exposure to browsers and operating systems is limited. BTW, the article
G-sharp major shows that linking under the current scheme can be done. --
Michael Bednarek (
talk)
01:41, 30 November 2021 (UTC)
Comparison:
𝄪
𝄪 vs
𝄫
𝄫 vs
Would it be possible to adopt the double-flat/double-sharp convention regarding {{music|halfdim}}
? There's a Unicode codepoint U+01D1A9
for it now, which renders as 𝆩. It's certainly not well supported presently, which is why I'm curious if it could be rendered as SVG in lieu of its actual codepoint.
Remsense (
talk)
04:13, 17 May 2023 (UTC)
I'm surprised that dynamics such as fff are not included here. Is there a reason? Tayste ( edits) 22:16, 20 June 2023 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please delete line 80 - '17 upside down' is duplicated
also line 180 - 'dot' is duplicated
also '+' is duplicated at lines 118 and 270 - please remove the duplicate at line 270 Desb42 ( talk) 10:48, 9 July 2023 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
We already have an image for the "Double whole note". Why not just use that as the template result? Enx8 ( talk) 18:26, 8 March 2024 (UTC)
{{music|doublewholenote}}
=
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Decided to make another topic because I wanted this to stand out from the double whole note ("breve")
I found two images of the 128th note and rest.
File:Quintuple-croche tête en bas.svg Not sure why the note image is so small, hopefully you can work with it
File:128th rest.svg same with this one.
Will subscribe to keep updated. Enx8 ( talk) 13:44, 11 March 2024 (UTC)
Following the discussion and recent amendment to MOS:FOOT to allow for specific use in music, and another discussion about pitch on MOS:MUSIC, I propose a possible "foot" shortcut that displays the correct prime character for use with (e.g.) organ stops, wind instrument air columns, etc. Something like adding the following:
| ft | ' | feet | foot =<span class="music-foot">′</span>
so that "this organ has a 16′ pedal stop" can be notated using 16{{music|foot}}
. It's only a convenience shortcut, because using 16{{prime}}
ought to have the same result (16′). —
Jon (
talk)
21:00, 20 March 2024 (UTC)
{{prime|16}}
which fixes typographic spacing details, and not 16{{prime}}
. Not sure how this music template can handle a second parameter like this, e.g. {{music|foot|16}}
? Perhaps this is all too hard...! —
Jon (
talk)
21:06, 20 March 2024 (UTC) ...aha, | foot ={{{2}}}<span class="music-foot">′</span>
![]() | It is
requested that an edit be made to the
template-protected template at
Template:Music. ( · history · last · links · sandbox · edit sandbox · sandbox history · sandbox last edit · sandbox diff · test cases · transclusion count · protection log) This template must be followed by a complete and specific description of the request, so that an editor unfamiliar with the subject matter could complete the requested edit immediately.
Edit requests to template-protected pages should only be used for edits that are either uncontroversial or supported by
consensus. If the proposed edit might be controversial, discuss it on the protected page's talk page before using this template. Consider making changes first to the
template's sandbox and
test them thoroughly here before submitting an edit request. To request that a page be protected or unprotected, make a
protection request. When the request has been completed or denied, please add the |
{{music|triplesharp}} = ♯
This currently looks very poorly, with half of it using unicode ♯ and half of it using SVG. Ideally we should create a new single SVG containing the whole combined symbol, though a lower effort version might do this:
[[File:Sharp.svg|{{{size|x16px}}}|sharp]][[File:DoubleSharp.svg|{{{size|x8px}}}|double sharp]] =![]()
![]()
- Rainwarrior ( talk) 18:28, 14 June 2024 (UTC)
I've created the proposed SVG:
[[File:TripleSharp.svg|{{{size|x16px}}}|triple sharp]] =
Example:
- Rainwarrior ( talk) 19:23, 14 June 2024 (UTC)
If you want nice SVG output, which actually works really nicely (I have it working on my test instances of MediaWiki) then please make some noise on this bug. It's ridiculous that it is now eleven years old and I don't think anyone involved has any appreciation of how much of a difference it would make. — Jon ( talk) 00:42, 21 June 2024 (UTC)
![]() |
Template:Music is permanently
protected from editing because it is a
heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by
consensus, editors may use {{
edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's
documentation to add usage notes or
categories.
Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases. |
Per the discussion on Wikipedia:Manual of style (music), I've put what was at Accidental here; moved the user box to Template:User Instruments List (discuss at Template talk:User Instruments List) and moved the newly created "Music portal" navigation box to Template:Music portal. -- Myke Cuthbert (talk) 15:49, 10 July 2007 (UTC)
What do you think about supporting {{music|#}}
and {{music|b}}
(using the number sign "#" and letter "b") as alternatives to {{music|sharp}}
and {{music|flat}}
?--
Dbolton
21:56, 10 July 2007 (UTC)
{{music|#}}
and {{music|b}}
, but added support for Unicode flats and sharps, i.e. {{music|♯}}
and {{music|♭}}
. This should make it more convenient if you are converting a page of Unicode sharps and flats.--
Dbolton
17:02, 16 July 2007 (UTC)Perhaps page protection would be appropriate for this page if most important changes have been made now? I'm sure it will have very extensive usage at some point in the near future. ck lostsword• T• C 14:33, 20 July 2007 (UTC)
This is a very cool template and I applaud your efforts. My only problem is in the "sample text" under the heading "Notes and rests". That looks like a clear place where prose should be used, not characters. It's bad style to write in that way, even if one can. Can someone please think of a better example of their use? I'll ponder it as well, but nothing is immediately coming to mind. Mak (talk) 16:04, 20 July 2007 (UTC)
Has anyone else noticed a change in behavior on Firefox? Now all the music symbols that don't use this template are displaying as "?" on my system instead of the proper flats and sharps. Is it just my system? I certainly didn't uninstall any fonts. -- Myke Cuthbert (talk) 04:02, 28 December 2007 (UTC)
Are rendering squares in Internet Explorer 6.0. OK in Mozilla 3.0 Fefogomez ( talk) 13:52, 9 July 2008 (UTC)
I suggest we add support for the diminished symbols (°) and (ø).
I believe this would require adding the following lines to the code, but I am afraid of breaking it.
| dim = ° | dimslash = <sup>ø</sup>
Jake the Editor Man ( talk) 17:14, 25 September 2008 (UTC)
°
and <sup>ø</sup>
. Plain Unicode text is clearer for editors to read and understand. --
Dbolton (
talk)
16:58, 26 September 2008 (UTC)The SVG images don't scale with different font sizes. I suggest that EM be used instead of PX as the unit of measurement. SharkD ( talk) 19:12, 2 January 2009 (UTC)
Perhaps a more realistic request: can we get symbols for common time and cut time? Something along the lines of {{Music|Cut}}? I was looking at Marty's book on Mozart's tempo indications and he uses those symbols within the text a lot. James470 ( talk) 04:49, 26 August 2009 (UTC)
Can someone add the Arabic half-flat and -sharp symbols (
and
)? The addition would be
| halfb | halfflat = [[File:Arabic music notation half flat.svg|9px]] | half# | halfsharp = [[File:Arabic music notation half sharp.svg]]
151.203.246.40 ( talk) 19:56, 30 October 2009 (UTC)
If we include the demiflat and demisharp symbols, shouldn't the sesquiflat (
, [[Image:Llpd+1½.svg|x16px]]) and sesquisharp (
, [[Image:Llpd-1½.svg|x16px]]) symbols be represented also? As with the demiflat, there is an alternative version of the flat sign with slashes (
, [[Image:Llpd-1½_var.svg|x16px]]). -
NDCompuGeek (
talk)
20:46, 15 November 2009 (UTC)
User ESSch added the Russion names of the symbols in the table. Since this is a template in the English WP, this serves no purpose and should be removed. − Woodstone ( talk) 01:56, 13 January 2010 (UTC)
To John Cardinal for making the documentation easier to read and more beautiful. And to Ford Prefect 42 for the addition of time signatures. -- Michael Scott Cuthbert (talk) 16:26, 6 March 2010 (UTC)
If one goes to the image description page for File:Figure_rythmique_noire_hampe_haut.svg one finds that it has been marked as superseded by File:Quarter note with upwards stem.svg due to the fact that the sides are cut off. However, since all the notehead images used here have their sides cut off File:Quarter note with upwards stem.svg doesn't fit in and unless there are similar replacements for all it should not be used in this context. Hyacinth ( talk) 08:37, 3 April 2010 (UTC)
Would it be terribly difficult to make
., such as for use in
Symphony for Classical Orchestra? Or should I just kludge it with
. ?
James470 (
talk)
02:55, 1 August 2010 (UTC)
Edokter ( talk | contribs) has been making changes to this template that I feel merit discussion here. See the page history. Lanthanum-138 ( talk) 12:29, 29 March 2011 (UTC)
Why are the scale degrees above where text lies and at a smaller font, especially when this makes it difficult to use them with any other variants of the music template such as accidentals, and while the math symbols with carets are below text lies? For example:
Hyacinth ( talk) 15:21, 3 July 2011 (UTC)
I have adjusted the 9 image (as earlier images: at 200px height, it has 6px margin). Is this OK (before/after):
Doesn't that defeat the purpose of the template? If one is just going to use Δ one could simply use it without the template. Hyacinth ( talk) 22:15, 14 May 2012 (UTC)
You are invited to participate in an RfC at Wikipedia talk:Requests for mediation/The Beatles on the issue of capitalising the definite article when mentioning that band's name in running prose. This long-standing dispute is the subject of an open mediation case and we are requesting your help with determining the current community consensus. Thank you for your time. For the mediators. ~ GabeMc ( talk| contribs) 22:59, 22 September 2012 (UTC)
I updated the Time Signatures to be serif and bold to better match real time signatures. I have a "pull request" on the underlying Lua code to make the numbers touch each other; when that request is completed, the template should automatically update to be even more accurate. -- Michael Scott Cuthbert (talk) 19:38, 27 January 2015 (UTC)
{{su|a=c|p=3|b=4|lh=0.85em}}
which gives: 3 {{Music|time_plain|3|4}}
would do that. --
Michael Bednarek (
talk)
04:20, 13 July 2016 (UTC)
Hyacinth, your recent edits to this template have created {{ error}} transclusions in three articles:
Can you fix these? Thanks, Wbm1058 ( talk) 16:31, 9 December 2015 (UTC)
I noticed that the # and b signs produced by this template have considerable white space around them, making combinations like F# and Bb look like F # and B b (here not using the template to show different behaviours stably). So I modified the template with some negative margin. Other editors notified me that this does not work out correctly in all cases. Anyone suggestions how to solve this issue? − Woodstone ( talk) 18:45, 2 May 2012 (UTC)
I would like to revive this issue. The spacing of this template, at least in case of # and b, is incorrect and produces ugly excessive white space before and after the accidental.
I have tried to solve this issue a long time ago, but met resistance. Who can help to find a good solution? Woodstone ( talk) 14:25, 9 January 2017 (UTC)
I think I've found a way to give those who have these problems (as I do, in fact) the means of overcoming them by using style sheets to correct the spacing. If the flat, natural, and sharp symbols in the template were to be enclosed in <span id="music-flat"> … </span>, <span id="music-natural"> … </span>, and <span id="music-sharp"> … </span> pairs, respectively, then anyone whose browsers put extra spaces around these characters could remove them by putting lines of the form
in a css style sheet, as I have done in my
common.css.
I have modified the
music template sandbox to incorporate these suggestions and test them. As far as I can tell, they work as expected, and will cause no problems for anyone without the adjustment instructions in any of their style sheets. Here are some expressions displayed using both the current music template and the music sandbox template, as modified:
Without the adjustment instructions in a style sheet, the first and second expressions in each of these pairs should render identically. With the above instructions included in a style sheet, however, the flat, natural and sharp symbols in the second expression of each of these pairs should be shifted 3 pixels to the left, and the text following those symbols 6 pixels to the left. That's certainly how it works for me, at least.
Before implementing these suggestions in the template proper, I thought it best to run them past the denizens of this talk page in case there's something I might be missing.
David Wilson (
talk ·
cont)
18:19, 27 November 2017 (UTC)
html[data-useragent*='unique-string']
, where "unique-string" is a substring of your browser's user-agent string. See my my
common.css file for the code that works for me on my IPad Pro. For your Android phone the string "Android" is probably good enough to work, I have now made the proposed changes to the template proper.
David Wilson (
talk ·
cont)
13:50, 28 November 2017 (UTC)
Seeing the actual change made, I now realise it's not technically correct. The attribute "id" is supposed to have a unique value within the whole page. So if the are more occurrences of one of the symbols, this is violated. You should have used a "class" instead. Sorry for not noticing it earlier. − Woodstone ( talk) 06:36, 29 November 2017 (UTC)
Moving this section to the bottom, since most of the discussion happened after the above sections were posted. -- SarekOfVulcan (talk) 16:38, 30 November 2017 (UTC)
Just for comparison, here's the straight text use of the flat symbol, compared with the template (no CSS), and I just copied the results of the template and pasted it back into the wikitext, to make sure it was an accurate comparison. I'll include a screenshot of how it renders in Chrome on Windows 10 as well.
-- SarekOfVulcan (talk) 16:38, 30 November 2017 (UTC)
Can we include the Helmholtz-Ellis notation as well? For example:
--
kupirijo (
talk)
10:41, 26 September 2019 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Would it be possible to add the following accidentals to the template: https://www.smufl.org/version/latest/range/arelEzgiUzdilekAeuAccidentals/ . This is to be able to improve the wikipedia article Turkish makam. Thank you. -- kupirijo ( talk) 08:40, 14 January 2020 (UTC) kupirijo ( talk) 08:40, 14 January 2020 (UTC)
As noted in a previous thread, there is a problem with the flat character, no matter which method you use to make it {{music|flat}} or {{music|b}} or {{flat}} or just entering the unicode symbol: it adds extra space before and after the flat sign. Sharp doesn't have this problem. Example: G♭ minor, G♯ minor. Makes displays look really crappy. I'm surprised nobody's corrected this in all these years. What's up?
Another oddity I've noticed: I tried just typing the actual unicode symbols in an article, which works, but the symbols' font is too large and creates extra space between lines. Obviously the wiki code for these templates reduces the font size. I'm using Safari on an iPad, BTW. Using the entity method ♭ or ♯ (or their equivalent decimal numbers), produces the same problem (at least on iPad Safari).
What worries me, though, about the use of all these templates or even entering the unicode symbol, is that both these characters, flat and sharp, no matter what method you use to produce them, are HTML 5.0. If you have an older 4.0 compliant browser, as many readers do, the symbol will display as a question mark or a square or blob or somesuch thing. I would therefore suggest refrain from using ANY of these flat or sharp templates at all and just type the WORD: G-flat minor. The convention is to put a dash between the letter key and the word "flat" or "sharp", with no spaces (per MOS). I see people do mass changes on pages that have the word spelled out, changed to the symbol template (everybody using {{music|sharp}}, not {{sharp}}). Doing such mass changes and using these templates is a bad idea IMO, for compatibility. Plain English text avoids all these problems. LisztianEndeavors ( talk) 23:19, 28 January 2020 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
"h-minor" is wrong. "b-minor" is right. MFSHK ( talk) 08:10, 19 November 2020 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Could the double-sharp and double-flat symbols be replaced by the actual Unicode characters 𝄪 and 𝄫 rather than images? Using images makes it difficult to link and copy-paste, and the actual Unicode characters have been in Unicode since way back in 2001 (Unicode 3.1). Double sharp ( talk) 15:15, 29 November 2021 (UTC)
{{
edit template-protected}}
template again.
P.I. Ellsworth -
ed.
put'r there
19:44, 29 November 2021 (UTC)I can't see any reason not to use 𝄪
(double sharp 𝄪) and 𝄫
(double flat 𝄫) instead of the images
and
, but my exposure to browsers and operating systems is limited. BTW, the article
G-sharp major shows that linking under the current scheme can be done. --
Michael Bednarek (
talk)
01:41, 30 November 2021 (UTC)
Comparison:
𝄪
𝄪 vs
𝄫
𝄫 vs
Would it be possible to adopt the double-flat/double-sharp convention regarding {{music|halfdim}}
? There's a Unicode codepoint U+01D1A9
for it now, which renders as 𝆩. It's certainly not well supported presently, which is why I'm curious if it could be rendered as SVG in lieu of its actual codepoint.
Remsense (
talk)
04:13, 17 May 2023 (UTC)
I'm surprised that dynamics such as fff are not included here. Is there a reason? Tayste ( edits) 22:16, 20 June 2023 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please delete line 80 - '17 upside down' is duplicated
also line 180 - 'dot' is duplicated
also '+' is duplicated at lines 118 and 270 - please remove the duplicate at line 270 Desb42 ( talk) 10:48, 9 July 2023 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
We already have an image for the "Double whole note". Why not just use that as the template result? Enx8 ( talk) 18:26, 8 March 2024 (UTC)
{{music|doublewholenote}}
=
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Decided to make another topic because I wanted this to stand out from the double whole note ("breve")
I found two images of the 128th note and rest.
File:Quintuple-croche tête en bas.svg Not sure why the note image is so small, hopefully you can work with it
File:128th rest.svg same with this one.
Will subscribe to keep updated. Enx8 ( talk) 13:44, 11 March 2024 (UTC)
Following the discussion and recent amendment to MOS:FOOT to allow for specific use in music, and another discussion about pitch on MOS:MUSIC, I propose a possible "foot" shortcut that displays the correct prime character for use with (e.g.) organ stops, wind instrument air columns, etc. Something like adding the following:
| ft | ' | feet | foot =<span class="music-foot">′</span>
so that "this organ has a 16′ pedal stop" can be notated using 16{{music|foot}}
. It's only a convenience shortcut, because using 16{{prime}}
ought to have the same result (16′). —
Jon (
talk)
21:00, 20 March 2024 (UTC)
{{prime|16}}
which fixes typographic spacing details, and not 16{{prime}}
. Not sure how this music template can handle a second parameter like this, e.g. {{music|foot|16}}
? Perhaps this is all too hard...! —
Jon (
talk)
21:06, 20 March 2024 (UTC) ...aha, | foot ={{{2}}}<span class="music-foot">′</span>
![]() | It is
requested that an edit be made to the
template-protected template at
Template:Music. ( · history · last · links · sandbox · edit sandbox · sandbox history · sandbox last edit · sandbox diff · test cases · transclusion count · protection log) This template must be followed by a complete and specific description of the request, so that an editor unfamiliar with the subject matter could complete the requested edit immediately.
Edit requests to template-protected pages should only be used for edits that are either uncontroversial or supported by
consensus. If the proposed edit might be controversial, discuss it on the protected page's talk page before using this template. Consider making changes first to the
template's sandbox and
test them thoroughly here before submitting an edit request. To request that a page be protected or unprotected, make a
protection request. When the request has been completed or denied, please add the |
{{music|triplesharp}} = ♯
This currently looks very poorly, with half of it using unicode ♯ and half of it using SVG. Ideally we should create a new single SVG containing the whole combined symbol, though a lower effort version might do this:
[[File:Sharp.svg|{{{size|x16px}}}|sharp]][[File:DoubleSharp.svg|{{{size|x8px}}}|double sharp]] =![]()
![]()
- Rainwarrior ( talk) 18:28, 14 June 2024 (UTC)
I've created the proposed SVG:
[[File:TripleSharp.svg|{{{size|x16px}}}|triple sharp]] =
Example:
- Rainwarrior ( talk) 19:23, 14 June 2024 (UTC)
If you want nice SVG output, which actually works really nicely (I have it working on my test instances of MediaWiki) then please make some noise on this bug. It's ridiculous that it is now eleven years old and I don't think anyone involved has any appreciation of how much of a difference it would make. — Jon ( talk) 00:42, 21 June 2024 (UTC)