User:Vaarky/Sandbox: Difference between revisions
Jump to navigation
Jump to search
m (Text replace - 'http;//choralwiki.net' to '{{SERVER}}') |
m (lnktxt vs. linktxt) |
||
| Line 6: | Line 6: | ||
{{MultiCatList|match=%Senfl|SATTB|Renaissance music|Works in Latin|Sacred music|col=2}} | {{MultiCatList|match=%Senfl|SATTB|Renaissance music|Works in Latin|Sacred music|col=2}} | ||
{{MultiCatList|Michael Praetorius compositions|SATB|Renaissance music|Works in Latin|Sacred music|col=2}} | {{MultiCatList|Michael Praetorius compositions|SATB|Renaissance music|Works in Latin|Sacred music|col=2}} | ||
--> | |||
==LnkTxt vs. LinkText== | |||
<!-- | |||
Hi Claude. Thank you for your continued work in adding texts and translations of works here at CPDL. If I might make one request - when you're adding links to text pages, please use Template:LnkTxt only when the list of settings on the text page is automatically generated. In all other cases, please use Template:LinkText. You can see which text pages you should use Template:LnkTxt for here. For the most part, you should use Template:LinkText. Many thanks! --Bobnotts talk 22:38, 16 December 2008 (UTC) | |||
Well, so, there are only 22 texts that can be reached by LinkTxt template. Why these and no other ? Also, when I add a LnkText template, is it possible to generate automatically the works/composer entry in the settings list for that text ?Claude 08:55, 17 December 2008 (UTC) | |||
Using Template:LnkTxt and automated settings lists was an experiment by Carlos or Chuck (I can't remember who started it) which has subsequently been abandoned to some degree or other because it doesn't allow for the level of flexibility that we usually want on such text pages. For example, on Psalm 150 we have a list of settings then a list of information about each setting - which verses it sets, what language it's in, etc. Basically, it's a big mess... --Bobnotts talk 14:02, 17 December 2008 (UTC) | |||
Hi Claude, let me try to explain it: The initial idea to use template:LnkTxt to generate an automated listing for text pages was mine, and a couple of pages were created in this new format as an experiment. Chuck decided to try it on a Psalm page, but psalm text pages do have their peculiarities and so it was decided not to use LnkTxt on them. BUT using it for all other works is still ok. So, if you see 3 or more works which share exactly the same text (or with very slight differences), you are encoraged to create a text page for them. The procedure is simple: | |||
1. Replace on one of the works page {{NoText}} by {{LnkTxt|<text page title>|<composer surname>}}. | |||
2. When you save the page, the <text page title> will appear as a red link. Click on it to create this new text page. | |||
3. On the page that opens, paste the following and click Save: {{subst:ChoralWiki:Text template}} | |||
4. Edit the page again and voilà!, you have a new text page properly formatted, just waiting for your text and translations. | |||
5. As soon as you click on Preview, the first work to which you applied LnkTxt on step 1 should already appear on the settings list. | |||
If you have any doubt, just ask me; if you simply prefer not to use this tool, feel free not to! :) —Carlos Email.gif 18:17, 17 December 2008 (UTC) | |||
Hi, Carlos, I tried your way of doing. It seems to work well : eleven works with same text and translation on that new text page. Some Bytes less on the server. But the works seem to be weirdly sorted (historical linking to the text page?). -Claude 15:32, 18 December 2008 (UTC) You just have to use the third parameter, Claude (writing to himself ;-) - Claude 07:40, 19 December 2008 (UTC) | |||
Oh, yes Claude! You just missed the sort key by composer surname ;) | |||
There's just one other point that I wanted to discuss with you: The Puer natus text has two main versions, one completely in Latin and one macarronic in Latin/German. We must decide how to deal with these two versions. Shall they stay on the same page? If I'm not mistaken, the macarronic text is used only by Praetorius. Carlos 14:31, 19 December 2008 (UTC) | |||
Just have a look at the 3 scores which are on the same discussed page: On Christian Mondrup's score, there is German text that wasn't with the Latin one, on Marco Cipoo's, I doesn't see any word in German! On the Abel di Marco edition, I doesn't see any word at all, nor any note because I'm unable to see any score of this editor (neither Mac nor Window, neither IE nor Firefox)! If you can, just explain me how! Yesterday, I just let the Latin words that were here and added a link to the general common text. | |||
Hi Claude, I've added a PDF/MIDI for the Abel di Marco edition (you need a plugin installed to see his page). As you noticed, the other two editions had different music or text and were moved to independent pages, ok! Carlos 18:31, 19 December 2008 (UTC) | |||
Carlos, the problem is that I've not been able to get the necessary plugin: it's an old (2002) SmartMusicViewer.class in Java impossible to install (neither on PC -Xp or Vista- nor Mac) because CodaMusic disappeared and all the links point to the successive FinaleViewer, which works perfectly well to see Finale files you posess on your disk but doesn't show the Abel diMarco's files that stay on his site (right click is there disabled). The whole thing is that among a thousand works in Latin on CPDL claiming "No text" there are about 500 in this case. So, thank you for having showed one score tonight. There are only 499 left to do ;-) | |||
--> | --> | ||
Revision as of 05:43, 20 December 2008
I've commented out items to save space.
LnkTxt vs. LinkText
Text replacement tool for sysadmins
...to input a URL as source or target string, just substitute in it http:// for http;//. The confirmation message will display the address as you typed it, but the URL will be saved correctly in the database.
Links to MediaWiki man pages, DPL etc.
Testing tables for translation
Why doesn't the composer's given name show?
Summary: du Caurroy does not appear under D in composers section because lowercase d is sorted after capital Z. Includes how to fix.