User talk:Philosopher
Requesting page deletion
Hi,
could you please fill in the complete template when requesting articles to be deleted? The date is important. See {{delete}} for all the variables.
Cheers, Gijs (talk) 22:17, 15 September 2013 (UTC)
That screenshot category link on the Village pump
I am of course thankful, but also very curious as how to you managed to fix that erroneous link on FlightGear wiki:Village pump#FlightGear screenshot categories (permalink). It could of course been one of those things that just fixes themselves...
The thing is is I only wrote [[:Category: in the top left cell and then copied it to the rest of them, and somehow one of the links end up not working!?
Thanks again. :-)
—Johan G (Talk | contribs) 20:31, 12 May 2014 (UTC)
- It was mostly dumb luck. I was intrigued by the error, so I tried several variations by editing a few words there, deleting dashes, etc, then I just copied the one above it (Category:FlightGear cockpit screenshots) and edited the name, and it worked! My guess was some funny character there or something - it looked like MediaWiki didn't want to parse it at all (I like their mark-down style, though, where syntax can be combined with non-syntax text that uses similar characters -- programming languages aren't allowed to do that).
- Aha! Plugging it into xlate reveals this character: ‎ (html escape code) -- that's apparently "left-to-right mark", which is of course invisible :). How'd ya get that on your keyboard? xlate gives me this as it's hex sequence (for the one character): "26 23 38 32 30 36 3b". :D
- —Philosopher (talk) 20:42, 12 May 2014 (UTC)
ec130.nas/ec135.nas/bo105.nas vs generic-helicopter-engine.nas
Uhmm..... The origin of this files is in the bo105.nas by Melchior Franz. It fakes and simulates helicopter engines for YASim helicopter as YASim isn't able to simulate engines for them. It does not only fake the engines, it also simulates the torque values and fuel systems, and other various stuff like blade snap sound and helicopter-type depending vibrations, for those helicopters made by AS/ MBB/ EC/ Airbus. Unfortunately all three helicopters (EC130, EC135, BO105) varies in fuel system, supporting systems and engines. So for the EC135 P2 I had to change the calculation of the torque values to get it right with the real climb values of the helicopter, and the fuel system will be also changed. So it would be maybe more forward to keep the ec130.nas and combine the other nasal files into one. Though I once dreamed to have a generic helicpter-engine.nas, today I think I'm not sure as many helicopters completely differs from each other in fuel system and other stuff. It would be more forward to allow YASim to simulate engines for helicopters. It would be also more realistic. --HHS (talk) 21:00, 25 May 2014 (UTC)
- the mid-term solution may be aapting that code to make use of galvedro's A Failure Management Framework for FlightGear work, which is generic enough to also provide building blocks for modeling different systems modeling. For YASim stuff, you'll probably want to get in touch with the guy whose patches have recently been committed (check the forum or newsletter).--Hooray (talk) 21:42, 25 May 2014 (UTC)
Template:Code vs <code>
I just saw your {{code}} template and the way you want to use it. I see what you want to do, but there is a few issues with templates, primarily that the equal sign (=) and the pipe sign (|) breaks them. They can be worked around by using {{!}} and {{=}} instead or by putting them characters inside <nowiki> tags though. See below.
-{{code||}}-{{code|{{!}}}}-{{code|=}}-{{code|{{=}}}}-
--|-{{{1}}}-=-
I think it might a good idea to play around with the CSS text and background attributes and find out what works and looks good (and looks good even if it is used a lot) and then apply that to what is used with the <code> tag (it is dictated in the wiki's style sheet). One has be bear in mind though that <code> can be used with both inline and on block level elements, though we for block level elements in the very most cases seem prefer <syntaxhighlight> (which is way better), a leading space or <pre>.