Template talk:Index talk remarks

From Wikisource
Jump to navigation Jump to search

Three exclamation marks?[edit]

I like the new look of this, but can I please suggest that the wording be changed to the less-overly-excited: "Formatting guidelines may already have been established for this proofreading project. Please check this Index's discussion page." I really don't think we need three exclamation marks, and a an orange border, and two exclamation mark icons at either side. Thanks!!!! (hehe) — Sam Wilson ( TalkContribs ) … 06:28, 14 June 2013 (UTC)[reply]

It was more about making it fit onto one line for the [assumed] most common settings and still having it make some sort of sense. Your line is too long and won't center & break nicely when larger than the typical font settings are in use.
...And the overkill is kind of neccessary because most newcomers are less-than-clueless to be nice about it. -- George Orwell III (talk) 08:05, 14 June 2013 (UTC)[reply]
Thanks for reducing the excitedness of the message... sorry to be a bother, but I'm wondering if the letter-spacing:1.65px should also be removed. Now there's only one exclaimation mark, it looks a bit odd. What do you think? — Sam Wilson ( TalkContribs ) … 12:00, 21 September 2013 (UTC)[reply]
Not a good idea? — Sam Wilson ( TalkContribs ) … 05:05, 15 November 2013 (UTC)[reply]
What exactly is it that you are still hung-up on here?

I thought it was well explained (Scriptorium?) that we're trying to emphasize a point, one frequently lost even on the most regular of contributors - to see if there is an editing style already in use before Users blindly create one of their own. In light of this aim, the extra, gimmicky bells and whistles such as multiple exclamation points / letter-spacing were warranted - even necessary - in the hopes of drawing in the clueless User and have them visit the Talk: page before doing anything counter-productive.

Sorry but I'd rather prevent 4 different approaches to formatting occur in a work than technically appease some notion of the Punctuation Police at work in this matter. -- George Orwell III (talk) 05:22, 15 November 2013 (UTC)[reply]

Sure, no worries! I just assumed it was a left-over from before and not intentional. I do think it's possible to emphasize the message and also have good typography (I mean, you can't really hassle be about being a pedant on a site that is all about pedantic proofreading, can you?! hehe). I'll give up on this now, but it just looks weird to me every single time I open an Index page. :-) That's all. — Sam Wilson ( TalkContribs ) … 06:17, 15 November 2013 (UTC)[reply]

Protected edit request: fix spacing[edit]

{{editprotected}}

Please apply the edits I've made in the sandbox. They correct a minor, but annoying, display issue that results in no space between the words "Please check this" and the link to the discussion page. Pathore (talk) 05:10, 10 February 2015 (UTC)[reply]

Close enough? The period at the end and the addition of a span to "control" margin(s) didn't sit well with me so I left those out. Plus I moved the #ifexist call to the main template where it should have been all along. -- George Orwell III (talk) 05:54, 10 February 2015 (UTC)[reply]
No effect on the problem. While moving the #ifexist call to the parent template is a good idea, I'm still seeing the period overlapped with the "e" at the end of the discussion page link and no space between the words "Please check this" and the discussion page link. The problem seems to be that the link is inheriting the negative margin from the {{ombox}} |style= parameter. Another option would be to attach the margins directly to the A element, but I don't know how to do that here without adding a CSS class to the ombox and then adding rules to the stylesheets.
Another solution, which also works, is to simply get rid of the non-breaking spaces. I've done this in the sandbox and it solves the problem I'm seeing. It seems that non-breaking spaces have strange side-effects on the box model in my environment. Pathore (talk) 06:16, 10 February 2015 (UTC)[reply]
What about now?

That whole ___box scheme is html table based and needs to be replaced with an all div (css3 compliant) approach. Problem is mostly contiguous free-time for me but (at some point) "they" also switched to using LUA to generate the family of templates and I'm not all fluent when it comes to such things. -- George Orwell III (talk) 07:06, 10 February 2015 (UTC)[reply]

It's fixed now. Thanks! Pathore (talk) 07:32, 10 February 2015 (UTC)[reply]