User talk:Wildheart7: Difference between revisions

From Tardis Wiki, the free Doctor Who reference
210 bytes removed ,  2 September 2012
m
No, you don't have new messages. Sorry for the false alarm.
m (Bot: Adding {{Please see|Can we disable visual editor please?}} <br> {{SUBST:user:CzechOut/autosig}} <span style="{{SUBST:user:CzechOut/Time}}">{{SUBST:#time:H:i: D}} {{SUBST:#time:d M Y}} </span>)
m (No, you don't have new messages. Sorry for the false alarm.)
Line 50: Line 50:


Once your down, save it and you can sign your post with the four <nowiki>~~~~</nowiki> and this will automatically add your signature. [[User:Mini-mitch|Mini-mitch]]\[[User talk:Mini-mitch|talk]] 11:18, July 8, 2011 (UTC)
Once your down, save it and you can sign your post with the four <nowiki>~~~~</nowiki> and this will automatically add your signature. [[User:Mini-mitch|Mini-mitch]]\[[User talk:Mini-mitch|talk]] 11:18, July 8, 2011 (UTC)
:Please see [[help:signatures]].  I obviously don't know how you have your signature line set up in [[Special:Preferences]], but that help file should give you a good overview of how to create a signature that works using templates. {{user:CzechOut/Sig}}&nbsp;<span style="{{User:CzechOut/TimeFormat}}">'''07:05:24 Sat&nbsp;'''09 Jul 2011&nbsp;</span>
:Please see [[help:signatures]].  I obviously don't know how you have your signature line set up in [[Special:Preferences]], but that help file should give you a good overview of how to create a signature that works using templates. {{user:CzechOut/Sig}}{{User:CzechOut/TimeFormat}}'''07:05:24 Sat&nbsp;'''09 Jul 2011&nbsp;</span>


::Glad you found the help file useful, and that it was successful in instructing you how to make things work.  Lets me know I was writing reasonably clearly.  I made a slight change to your sig file (which, by the way, I quite like.  Lovely retro 70s look).  The link to user talk pages is [[user talk:username]] not [[talk:username]].  So, as you can see, [[talk:Wildheart7]] is a redlink, while [[user talk:Wildheart7]] is a working bluelink. (Well, cause we're on that page right now, it's actually a ''black'' link.  But what's a shade or two between friends?)   
::Glad you found the help file useful, and that it was successful in instructing you how to make things work.  Lets me know I was writing reasonably clearly.  I made a slight change to your sig file (which, by the way, I quite like.  Lovely retro 70s look).  The link to user talk pages is [[user talk:username]] not [[talk:username]].  So, as you can see, [[talk:Wildheart7]] is a redlink, while [[user talk:Wildheart7]] is a working bluelink. (Well, cause we're on that page right now, it's actually a ''black'' link.  But what's a shade or two between friends?)   


::A little word of caution about font families.  In high web design theory, you should create what's called a "font stack", rather than including only one family.  The chances of most people actually having Consolas on their sstem is quite small. (About a quarter of Windows users don't have the font installed.  But 75% of Mac users don't have it installed.  And Linux/Ubuntu users don't even have Consolas available to them at all.) So you should create a list of alternative fonts that are somewhat close to what you want.  Peoples' browsers will then try each of the fonts, in order, until it finds one it can use. Click [http://coding.smashingmagazine.com/2009/09/22/complete-guide-to-css-font-stacks/ here] for a good overview of the concept, and [http://www.codestyle.org/servlets/FontStack here] for a free font stack generator that tells you the probability that your font stack will result in a font that people actually have on their systems.  (On my system, incidentally, your signature is just falling through to the random generic font of Tahoma.)  {{user:CzechOut/Sig}}&nbsp;<span style="{{User:CzechOut/TimeFormat}}">'''20:57:19 Sat&nbsp;'''09 Jul 2011&nbsp;</span>
::A little word of caution about font families.  In high web design theory, you should create what's called a "font stack", rather than including only one family.  The chances of most people actually having Consolas on their sstem is quite small. (About a quarter of Windows users don't have the font installed.  But 75% of Mac users don't have it installed.  And Linux/Ubuntu users don't even have Consolas available to them at all.) So you should create a list of alternative fonts that are somewhat close to what you want.  Peoples' browsers will then try each of the fonts, in order, until it finds one it can use. Click [http://coding.smashingmagazine.com/2009/09/22/complete-guide-to-css-font-stacks/ here] for a good overview of the concept, and [http://www.codestyle.org/servlets/FontStack here] for a free font stack generator that tells you the probability that your font stack will result in a font that people actually have on their systems.  (On my system, incidentally, your signature is just falling through to the random generic font of Tahoma.)  {{user:CzechOut/Sig}}{{User:CzechOut/TimeFormat}}'''20:57:19 Sat&nbsp;'''09 Jul 2011&nbsp;</span>


:::Format for font families is straightforward.  It's just a matter of listing them, separated by commas.  I've taken the liberty of building a bit of a font stack for you.  It'd look something like this:
:::Format for font families is straightforward.  It's just a matter of listing them, separated by commas.  I've taken the liberty of building a bit of a font stack for you.  It'd look something like this:
Line 66: Line 66:
:::The thing about Consolas that I gather you like about Consolas is that it's monospace and that it has a line through zeros.  Monaco does the samething for 99.5% of all Mac users, so they're taken care of.  It also picks up a sliver of Windows and Linux users.  Bitstream Vera Sans Mono is, I think, the same thing for Linux users, although it's a little less ubiquitous, so you need Nimbus Mono L in there to round out the Linux guys.  This leaves you with about 17% of all Windows users to take care of, which I guess if I weren't trying to do this in a hurry, I'd be able to figure out.  But, I'm just gonna let them fall through to any old monospace font, since you don't actually have a zero in your name anyway.  
:::The thing about Consolas that I gather you like about Consolas is that it's monospace and that it has a line through zeros.  Monaco does the samething for 99.5% of all Mac users, so they're taken care of.  It also picks up a sliver of Windows and Linux users.  Bitstream Vera Sans Mono is, I think, the same thing for Linux users, although it's a little less ubiquitous, so you need Nimbus Mono L in there to round out the Linux guys.  This leaves you with about 17% of all Windows users to take care of, which I guess if I weren't trying to do this in a hurry, I'd be able to figure out.  But, I'm just gonna let them fall through to any old monospace font, since you don't actually have a zero in your name anyway.  


:::So there ya go.  Note that the families don't ''have''to be on separate lines.  I just did that for clarity.  You can certainly get away with:<pre><span style="font-family:Consolas,Monaco,'Bitstream Vera Sans Mono','Nimbus Mono L',monospace;">Enter text here</span> </pre>Also, you ''can'' put single quotes around the one-word fonts, but you don't have to.  The final, generic font (monospace), should probably not go in single quotes.  I'm honestly not sure if it would hurt things, but I've never seen it done. Finally, observe how the final bit of punctuation is a semi-colon.  That lets the system know when the definition of the font-family is over.  You can put additional styling elements after that, such as font-size, color, whatever, but each stylistic instruciton must be separated from the next by a semi-colon.  {{user:CzechOut/Sig}}&nbsp;<span style="{{User:CzechOut/TimeFormat}}">'''22:43:44 Sat&nbsp;'''09 Jul 2011&nbsp;</span>
:::So there ya go.  Note that the families don't ''have''to be on separate lines.  I just did that for clarity.  You can certainly get away with:<pre><span style="font-family:Consolas,Monaco,'Bitstream Vera Sans Mono','Nimbus Mono L',monospace;">Enter text here</span> </pre>Also, you ''can'' put single quotes around the one-word fonts, but you don't have to.  The final, generic font (monospace), should probably not go in single quotes.  I'm honestly not sure if it would hurt things, but I've never seen it done. Finally, observe how the final bit of punctuation is a semi-colon.  That lets the system know when the definition of the font-family is over.  You can put additional styling elements after that, such as font-size, color, whatever, but each stylistic instruciton must be separated from the next by a semi-colon.  {{user:CzechOut/Sig}}{{User:CzechOut/TimeFormat}}'''22:43:44 Sat&nbsp;'''09 Jul 2011&nbsp;</span>


::Well, you're certainly welcome.  As you may have gathered, I am your "tech admin" for this wiki, so if you have any other technical issues, please do not hestiate to call again.  Other useful people on technical matters — in case I'm not here when you need me — include (in no particular order)  
::Well, you're certainly welcome.  As you may have gathered, I am your "tech admin" for this wiki, so if you have any other technical issues, please do not hestiate to call again.  Other useful people on technical matters — in case I'm not here when you need me — include (in no particular order)  
Line 75: Line 75:
::There are other people around who can help you with tech stuff if you just ask at [[forum:Panopticon]], but I thought you might like four names right up front of people who can help you more directly.   
::There are other people around who can help you with tech stuff if you just ask at [[forum:Panopticon]], but I thought you might like four names right up front of people who can help you more directly.   


::I know your user page says you're not going to "seriously" edit here, but we sure could use people with previous wiki experience.  So I hope you'll find this a good environment in which to satisfy your occasional twinge for wiki editing.  {{user:CzechOut/Sig}}&nbsp;<span style="{{User:CzechOut/TimeFormat}}">'''04:40:37 Mon&nbsp;'''11 Jul 2011&nbsp;</span>
::I know your user page says you're not going to "seriously" edit here, but we sure could use people with previous wiki experience.  So I hope you'll find this a good environment in which to satisfy your occasional twinge for wiki editing.  {{user:CzechOut/Sig}}{{User:CzechOut/TimeFormat}}'''04:40:37 Mon&nbsp;'''11 Jul 2011&nbsp;</span>
:::Thanks for your kind words.  Time stamp customization is also covered at [[help:signatures]] — though in fairness that section was added likely after you initially read it.  Just go to the help page, hit your keyboard's "end" key, and read the last section.  {{user:CzechOut/Sig}}&nbsp;<span style="{{User:CzechOut/TimeFormat}}">'''16:38:12 Mon&nbsp;'''11 Jul 2011&nbsp;</span>
:::Thanks for your kind words.  Time stamp customization is also covered at [[help:signatures]] — though in fairness that section was added likely after you initially read it.  Just go to the help page, hit your keyboard's "end" key, and read the last section.  {{user:CzechOut/Sig}}{{User:CzechOut/TimeFormat}}'''16:38:12 Mon&nbsp;'''11 Jul 2011&nbsp;</span>


== Infobox image at [[The Master]] ==
== Infobox image at [[The Master]] ==
Line 86: Line 86:
I think I should also advise you of another policy peculiarity that your image, [[:file:TheMaster.jpg]], offends.  It's a publicity shot, and therefore disallowed on in-universe pages, as explained in our [[tardis:Manual of Style|Manual of Style]] and at [[tardis:image use policy]].  We regard publicity stills of characters as being "a shot of the actor in the costume of the character", not as the character itself.  Publicity stills are not allowed on in-universe pages (that is, pages in the main [[namespace]] which are not adorned with {{tl|real world}}), or story pages.  You ''could'', however, use the image on [[John Simm]].  
I think I should also advise you of another policy peculiarity that your image, [[:file:TheMaster.jpg]], offends.  It's a publicity shot, and therefore disallowed on in-universe pages, as explained in our [[tardis:Manual of Style|Manual of Style]] and at [[tardis:image use policy]].  We regard publicity stills of characters as being "a shot of the actor in the costume of the character", not as the character itself.  Publicity stills are not allowed on in-universe pages (that is, pages in the main [[namespace]] which are not adorned with {{tl|real world}}), or story pages.  You ''could'', however, use the image on [[John Simm]].  


I know all that might seem silly, but it's important to drive a firm distinction between in-universe and out-of-universe pages, because the distinction affects the writing style of the two types of page.  In-universe pages are '''always''' written in the past tense, from the perspective of a social historian from the far future who's looking back on the events of the DWU as something from the distant past, but is only able to write about events ''as they were actually recorded'' by history.  So, firm past tense and no speculation.  Out-of-universe pages have a more relaxed, naturalistic, journalistic style that can use a variety of tenses.  Check out [[tardis:point of view]] for more on that. {{user:CzechOut/Sig}}&nbsp;<span style="{{User:CzechOut/TimeFormat}}">'''19:44:22 Mon&nbsp;'''11 Jul 2011&nbsp;</span>
I know all that might seem silly, but it's important to drive a firm distinction between in-universe and out-of-universe pages, because the distinction affects the writing style of the two types of page.  In-universe pages are '''always''' written in the past tense, from the perspective of a social historian from the far future who's looking back on the events of the DWU as something from the distant past, but is only able to write about events ''as they were actually recorded'' by history.  So, firm past tense and no speculation.  Out-of-universe pages have a more relaxed, naturalistic, journalistic style that can use a variety of tenses.  Check out [[tardis:point of view]] for more on that. {{user:CzechOut/Sig}}{{User:CzechOut/TimeFormat}}'''19:44:22 Mon&nbsp;'''11 Jul 2011&nbsp;</span>


==Formatting time==
==Formatting time==
Line 103: Line 103:
So, to sum up.  Create two subpages from your user page.  In file ''a'', place your formatting.  In file ''b'', place a template call to file ''a'' ({{user:Wildheart7/File a}}).  Then, in your preferences, type<pre><span style="{{SUBST:{{user:Wildheart7/File B}}}}">{{#time:<whatever>}}</span></pre>
So, to sum up.  Create two subpages from your user page.  In file ''a'', place your formatting.  In file ''b'', place a template call to file ''a'' ({{user:Wildheart7/File a}}).  Then, in your preferences, type<pre><span style="{{SUBST:{{user:Wildheart7/File B}}}}">{{#time:<whatever>}}</span></pre>


Don't forget that [[help:signatures]] tells you more about how actualy format time — that is, it tells you what that <whatever> should be.  Hope that helps! {{user:CzechOut/Sig}}&nbsp;<span style="{{User:CzechOut/TimeFormat}}">05:58: Sat&nbsp;24 Sep 2011&nbsp;</span>
Don't forget that [[help:signatures]] tells you more about how actualy format time — that is, it tells you what that <whatever> should be.  Hope that helps! {{user:CzechOut/Sig}}{{User:CzechOut/TimeFormat}}05:58: Sat&nbsp;24 Sep 2011&nbsp;</span>
==Why have two templates?==
==Why have two templates?==
Well, I explained three paragraphs back why I use two templates, but perhaps it's easier to see if we compare two signatures next to each other.  Edit this section and look at the difference in the amount of code generated by your method
Well, I explained three paragraphs back why I use two templates, but perhaps it's easier to see if we compare two signatures next to each other.  Edit this section and look at the difference in the amount of code generated by your method
Line 109: Line 109:
as compared to mine
as compared to mine
{{user:CzechOut/Sig}}
{{user:CzechOut/Sig}}
As you can see, having two templates allows for a much neater appearance when you're editing.  If you're in a discussion with only one or two replies, maybe that difference is insignificant.  But if you're in an involved discussion with lots of respondents, it matters a great deal.  Also, if you dump only a template call onto a page, there's less chance that subsequent editors will "break" your signature.  If it's an entire bit of code, all they have to do to break it is backspace over your closing <code></span></code> tag. {{user:CzechOut/Sig}}&nbsp;<span style="{{User:CzechOut/TimeFormat}}">14:28: Sun&nbsp;25 Sep 2011&nbsp;</span>
As you can see, having two templates allows for a much neater appearance when you're editing.  If you're in a discussion with only one or two replies, maybe that difference is insignificant.  But if you're in an involved discussion with lots of respondents, it matters a great deal.  Also, if you dump only a template call onto a page, there's less chance that subsequent editors will "break" your signature.  If it's an entire bit of code, all they have to do to break it is backspace over your closing <code></span></code> tag. {{user:CzechOut/Sig}}{{User:CzechOut/TimeFormat}}14:28: Sun&nbsp;25 Sep 2011&nbsp;</span>


:To be honest with you, I'd never heard of {{tl|nosubst}} before you mentioned it.  It, or the possibility of it, isn't mentioned in any SUBST documentation I've ever read.  And it obviously doesn't exist at tardis, so I've never played with it.  I see through flatly Googling "nosubst wikia" that it has purchase throughout several Wikia wikis, but I'm dubious of its abilities to handle time.
:To be honest with you, I'd never heard of {{tl|nosubst}} before you mentioned it.  It, or the possibility of it, isn't mentioned in any SUBST documentation I've ever read.  And it obviously doesn't exist at tardis, so I've never played with it.  I see through flatly Googling "nosubst wikia" that it has purchase throughout several Wikia wikis, but I'm dubious of its abilities to handle time.
Line 119: Line 119:
:I see you're still not giving us a time stamp on this wiki.  I do need you to solve this problem ''somehow'', as it's a specific requirement of our [[tardis:signature policy|signature policy]] that all signatures be time stamped.  A ''temporary'' workaround, while you sort out your own personal requirements, Wikia wide, is just to force a time stamp through the use of 5 tildes, separated by a space from however many tildes you're using to call your signature.  So, if you're calling your sig with three tildes, you could produce a time stamp by typing:<pre>~~~ ~~~~~</pre>.   
:I see you're still not giving us a time stamp on this wiki.  I do need you to solve this problem ''somehow'', as it's a specific requirement of our [[tardis:signature policy|signature policy]] that all signatures be time stamped.  A ''temporary'' workaround, while you sort out your own personal requirements, Wikia wide, is just to force a time stamp through the use of 5 tildes, separated by a space from however many tildes you're using to call your signature.  So, if you're calling your sig with three tildes, you could produce a time stamp by typing:<pre>~~~ ~~~~~</pre>.   


:Still, I'm not quite sure I quite understand the problem you're having.  I go on plenty of wikis and I've never had a problem getting a time stamp to show up.  If you need any additional help, please don't hesitate to write again.  {{user:CzechOut/Sig}}&nbsp;<span style="{{User:CzechOut/TimeFormat}}">14:30: Sat&nbsp;01 Oct 2011&nbsp;</span>
:Still, I'm not quite sure I quite understand the problem you're having.  I go on plenty of wikis and I've never had a problem getting a time stamp to show up.  If you need any additional help, please don't hesitate to write again.  {{user:CzechOut/Sig}}{{User:CzechOut/TimeFormat}}14:30: Sat&nbsp;01 Oct 2011&nbsp;</span>
{{Please see|Can we disable visual editor please?}} <br> {{user:CzechOut/Sig}}&nbsp;<span style="{{User:CzechOut/TimeFormat}}">07:52: Wed&nbsp;21 Dec 2011&nbsp;</span>
{{Please see|Can we disable visual editor please?}} <br> {{user:CzechOut/Sig}}{{User:CzechOut/TimeFormat}}07:52: Wed&nbsp;21 Dec 2011&nbsp;</span>
Bots, Bureaucrats, emailconfirmed, Administrators
765,429

edits

Cookies help us deliver our services. By using our services, you agree to our use of cookies.