Template talk:Audio-nohelp

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Revealing license information[edit]

As with Template:IPAudio I question the design of this template, since it effectively obscures license information for anyone but Commons-savvy users. We would never accept this treatment of pictures or photographs. Why should this be any different?

Peter Isotalo 10:19, 21 June 2006 (UTC)[reply]

And what exactly is the problem with the license information? In the case of pictures one has to do some work as well in order to see it, we don't add {{GFDL}} license tags to every image caption, nor do we put links to the license there. The license is still available to those who seek it, so we're ok with the laws. //Halibutt 13:10, 17 July 2006 (UTC)[reply]
We do put links to the license information from every image. It's on the image description page, which you get to by clicking on the image. Not all pictures are GFDL. Same for audio.
I've suggested that javascript be used to hide the info and help links until someone hovers over the sound file. You can try it yourself using the example on that talk page. This would provide both forms of information while not cluttering up the articles with "(info • help)" after every sound file. No one seems to have noticed my proposal, though. (Don't worry; it would be made to degrade gracefully for people who don't have javascript.) — Omegatron 13:32, 17 July 2006 (UTC)[reply]
Yup, it's a decent solution (using pop-ups myself), but the problem here seems to be that the info is unavailable to un-registered users. I bet most of the registered users know how to strip an URL anyway, so reaching the media info page is easy for them anyway. This can't be said of unregistered users who don't have their own monobook installed - unless of course the script is integrated with the default monobook. Is that an option at all? //Halibutt 14:36, 17 July 2006 (UTC)[reply]
No. The proposal is to use the pop-ups sitewide (after tweaking, troubleshooting and bug killing). Then we won't need this type of template at all and people won't complain about the clutter from the regular templates either. It will solve all the problems we currently have with audio file links. — Omegatron 15:15, 17 July 2006 (UTC)[reply]
Just let me know where is the voting held and you have my vote on that one. //Halibutt 18:55, 17 July 2006 (UTC)[reply]
I doubt it's something that people are going to vote on. Just put a note in Template_talk:Audio#Formatting showing support. — Omegatron 19:21, 17 July 2006 (UTC)[reply]

Wrapping problems with in-line use[edit]

This template adds a space after the displayed text. When used in-line it is often followed by a comma or period. The added space creates a violation with almost any style guide and may lead to wrapping the single punctuation mark to the next line. See examples on pitch (music). Can someone break through the protection and remove the blank? P.S. I do not see the (info) tag shown in the description here.−Woodstone (talk) 14:42, 9 September 2008 (UTC)[reply]

EditProtected: Documentation + hAudio[edit]

{{editprotected}}

Please apply {{documentation}}; then apply the hAudio microformat, by changing [ redacted ]. No visual changes will occur. The category is hidden. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 20:08, 8 April 2010 (UTC)[reply]

 Done — Martin (MSGJ · talk) 09:02, 9 April 2010 (UTC)[reply]
Thank you. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 20:49, 9 April 2010 (UTC)[reply]

"info"?[edit]

Hi, I came across this template at Concert pitch, and I am a bit confused by the "info" link, which seems to point to pages where one can listen to the item (or could if one had the required software). Why is the link called "info" rather than, say, "listen"? It does not seem to be the right word. 86.128.3.46 (talk) 03:03, 1 September 2012 (UTC)[reply]

Actually, the link goes to the file page where there is important information such as the creator, source, and licencing of the file. SpinningSpark 10:17, 13 May 2014 (UTC)[reply]