imslp wrote:Well... it is going to be a pain to cover all cases; I would just concern myself with covering the cases where Y/M/D, Y/M, M, or Y is given... everything else we will have to see as we go. $wgLang->date() should be able to deal with most, except the formatting of Y/M (the translation is there, but not the formatting). It'd be nice if we could somehow extract the Y/M formatting from Y/M/D, but I'm not sure if that's possible...
Agree with covering only Y/M/D, Y/M and Y (M doesn't make much sense, or does it? "Born: May"?). I'm afraid that extracting Y/M from Y/M/D is impossible, e.g. in Polish, "January" is "styczeń", but "January 1" is "1 stycznia" (genitive case, I believe; from the technical point of view, a different word). I'll have to think about it some more.
About birth and death places... one reason I didn't include that on the composer page is because it is not directly relevant to the copyright status of a composer; and I would like to prevent IMSLP from trying to do what Wikipedia has already done well (i.e. biography); which is why I have the wikipedia link entry in the composer template
Agree. Which leads me directly to the next question: Any idea how to present users with a link to the Wikipedia article in their own language? Obviously I do not
expect users to put all the links when they add a composer (sheer madness), but maybe we could periodically run a bot to add the links for all the enabled languages (i.e. those that have at least a partial translation on IMSLP)? So the question is twofold: 1) how to implement: direct use of IFLANG in the composer page, a template, or a parser function? 2) how to manage: I think I could code a basic bot for the purpose (I've done it before: I had an officially flagged bot on the Italian Wikipedia for a while which worked fairly well). To extract the language links from Wikipedia, I already have some code that is almost ready for use.