User talk:ObsessiveMathsFreak
Listing the episode names
I originally toyed with the idea of putting all 3 names for episodes in their templates but thought it looked "cluttered", but if you think it will work okay. The problem is that each episode has kind of 3 titles: the original Japanese title, the English title Gainax came up with, and ADV Film's official translation of the original Japanese title. On top of this, we could like the kangi for the original Japanese.
Should we list all of these in template, list some and put the other info in the "Notes" section, or just have 2 slots: "Japanese title" (that is, list ADV film's official English translation instead of the Japanese) and the English Title selected by Gainax? The result being i.e. "An Angel's Attack"/"Angel Attack" and we just don't bother to list "Shito, shūrai" or the japanese characters? Btw, I got it in my head that Gainax was spelled all-capitals "GAINAX" for some reason; what's the story with that? At any rate, another issue is do we spell things in all-caps as "ANGEL ATTACK" or "THE BEAST", or would it be less...garish, to just write "Angel Attack" and "The Beast"?--V 19:01, 23 July 2007 (EDT)
- Best to bring all this up in a thread somewhere. But in any case, I think we should basically throw everything into the template and then decide later if and how we display it. ObsessiveMathsFreak 05:41, 24 July 2007 (EDT)
- Reichu told me to put a freeze on English dub info for the moment; please revert changes you made to the character infobox template. --V 13:25, 11 August 2007 (EDT)
- The edits adding the other dub VAs names have been reverted, which is altogether a good thing as I was never able to get them done right. ObsessiveMathsFreak 06:50, 13 August 2007 (EDT)
Problem with user rights
This page: "Special pages" (on the left there) should have a subsection under "restricted pages" which, besides saying "block user", should have a thing letting me make someone an Administrator (below Bureaucrat but above normal user); I cannot see this; why don't I have it? Can you help?--V 20:34, 15 August 2007 (EDT)
- I think you mean the Special:UserRights page. As far as I know, MediaWiki 1.8 only allows Bureaucrats to add Sysops. I'll look into changing this, as it would be unwise to have more than one Bureaucrat account, especially if those accounts were being used for general editing. I'll set what I can scrounge up. ObsessiveMathsFreak 18:36, 17 August 2007 (EDT)
- I thought you Reichu and I had Bureaucrat stuff so I could use all the tools. If I am going to "run the EvaPedia as I see fit", I need the B-Crat tools for stuff; this is not the most important thing I'm focusing on at the moment though; crud I slow down here for a few days and look at the clutter... ^_^ --V 19:28, 18 August 2007 (EDT)
- I've figured out how to give Sysops the rights you need. I just need to figure out how to add those rights without breaking the wiki. You should have them shortly, hopefully.ObsessiveMathsFreak 19:39, 18 August 2007 (EDT)
- I need to be able to make other people Administrators (the biggest difference, tool-wise, between Bureaucrats and Admins). --V 21:19, 18 August 2007 (EDT)
- I've figured out how to give Sysops the rights you need. I just need to figure out how to add those rights without breaking the wiki. You should have them shortly, hopefully.ObsessiveMathsFreak 19:39, 18 August 2007 (EDT)
- I thought you Reichu and I had Bureaucrat stuff so I could use all the tools. If I am going to "run the EvaPedia as I see fit", I need the B-Crat tools for stuff; this is not the most important thing I'm focusing on at the moment though; crud I slow down here for a few days and look at the clutter... ^_^ --V 19:28, 18 August 2007 (EDT)
Protecting pages
Adding the Protection template to pages isn't preventing normal users from editing them; Administrators by definition have to be able to "Protect" pages by locking out the editing of a particular page by non-Administrators; the feature isn't working. This is a serious problem, please find how to make pages locked. --V 17:43, 14 December 2007 (PST)
Transferral
Is it the simple act of copy-pasting and editing comments? I added the comments for cut 001a in the OP...is that how it should look? http://evageeks.org/FGP/FGC:OP_Cut_001a
Shin-seiki's comment is directly appeneded to Reichu's, with no space between them. --UrsusArctos 18:01, 19 April 2008 (PDT)
- I'm in the process of Ironing out some issues, so there may be a few teething troubles. ObsessiveMathsFreak 18:05, 19 April 2008 (PDT)
- All right. I presume it's okay to keep transferring the comments to the cuts, in the meantime?--UrsusArctos 18:07, 19 April 2008 (PDT)
- Go right ahead. It's only small things like formatting anyway. ObsessiveMathsFreak 18:09, 19 April 2008 (PDT)
- Great. Do you intend to do part A of the OP now? If so, I'll move to doing part B, so we won't have any edit conflicts.--UrsusArctos 18:15, 19 April 2008 (PDT)
- For now, I rest. But you could try simply randomly selecting cuts to prevent edit conflicts. ObsessiveMathsFreak 18:17, 19 April 2008 (PDT)
My user page is locked for some reason?
Cut test
Simple collapsible table |
---|
Lorem ipsum dolor sit amet |
Screenshots | Cut # | Description/Dialogue | Commentary | ||
---|---|---|---|---|---|
images |
Edit |
|
|
Table test
Stuff before
α | cell2
|
the original table again |
|
|
Stuff after
Simple collapsible table | |||
---|---|---|---|
Lorem ipsum dolor sit amet |
|
More stuff after
Screenshots | Cut # | Description/Dialogue | Commentary | ||
---|---|---|---|---|---|
images | Edit |
|
|
Test collapse comments
Screenshots | Cut # | Description/Dialogue | Commentary | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
images | Edit |
|
|
|
Image Linking Test
{{#img: image=Sachiel Monitor.jpg |page=Sachiel |width=150px}} {{#img: image=Sachiel Monitor.jpg |page=Sachiel |width=}} {{#img: image=Sachiel Monitor.jpg |page= |width=}}
Multicolumn Ordered List Test
|
|
CSS testing
Table Test 1 |
---|
Lorem ipsum dolor sit amet |
Logic Testing
no
Table Testing
A | B | C |
Col 1, row 1 and 2 | Col 2, row 1 (and 2) and 3 | Col 1, row 2 |
Col 3, row 2 | ||
stuff | more | even more |
Multicut test
Screenshots | Cut # | Description/Dialogue | Commentary | |||
---|---|---|---|---|---|---|
118 |
|
| ||||
images01 |
121 |
|
| |||
|
| |||||
images03 |
| |||||
123 |
|
| ||||
images01 |
121 |
|
| |||
| ||||||
images03 |
| |||||
images04 |
|
| ||||
|
124 |
|
|
MGS Supplemental test
Random: Character Flaws
(Expanded Commentary from 03-002 (ctd.) )
OMF: But I wonder why directors put in such weaknesses in "giant robots" at all. The most obvious reason is that it "keeps things interesting", although I think it's best summed up in the following interchange from the original Metal Gear Solid. When Solid Snake has to face the mecha Metal Gear Rex, he is assisted by its lead designer Hal Emmerich, a.k.a Otacon, who is able to reveal the beast's weak point—and why having one isn't always such a bad thing.
Otacon:“Snake, Rex's armor is impregnable. You can't do any damage with the weapons you've got.
Rex uses the latest advances in compound armor. The only way you can pierce it is with a high performance HEAT (high explosive, anti-tank) round.”
Snake:“So what do I do?”
Otacon:“Rex's pilot seat operates exactly like a VR system. It's got multiple sensors connected to a high tech interface used for the controls. It's completely self-enclosed and shut off from the outside environment.”
Snake:“He's not using his naked eyes?”
Otacon:“That's right. So if you could somehow destroy the sensors... Do you see that round plate on Rex's left arm?”
Snake:“Yeah, that thing that looks like a shield?”
Otacon:“That's a radome. If you can destroy that thing, it won't be able to use its electronic equipment.”
Snake:“So he'll be blinded?”
Otacon:“Yeah. Try to hit that radome with a Stinger missile.”
Snake:“So that will stop it?”
Otacon:“No, Rex was designed so it can be controlled manually too.”
Snake:“Oh great.”
Otacon:“The part that looks like a beak is where the pilot seat is. In an emergency it will open up. Rex's armor is perfect. You can't destroy it.”
Snake:“You told me that already.”
Otacon:“But the interior is a different story.”
Snake:“I get it...first I destroy the radome. That will force him to open up the pilot's seat.”
Otacon:“Right. If you can shoot a Stinger missile into the cockpit, you'll destroy the computer control system.”
Snake:“You intentionally designed it with a weak point?”
Otacon:“It's not a weak point. I like to think of it as a character flaw. People just aren't complete without some type of character flaw, don't you think?”
Snake:“I guess so. I owe you one, Otacon.”
OMF: The quirks and limitations of various mecha—Evangelions included—can be viewed as type of super robot character flaw. Such technical idiosyncrasies and limitations act like personality traits for the mecha, giving them their own individuality; and of course allowing for dramatic tension when the mecha's "flaw" catches up with them, just as with regular cast characters. They allow mechas to be characters in their own right.
EVA-01's own character flaw is a great example of this kind of trope. The ticking clock time limit of course adds inherent tension, but moreover this limitation is actually something EVA-01 actually manages to "overcome" during piviotal moments in the narrative. Its eleventh hour reactivations and ultimate procurement of an S^2 organ give the Evangelion its own form of climactic character development, and provides some of the most memorable scenes in the show.