Help talk:Manual of Style/Specific Cases
I think the part abou taking screenshots should have some modifications:
In all cases, SRB2 screenshots should be taken in 640x400 Software mode. Software mode screenshots are preferable, though OpenGL screenshots are also acceptable. The reasons for this screenshot guideline are:
- A 640x400 graphic is considered to be in web-resolution, thus complying with United States fair use laws.
- 640x400 is also the default resolution used by SRB2.
- Software mode is the default for SRB2, and is officially supported over OpenGL mode. However, OpenGL mode screenshots are also acceptable, as the differences between the two renderers are considered to be small. Note that these additional provisions exist for OpenGL mode screenshots:
- Coronas and dynamic lighting must be turned off, mainly because being turned off is the default behavior for SRB2. Dynamic lighting also differentiates OpenGL mode from Software mode unneccessarily.
- OpenGL-specific glitches must not be prevalent and/or obvious in screenshots.
- 640x400 resolution is still preferred.
- You must set
GR_FILTERMODEto 0, or Nearest, thus giving the same pixellation as Software mode.
An exception to the additional OpenGL provisions is when it's required for the subject matter to be documented. Obviously, this would include such features as OpenGL lights, as OpenGL lights are an OpenGL-only feature. An article on OpenGL mode itself, covering renderer-specific topics, is also an acceptable case of exception. Otherwise, if the meaning of a subject matter is intended to be the same across both Software and OpenGL modes, the additional provisions apply.
Although 640x400 is preferred, 320x200 is also an acceptable resolution in which screenshots may be taken. This complies even more with the definition of web-resolution, which would then safely allow the image to be assumed to comply with United States fair use laws. 320x200 was also a default resolution used by SRB2 in earlier versions. ~Kaysakado • Talk
I'm sorry, but I don't know why.
What's the problem with
<br> tags? I'm sorry, I mean, it was in the Style Guide saying to only use it for paragraphs. I didn't read it because I thought I knew enough about English (I got a 33 on the ACT section on English for the record) and formatting. I thought I was making things look better. –SonicMaster 17:34, 1 December 2007 (PST)
That's why I'm thinking of revamping the Style Guide. :P
You see the whitespace in both pages? Those are made by multiple <br> tags. While those tags are okay for individual paragraphs, they are improper for layout purposes, including whitespace. My argument for this is that it's improper for usability, such as screenreaders or zoomed text. See w:Accessibility and w:Computer accessibility. Also, it's much better to use CSS rules, such as margins or padding, to handle width and stuff. It's a concept for more advanced HTML, but a really important one. For that reason, I'll eradicate any and all uses of <br> whitespaces, and also table-code images. --Digiku talk 17:44, 1 December 2007 (PST)
Oh...I think I get it. It might not appear correctly in the wrong window size or a browser other than Firefox... –SonicMaster 17:57, 1 December 2007 (PST)
OK. I think we need to start mentioning these:
- They are a very good workaround for whitespace.
- They can actually be very nice-looking.
Rules on how to do the gallery tag, therefore, should be added:
<gallery caption="An example on how to use the gallery tag" widths="160px" heights="100px" perrow="3"> Image:Slumped-pic1.PNG|Picture 1 Caption Image:Slumped-pic2.PNG|Picture 2 Caption Image:Slumped-pic3.PNG|Picture 3 Caption Image:Slumped-pic4.PNG|Picture 4 Caption </gallery>
will produce this:
Picture 1 Caption
Picture 2 Caption
Picture 3 Caption
Picture 4 Caption
Don't you think gallery tags are for the win? –SonicMaster 14:32, 7 February 2008 (PST)
I just discovered that Digiku already mentioned this. –SonicMaster 14:52, 25 February 2008 (PST)
Before I change this, I want to make sure of this. It says "Objectplace" is always capitalized. Um, shouldn't it be "OBJECTPLACE"? –SonicMaster 14:58, 25 February 2008 (PST)