Difference between revisions of "FlightGear wiki:Village pump"

From FlightGear wiki
Jump to: navigation, search
(Reorganizing the Git articles)
(Space shuttle screenshots category need cleanup: Added Category:Screenshots of Earthview to some of the relevant screenshots.)
 
(117 intermediate revisions by 10 users not shown)
Line 1: Line 1:
{{Archives|[[/Archive 2012|2012]]|[[/Archive 2013|2013]]|[[/Archive 2014|2014]]|[[/Archive 2015|2015]]}}
+
{{Archives|[[/Archive 2012|2012]]|[[/Archive 2013|2013]]|[[/Archive 2014|2014]]|[[/Archive 2015|2015]]|[[/Archive 2016|2016]]|[[/Archive 2017|2017]]|[[/Archive 2018|2018]]|[[/Archive 2019|2019]]}}
 
{{shortcut|FGW:VP}}
 
{{shortcut|FGW:VP}}
 +
 
Welcome to the '''Village Pump'''. This page is used to discuss the technical issues, operations and guidelines of the [[FlightGear wiki]].
 
Welcome to the '''Village Pump'''. This page is used to discuss the technical issues, operations and guidelines of the [[FlightGear wiki]].
  
 
Please <span class="plainlinks">[{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics]</span> to the '''bottom''' of this page.
 
Please <span class="plainlinks">[{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics]</span> to the '''bottom''' of this page.
  
Old discussion should be moved to a [[FlightGear wiki:Village pump/Archive YEAR]]. These discussions can then be moved to a relevant talk page if appropriate.
+
Old discussions should be moved to a [[FlightGear wiki:Village pump/Archive YEAR]]. These discussions can then be moved to a relevant talk page if appropriate.
  
== Welcome template? ==
+
== New Portal: Embedded or Hardware (02/2020) ==
I have been thinking about suggesting a welcome template, for example named {{obr}}welcome{{cbr}}, to place on top of (at least) new users user discussion pages.
+
Suggestion: Dedicated portal for articles relating to embedded/hardware topics (which would be in line with numerous threads on the forum, as well as existing articles on the wiki). - [[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 11:59, 17 February 2020 (EST)
  
It should welcome the (new) user
+
: That is slightly less complicated than you might think.  What you would do is to create a new page with the prefix <code>Portal:</code> and a suitable name, say for example [[Portal:Hardware development]], [[Portal:Cockpit hardware]] or [[Portal:DIY cockpit hardware]], or maybe [[Portal:Hardware]] if you would also like to see commercial hardware there, and then copy and modify the content from a similar portal.
  
In addition, it should probably mention and/or link to pages mentioning:
+
: Hint: There is actually not a portal [[Help:Namespaces|namespace]], it is just a prefix. The portal pages are actually in the main namespaces, and thus function just like any other article page on the wiki.
* The introduction page/tutorial (Hmm, I do not think I did finish that one. See [[Help talk:Tutorial]] ([http://wiki.flightgear.org/index.php?title=Help_talk:Tutorial&oldid=70843 perm])).
+
* Help pages
+
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 13:35, 10 March 2020 (EDT)
* How to use categories (in particular not like #tags, ;-) but also that image and article categories should be separate, but link to each other)
+
* The portals
+
* The style manual
+
* Discussion pages and where to discuss what:
+
** How to use discussion pages
+
** The wiki in general: The village pump (this page)
+
** Wiki articles: Article discussion pages
+
** Wiki user actions:  User discussion pages
+
  
Maybe it should also mention that FGAddon aircraft, effects, other features etc. (except for their articles) and their bugs should be discussed on the forum, unless developers say otherwise, and that core features should be discussed on the developer mailing list and core bugs on the bug tracker.
+
: Though I think your [[Portal:Embedded]] might be more diffuse than [[Portal:Hardware]] for people that do not know what {{wikipedia|embedded software}} is, I have still added it to the main page and added [[:Category:Portals]] to it.  It will get more use if people can find it. :-P
  
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 20:31, 30 January 2016 (EST)
+
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 04:16, 14 March 2020 (EDT)
  
: I think this is a great ideaA nice concise summary with links to help a new user navigate the FlightGear jungle would be a great additionIt should however remain very short with simple sentences - while being complete - as many users are not native speakersSo maybe there should be translations of the template with manually added links at the bottom for easy access to all the translations?
+
== Use as few categories as possible ==
 +
Always use as few categories as possibleCategories are a place in a structure rather than tagsPutting each page in a lot of categories will put a lot of of pages in each categoryThere is in particular no need to put a page in both a category and then in each category above that category.
  
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 03:35, 12 February 2016 (EST)
+
Please see advice in [[Help:Your first article#Categories]] and maybe also [[Help:categories]].
  
:: Regarding an introduction article, I have come to the conclusion that a complete but long article is probably not as helpful as short but specific help pages.  In essence the latter would be easier to navigate and absorb.  I have therefore started to slowly split up some of the help pages and have added one more section to [[Help:Contents]].
+
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 13:04, 15 March 2020 (EDT)
:: I think that a welcome phrase, a link to that page and the [[FlightGear wiki:Manual of Style|style manual]] might actually suffice for a welcome template for now.  It is at least better than what we currently have (i.e. more or less nothing).
+
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 14:47, 4 March 2016 (EST)
+
  
:: I now consider
+
== Meta template and templates for commonly used logotypes and icons ==
::* A Welcome message
+
Through a placeholder page (ugh!) and a edit summary Hooray suggested making a template for commonly used logotypes.
::* A link to this page
+
::* A link to the help pages
+
::* A link to the manual of style
+
::* Some final welcoming words
+
  
:: A welcome template should probably also very briefly mention a pet peeve of mine: the categories.
+
{{cquote|placeholder/stub for all sorts of wiki related logos that may need to be updated over time, but that are referenced on multiple pages - so that we don't need to edit each and every page here.|2=[http://wiki.flightgear.org/index.php?title=Template:Logo&oldid=123306 Hooray, 11 April 2020‎, 08:04]}}
:: Many (if not most) image uploaders seem to treat them like tags, but if say all screenshots of aircraft (probably >2000) would end up at [[:Category:Aircraft]] (instead of under a subcategory to [[:Category:Screenshots of aircraft]]), of what use would that page be when looking for a specific one?  If people would like to be able to search for an aircraft, a concise but comprehensive image description is very hard to beat.
+
{{cquote|@Johan: could use your help with this, unless I can write the heuristics in Php or JavaScript ;-)|Hooray, 11 April 2020‎, 08:04}}
:: How do I convey all that in a way that is, short, to the point and easy to absorb (and act by)? And where is the best place?
+
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 02:46, 8 March 2016 (EST)
+
  
:: An early draft is now at [[User:Johan G/Template:Welcome to the wiki]]
+
I would guess you also intend it to be used for icons as well, for example the [[:Category:Ready icons|ready icons]]?  Logotype/icon templates might not be a bad idea.  Less typing is almost always good.
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 02:52, 18 April 2016 (EDT)
+
  
::: Some comments on the draft:
+
{{tl|logo}} should probably be a meta template, a template used by other templates in this case by logotype templates.  Meta templates are pretty common on MediaWiki wikis.
::: * I'm not fully sure about using a prominent box - I think it stands out a bit too much. Wikipedia {{wikipedia|Template:Welcome|uses a simple thread on the Talk page}}; as an alternative, we could use lighter colors.
+
::: * I've also expanded the text a bit. My proposal would be (I've put it in a box, but I'm for the "thread" solution):
+
<div style="background: #fff; border: 1px #585858 solid; padding: 12px; margin: 12px">
+
[[Image:Example.png|left]] '''Welcome to the FlightGear wiki, {{#if: {{{name|}}} | {{{name}}} | {{BASEPAGENAME}}}}'''! We hope you will enjoy your stay!
+
  
See [[Help:Contents#Reading|Reading]] to learn how wikis work. You can also [[Special:CategoryTree/Root category|browse the existing page categories]].
+
Essentially, there could be a set of logotype and icon templates, for example {{tl|Compositor logo}}, {{tl|FGInterface logo}}, {{tl|Air refueling ready icon}} etc, that pass the image for the logotype, an alt text (for accessibility and when the image is not shown, for example due to browser settings) and a link to a relevant wiki page to {{tl|logo}}. Possibly also optional parameters like other sizes etc.  The meta template would then add the boilerplate stuff around that and set the size.
  
Should you wish to create or edit some articles, ''do so''! Here are some resources to get you started:
+
I would advise that having a suffix indicating the type of template, for example ''logo'', ''icon'' like mentioned above or ''navigation'' (for navigation boxes), in essence having less ambiguous names, is generally a good idea.
* [[Help:Contents#Editing|How to edit pages]]
+
* [[Help:Discussion pages|Discussion pages]], where we discuss and agree on potential improvements
+
* [[FlightGear wiki:Manual of Style|The Manual of Style]], a set of guidelines to help editors maintain a consistent style and formatting (please follow them)
+
* [[Help:Contents|Wiki help page]]
+
  
If you have any questions, just start a topic on the [[FlightGear wiki:Village pump|''Discuss!'' page]]. Again, welcome!
+
I should mention that I am generally against placeholder pages.
</div>
+
::: ...where the image on the left is an appropriately chosen icon.
+
::: Finally, we could use the {{mediawiki|Extension:NewUserMessage|NewUserMessage extension}} to have the wiki software automatically post the message to the new user's talk page.
+
::: ---- [[User:Elgaton|ElGaton]] ([[User talk:Elgaton|<tt>talk</tt> to me]]) 17:30, 1 May 2016 (EDT)
+
  
== Permanently removing spam bots ==
+
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 06:44, 12 April 2020 (EDT)
For permanently removing spam bots, has the [https://www.mediawiki.org/wiki/Extension:UserMerge UserMerge] Mediawiki extension been considered?  I use that regularly on [http://wiki.nmr-relax.com my own wiki], though there we have also reverted to communicating to the person via email before manually granting access (probably not an option here), as all of the Mediawiki captcha methods were recently cracked.
+
  
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 03:15, 12 February 2016 (EST)
+
== UTF-8 language pages cannot be edited (cont. from 2015) ==
  
: Oh, for the extension, we simply have a user called 'Spam bot' in a blocked state, and merge the spam bot accounts into this one, deleting the old account.
+
While migrating my own unrelated MediaWiki instance, I may have stumbled upon "a" SQL issue blocking the creation of pages with non-latin characters in their titles. See:
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 03:20, 12 February 2016 (EST)
+
  
:: I'd use the [https://www.mediawiki.org/wiki/Extension:AbuseFilter abuse filter extension] instead (much more powerful and automated) - other users have also proposed different remedies, see [http://forum.flightgear.org/viewtopic.php?f=42&t=28734 this forum thread]. Anyway, Gijs is going to upgrade MediaWiki shortly and review the current anti-spam measures.
+
* [[FlightGear wiki:Village pump/Archive 2015#UTF-8 language pages cannot be edited]]
:: -- [[User:Elgaton|ElGaton]] ([[User talk:Elgaton|<tt>talk</tt> to me]]) 06:26, 13 February 2016 (EST)
+
* [[FlightGear wiki:Village pump/Archive 2016#UTF-8 language pages cannot be edited]]
 +
* [[FlightGear wiki:Village pump/Archive 2019#Language flags on the main page]]
  
::: A lot of the spam bots are using their name as advertising nowadays, so the [https://www.mediawiki.org/wiki/Extension:UserMerge UserMerge] extension is the only one I know which will allow a user and associated name to be permanently deleted.
+
If someone has access to the MySQL backend (command line or phpMyAdmin), could you check what the "Collation" of our database is set to?  For example:
  
::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 12:04, 14 February 2016 (EST)
+
<syntaxhighlight lang="sql">
 +
USE dbname;
 +
SELECT @@character_set_database, @@collation_database;
 +
</syntaxhighlight>
  
:::: The problem now is that they're also adding the information to the page title, so that it will still show up in the deletion logs [http://wiki.flightgear.org/Special:Log/delete] in other words, there's still some SEO juice associated with deleted entries ... Another idea would be to allow admins to temporarily disable wiki registrations/article creation, e.g. if more than 2 admins agree, this could be done to protect the wiki from spam attacks.
+
Or in phpMyAdmin the collation is given in the database listing. My guess is that we are not using UTF-8. That can be changed (after a backup) with:
  
::::: Hooray, you should sign your posts ;)  The bots don't target the deletion logs, as that's a little pointless.  It's a Special:* page, and the default Mediawiki robots.txt file tells all search engines to not index these pages.  User pages, page histories, etc. are however normally indexed.
+
<syntaxhighlight lang="sql">
 
+
ALTER DATABASE dbname CHARACTER SET utf8 COLLATE utf8_general_ci;
::::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 14:36, 19 February 2016 (EST)
+
 
+
:: The point was not what the bots are targeting, but what shows up in the logs - i.e. SEO-wise - Gijs' article blacklist stuff should help with that hopefully. PS: I could not find the signature button on the mobile device I am using, and I am not too good at remembering the correct number of tildes ;-) [[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 15:04, 19 February 2016 (EST)
+
 
+
== WIP vs. Under construction ==
+
I have been beginning to miss the under construction template[http://wiki.flightgear.org/index.php?title=Template:Under_Construction&direction=prev&oldid=46229] more and more (though I could it definitively could be improved).
+
 
+
I have begun to appreciate the need to differentiate between letting readers that a page is to be considered a yet to be finished construction site (though we in a way have that through the {{tl|incomplete}} template) and letting the reader (and other editors) that a page will receive a large amount of work for some hours or even days, usually the use for {{tl|WIP}}.
+
 
+
In summary i miss templates giving a clear distinction between conditions akin to "Under construction" and "Caution - Wet floors", rather than "being worked on" and "could need more work".
+
 
+
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 10:11, 17 February 2016 (EST)
+
 
+
== [[Fr/Pilote automatique]] ==
+
Bonjour,
+
 
+
Je viens de créer la page de traduction en français de l'article original en anglais [[Autopilot]]. Vu mes faibles compétences en matière de pilotage, vu que je n'ai pas sur ma version téléchargée d'avion avec un pilote automatique, la traduction doit souffrir quelques approximations, si ce n'est des contresens plus ennuyeux. Si quelques bonnes âmes plus qualifiées pouvaient me faire la grâce d'une relecture... merci d'avance.
+
 
+
Cordialement, et Hop ! --[[User:F-WTSS|F-WTSS]] ([[User talk:F-WTSS|talk]]) 15:30, 18 February 2016 (EST)
+
 
+
== MediaWiki updated to 1.26.2 ==
+
I've updated MediaWiki to the latest stable release (1.26.2) today. I've still got to update some of the extensions, so there may be regressions for now. Please report bugs if you find any. For a list of changes, see https://www.mediawiki.org/wiki/Release_notes/1.26
+
 
+
[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:47, 19 February 2016 (EST)
+
 
+
: Cheers!  I was hoping that it would solve the uneditable Chinese, Russian, and other non-latin character-based pages (Polish strangely as well), but unfortunately [[FlightGear_wiki:Village_pump/Archive_2015#UTF-8_language_pages_cannot_be_edited|that issue remains]].
+
 
+
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 10:54, 19 February 2016 (EST)
+
 
+
:: Hm, looks that will require quite some attention indeed. I'm afraid that'll has to wait for now.
+
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 12:29, 19 February 2016 (EST)
+
 
+
=== Nasal Syntaxhighlighting ===
+
: Thanks for your efforts, btw: Nasal syntax highlighting is gone again.
+
: {{unsigned|17:22, 19 February 2016‎|Hooray}}
+
 
+
:: Unfortunately this time it isn't me forgetting to copy a file. The SyntaxHighlight extension no longer uses GeSHi, but has switched to Pygments. This means our Nasal mapping no longer works and has to be re-written. If anyone is interested, be my guest. See http://pygments.org/docs/lexerdevelopment/
+
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 12:29, 19 February 2016 (EST)
+
 
+
::: Hi Gijs,
+
::: I'm interested in making a Pygments Nasal lexer, but unfortunately I won't be able to work on it until the end of March at the earliest.
+
::: [[User:Red_Leader|<span style="color:red">'''''Red Leader'''''</span>]] ([[User_talk:Red_Leader|Talk]], [[Special:Contributions/Red_Leader|contribs]]) 16:59, 23 February 2016 (EST)
+
 
+
:::: Unless Gijs is facing any problems, I don't think it's necessarily needed, see my comment/suggestion in this revision: [http://wiki.flightgear.org/index.php?title=FlightGear_wiki:Village_pump&oldid=93166] [[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 17:20, 23 February 2016 (EST)
+
 
+
:::Hi Gijs,
+
:::Here's the code for a Nasal lexer. Be warned, it's thoroughly untested, but has the following features:
+
:::* Full support for all three string types (backtick, single quote, and double quote), including escapes and formatting strings (e.g., for {{func link|sprintf}}).
+
:::* All kinds of numbers, including numbers in scientific notation and octal and hex numbers.
+
:::* All global functions and variables as of FG v2016.1.1.
+
:::* Some of the commonly-used <code>props.Node</code> methods.
+
:::* All the other things that can be expected (keywords, punctuation, etc.).
+
:::I have also created a lexer based on the XML lexer for XML with embedded Nasal, which I thought would be useful.
+
:::Regards,
+
:::[[User:Red_Leader|<span style="color:red">'''''Red Leader'''''</span>]] ([[User_talk:Red_Leader|Talk]], [[Special:Contributions/Red_Leader|contribs]]) 16:35, 2 April 2016 (EDT)
+
 
+
:::http://pygments.org/docs/lexerdevelopment/#adding-and-testing-a-new-lexer
+
:::<syntaxhighlight lang="python" enclose="div">
+
# -*- coding: utf-8 -*-
+
"""
+
Lexer for Nasal.
+
"""
+
 
+
from pygments.lexer import RegexLexer, words, include, inherit, bygroups, using
+
from pygments.token import Text, Keyword, Name, String, Number, Operator, Punctuation, Comment
+
from pygments.lexers.html import XmlLexer
+
 
+
__all__ = ['NasalLexer', 'XMLNasalLexer']
+
 
+
class NasalLexer(RegexLexer):
+
 
+
name = 'Nasal'
+
aliases = ['nasal']
+
filenames = ['*.nas']
+
 
+
tokens = {
+
'formatters': [
+
(r'%[-#0 +]*(?:[0-9]+)?(?:\.[0-9]+)?[dis%couxXeEfFgG]', String.Interpol),
+
],
+
'backtick': [
+
(r'`', String.Backtick, '#pop'),
+
(r'[^`\\]+', String.Backtick),
+
(r'\\n|\\r|\\t|\\`|\\\\|\\x[0-9a-fA-F]{2}', String.Escape),
+
],
+
'sqstring': [
+
(r"'", String.Single, '#pop'),
+
(r"[^'\\%]+", String.Single),
+
(r"\\'", String.Escape),
+
include('formatters'),
+
],
+
'dqstring': [
+
(r'"', String.Double, '#pop'),
+
(r'[^"\\%]+', String.Double),
+
(r'\\n|\\r|\\t|\\"|\\\\|\\x[0-9a-fA-F]{2}', String.Escape),
+
include('formatters'),
+
],
+
'root': [
+
(r'\s+', Text),
+
(r'#.*?$'m, Comment.Single),
+
(r':|\?|[!=<>+\-*\/~&|^]=?', Operator),
+
(words(('or', 'and'), suffix=r'\b'), Operator.Word),
+
(r'[{(\[})\]\.;,]', Punctuation),
+
(words(('for', 'foreach', 'forindex', 'while', 'break', 'return', 'continue', 'if', 'else', 'elsif'), suffix=r'\b'), Keyword),
+
(words(('var', 'func'), suffix=r'\b'), Keyword.Declaration),
+
(words(('nil'), suffix=r'\b'), Keyword.Constant),
+
(words(('me', 'arg'), suffix=r'\b'), Name.Builtin.Pseudo),
+
(words(('new', 'del', 'getNode', 'getParent', 'getChild', 'getChildren', 'removeChild', 'removeChildren', 'removeAllChildren', 'getName', 'getIndex', 'getType', 'getAttribute', 'setAttribute', 'getValue', 'setValue', 'setIntValue', 'setBoolValue', 'setDoubleValue', 'unalias', 'alias', 'getPath', 'getBoolValue', 'remove', 'setValues', 'getValues', 'initNode'), suffix=r'\b'), Keyword.Pseudo),
+
(r'0o[0-7]+', Number.Oct),
+
(r'0x[0-9a-fA-F]+', Number.Hex),
+
(r'\d*(?:\.\d*)?[eE][+-]?\d+', Number.Float),
+
(r'\d*\.\d*', Number.Float),
+
(r'\b[0-9]+\b', Number.Integer),
+
(words(('D2R', 'R2D', 'FT2M', 'M2FT', 'IN2M', 'M2IN', 'NM2M', 'M2NM', 'KT2MPS', 'MPS2KT', 'FPS2KT', 'KT2FPS', 'LB2KG', 'KG2LB', 'GAL2L', 'L2GAL'), suffix=r'\b'), Name.Variable.Global),
+
(words(('abort', 'abs', 'addcommand', 'airportinfo', 'airwaysRoute', 'assert', 'carttogeod', 'cmdarg', 'courseAndDistance', 'createViaTo', 'createDiscontinuity', 'createWP', 'createWPFrom', 'defined', 'directory', 'fgcommand', 'findAirportsByICAO', 'findAirportsWithinRange', 'findFixesByID', 'findNavaidByFrequency', 'findNavaidsByFrequency', 'findNavaidsByID', 'findNavaidsWithinRange', 'finddata', 'flightplan', 'geodinfo', 'geodtocart', 'getprop', 'greatCircleMove', 'interpolate', 'isa', 'logprint', 'magvar', 'maketimer', 'md5', 'navinfo', 'parse_markdown', 'parsexml', 'print', 'printf', 'printlog', 'rand', 'registerFlightPlanDelegate', 'removecommand', 'removelistener', 'resolvepath', 'setlistener', 'setprop', 'settimer', 'srand', 'systime', 'thisfunc', 'tileIndex', 'tilePath', 'values'), suffix=r'\b'), Name.Builtin),
+
(words(('append', 'bind', 'call', 'caller', 'chr', 'closure', 'cmp', 'compile', 'contains', 'delete', 'die', 'find', 'ghosttype', 'id', 'int', 'keys', 'left', 'num', 'pop', 'right', 'setsize', 'size', 'sort', 'split', 'sprintf', 'streq', 'substr', 'subvec', 'typeof'), suffix=r'\b'), Name.Builtin),
+
(words(('_createCondition', '_fgcommand', '_interpolate', '_setlistener'), suffix=r'\b'), Keyword.Reserved),
+
(r'`', String.Backtick, 'backtick'),
+
(r"'", String.Single, 'sqstring'),
+
(r'"', String.Double 'dqstring'),
+
(r'\b_\w*?\b', Keyword.Reserved),
+
#(r'\b\w*?\b', Name),
+
]
+
}
+
 
+
class XMLNasalLexer(XmlLexer):
+
"""
+
For Nasal code embedded in XML files.
+
"""
+
 
+
name = 'XML-Nasal'
+
aliases = ['xml-nasal', 'xml-ns']
+
 
+
tokens = {
+
'root': [
+
(r'(<(?:load|unload|script)>)(<!\[CDATA\[)?(.*?)(]]>)?(</(?:load|unload|script)>)', bygroups(Name.Tag, Comment.Preproc, using(NasalLexer), Comment.Preproc, Name.Tag),
+
inherit,
+
],
+
}
+
 
</syntaxhighlight>
 
</syntaxhighlight>
  
:: We can use the ECMAScript/JavaScript lexer[http://pygments.org/docs/lexers/#lexers-for-javascript-and-related-languages] for now, my suggestion would be to copy that over to a file so that we can work on a custom Nasal lexer (Syntax  is almost identical, with a few different keywords, and many others being irrelevant). What is missing/different can be obtained from other lexers that are similar, e.g. [http://pygments.org/docs/lexers/#lexers-for-other-c-like-languages] [[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 15:45, 19 February 2016 (EST)
+
Or in phpMyAdmin, select the databse of this wiki, click on the "Operations" tab, in the "Collation" box select "utf8_general_ci", and finally click on "Go".  Hopefully this is the cause of this long standing and painful issue.
 
+
:: Okay, here's the better/quick&easy way: We have Nasal support for some fairly popular editors, like [http://wiki.flightgear.org/Howto:Syntax_highlighting_for_Nasal#Vim|vim](originally created by Melchior<ref>https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/scripts/syntax/nasal.vim</ref>), listed at [[Howto:Syntax_highlighting_for_Nasal]] - there are various free converters available that will read such a syntaxhighlighting file and convert it to a pygments class, e.g. see: https://github.com/honza/vim2pygments [[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 16:00, 19 February 2016 (EST)
+
 
+
==== References ====
+
<references />
+
 
+
== The repository link templates ==
+
=== Complete overhaul of the repository link templates ===
+
 
+
I have now performed a complete overhaul of the repository link templates (see {{tl|repo link/doc related}}).  This was motivated by the incomplete state of these templates, the lack of standardisation, the lack of SourceForge git repository support for {{tl|repo link}}, web-interface only support, etc.  I have used a lot of recursive transclusion for standardisation, so that there is a single point for updating for any FlightGear infrastructure changes.  This is the master {{tl|repo link}} template.  All the other templates are subtemplates which recursively transclude from this master template.  I have also created a number of documentation templates for simplifying template maintenance (see {{tl|repo link/doc related‎}}, {{tl|repo link/doc specific file git‎‎}}, {{tl|repo link/doc git clone‎‎}}, and {{tl|repo link/doc commit}}).  The changes were constrained to maintain backwards compatibility as much as possible.  However I would like to break this to allow the following templates to be updated to transclude from the master {{tl|repo link}} template:
+
 
+
* {{tl|flightgear file}},
+
* {{tl|simgear file}},
+
* {{tl|fgdata file}},
+
* {{tl|fgaddon file}}.
+
 
+
If no one objects, I would like to completely break these and expand and rename the parameter set to match the other <nowiki>{{* file}}</nowiki> repository templates (e.g. {{tl|terragear file}}).  My overhaul currently does not include Hooray's ideas for non command line usages, i.e. different GUIs, but it enables it to be easily added via the master template and the addition of a single parameter to any subtemplates.
+
 
+
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 15:05, 25 February 2016 (EST)
+
 
+
: I don't have any objections myself, I appreciate all the work you are putting into this, and would like to thank you for helping us clean up all that mess by doing such unglamorous work ;-) I also appreciate that your changes would facilitate adding a non-CLI mode to the corresponding templates. However, I would suggest to wait for Gijs' feedback, because he's ultimately the most likely person to veto something around here ;-) [[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 17:31, 25 February 2016 (EST)
+
 
+
:: Johan seems to be the one who did a lot of the initial work on these <nowiki>{{* file}}</nowiki> templates, and Red Leader with the {{tl|repo link}} template.  And they were involved in the general discussions ([[http://wiki.flightgear.org/index.php?title=FlightGear_wiki:Village_pump&oldid=87148#Repository_link_templates perm]).  But I know Gijs was also involved in the design.
+
 
+
:: For the non-CLI mode, that will need -a lot- more planning.  For example a definitive list of all these modes would be useful.  Should this use an optional Mediawiki pop up extension showing a link to a general page that describes the action for all different GUIs, CLI, etc.?  Should we have a switch box so that the reader can switch in-text between CLI, and the numerous GUIs?  Are we going to have a large set of screenshots for each GUI?  If so, I would strongly recommend the [https://www.mediawiki.org/wiki/Extension:Labeled_Section_Transclusion labelled section transclusion extension] for creating a single page for one GUI with everything for that GUI, as a tutorial.  Here is [http://wiki.nmr-relax.com/Relax_4.0.1 an external example where I have used this], to fragment the base release page to create [http://wiki.nmr-relax.com/Relax_release_descriptions this meta page], as well as many other meta pages.
+
 
+
:: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 03:14, 26 February 2016 (EST)
+
 
+
I am also thinking of changing the name of the <nowiki>{{* file}}</nowiki> templates, as I hope to make the scope of the templates far more general.  The name <nowiki>{{* source}}</nowiki> or <nowiki>{{* repo}}</nowiki> might be better.  For example these will allow the repository commit, tree view, log view (and maybe rss feed), with or without a file/directory path.  And I would like to generalise this to handle both the SF web-interface and non-web net protocols (git://, ssh://, svn://, etc.).  It will allow for CLI instructions to be built up and embedded in <nowiki>{{#tag:source|<content>|lang=sh}}</nowiki> tags.  And I will defer all infrastructure decisions in the subtemplates to the single point of {{tl|project infrastructure}}, so that if there are changes in the future, then only this single template needs to be updated to update the entire wiki.
+
 
+
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 03:22, 26 February 2016 (EST)
+
 
+
: The {{tl|project infrastructure}} template as a single point provider of various project infrastructure names and URL pairs seem like a great idea.  If it work out well it will really lessen the maintenance by having less places needing updates, while allowing the various repository templates to be simple to use, in essence by having comprehensible names and no boiler plate parameters for their users.
+
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:15, 27 February 2016 (EST)
+
 
+
==== Repository link update ====
+
For those following, I have massively expanded the capabilities of the {{tl|repo link}} template:
+
* The SourceForge URLs are now comprehensive.
+
* Full support for the new query-based URLs for the Gitorious archives.
+
* Functional GitLab URLs.
+
* Generic repository support (used to create the {{tl|openscenegraph co}} template).
+
* Detailed documentation and extensive examples for checking the implementation (if you find any non-supported links, please add these as examples).
+
* Isolation of the '''cmd''' parameter from the CLI options &mdash; this is to enable future support for non-CLI instructions based on the value of '''cmd'''.
+
 
+
I have also completed a large set of subtemplates of {{tl|repo link}}, see the list at {{tl|repo link/doc related}}.  This includes a full set of <nowiki>{{* source}}</nowiki> templates.  I have left the original <nowiki>{{* file}}</nowiki> templates, rather than renaming and modifying them, so these are now redundant.  All of the <nowiki>{{* source}}</nowiki>, <nowiki>{{* commit}}</nowiki>, <nowiki>{{* clone}}</nowiki>, and <nowiki>{{* co}}</nowiki> templates transclude from the master {{tl|repo link}} template to do all of the work.
+
 
+
One important template is {{tl|gitorious source}}.  The support for the new query-based URLs for the Gitorious archives is now quite comprehensive in {{tl|repo link}}.  Therefore I have converted almost every single FlightGear wiki link to https://gitorious.org to use {{tl|gitorious source}} instead.  This fixes a lot of broken links and broken git instructions.  I have reduced the number of hits for gitorious.org on the wiki (searching just for "gitorious") to 22 hits.  This includes 2 very outdated articles ([[FlightGear Git: aircraft authors]], [[Fr/FlightGear et Git]]), 15 locked newsletters, 1 with no longer existent Gitorious merge request links, and 4 base URL links for Hangars.  This way we can maintain the Gitorious web interface links and git command instructions in a functional state by simply updating the single source of {{tl|repo link}}.
+
 
+
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 11:38, 29 February 2016 (EST)
+
 
+
: I just remembered [[Special:LinkSearch]], so make that 184 broken gitorious.org links remaining.  Lots more work to do :)
+
 
+
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 14:46, 29 February 2016 (EST)
+
 
+
For some of these templates, e.g. {{tl|repo link/doc usage}}, I'm trying to implement some logic for automatic whitespace padding for documentation formatting, but the <code><nowiki>{{#len:string}}</nowiki></code> function is not enabled.  According to {{mediawiki|Wikitext_parser/Core_parser_functions#.23len}} and {{mediawiki|Extension:StringFunctions}}, the option <code>$wgPFEnableStringFunctions = true;</code> should be set (in <code>LocalSettings.php</code>).  Unless there is a reason for not using this, I was wondering if someone could enable this?  Cheers!
+
 
+
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 09:53, 8 March 2016 (EST)
+
 
+
=== Archived newsletters and dead links? ===
+
 
+
Do we have a policy for the dead links in the FlightGear newsletters?  It is obviously good to preserve the historic state.  But there are many Gitorious links that could be made functional again using the {{tl|gitorious source}} template to point to the historic Gitorious archives (including the official FlightGear repositories, rather than using {{tl|fgdata source}}, for example).  The https://gitorious.org links have been converted from URL/path based to query based, so absolutely all of the old links are broken.  I am steadily converting all Gitorious links to use the [[Template:repo link/doc related|{{obr}}repo link{{cbr}} family of templates]], with the exception of the newsletters.
+
 
+
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 04:52, 8 March 2016 (EST)
+
 
+
: I think it could be a good idea to try update old links in those newsletters.  I sometimes look back at things and tend to think that I probably are not the only one doing that.
+
: I wonder if the rotten links should be replaced or stricken, but I think they could just as well be replaced.  The key thing is that they go to the same resource or content, not weather they have been updated or not (also, the change will be visible in the revision history after all).
+
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 07:11, 8 March 2016 (EST)
+
 
+
:: I should add that I'm using [http://wiki.flightgear.org/index.php?title=Special:LinkSearch&limit=500&offset=0&target=http%3A%2F%2Fgitorious.org <nowiki>Special:LinkSearch for http://gitorious.org</nowiki>] and [http://wiki.flightgear.org/index.php?title=Special:LinkSearch&limit=500&offset=0&target=https%3A%2F%2Fgitorious.org <nowiki>Special:LinkSearch for https://gitorious.org</nowiki>].  And I am also not touching the <code>User*</code> pages, <code>*talk*</code> pages, or pages tagged as out of date or up for deletion.  For the newsletters I might look at these later when the broken Gitorious links are fixed in the rest of the wiki but, as these are locked, someone else might have make the switch to {{tl|gitorious source}}, {{tl|gitorious url}}, {{tl|gitorious clone}}, and {{tl|gitorious merge request}}.
+
 
+
:: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 02:53, 9 March 2016 (EST)
+
 
+
::: I will temporarily add a table here for the templates in the newsletters and will slowly fix them one by one together with any other admin.
+
{{navbox
+
| title = Click "show" to show -->
+
| state = collapsed
+
| navbar = plain
+
| list1 =
+
http:...
+
{{{!}} class="wikitable"
+
! Fixed !! Newsletter !! Gitorious URL !! Notes
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter May 2010]]
+
{{!}} http://gitorious.org/fg
+
{{!}} No equivalent link for the Gitorious archive - project pages are dead.  Maybe just use http://gitorious.org/?
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[Es/FlightGear Newsletter May 2010]]
+
{{!}} http://gitorious.org/fg
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter September 2010]]
+
{{!}} http://gitorious.org/fg/flightgear/commit/5c6fe952598053fa63631fc0161d666f22a50f51
+
{{!}} Functional link, equivalent to {{gitorious url|fg|flightgear|commit=5c6fe952598053fa63631fc0161d666f22a50f51}}.
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[Es/FlightGear Newsletter September 2010]]
+
{{!}} http://gitorious.org/fg/flightgear/commit/5c6fe952598053fa63631fc0161d666f22a50f51
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter January 2011]]
+
{{!}} http://gitorious.org/jsbsim/jsbsim
+
{{!}} Functional link.  Switched to {{gitorious url|jsbsim|jsbsim}} to future-protect the link.
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[Es/FlightGear Newsletter January 2011]]
+
{{!}} http://gitorious.org/jsbsim/jsbsim
+
{{!}} Functional link.  Switched to {{gitorious url|jsbsim|jsbsim}} to future-protect the link.
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter February 2011]]
+
{{!}} http://gitorious.org/headtrack
+
 
+
http://gitorious.org/arduinocockpit
+
{{!}} Project pages are dead, switched to {{gitorious url|headtrack|headtrack}}
+
 
+
{{gitorious url|arduinocockpit|arduinocockpit}}
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[Es/FlightGear Newsletter February 2011]]
+
{{!}} http://gitorious.org/arduinocockpi
+
 
+
http://gitorious.org/headtrack
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter March 2011]]
+
{{!}} http://gitorious.org/lockheed-l10-electra
+
{{!}} Missing project - i.e. {{gitlab source|user=emilianh|repo=Lockheed-L10-Electra|text=migrated to GitLab}}.  Switched to {{gitlab source|user=emilianh|repo=Lockheed-L10-Electra}}.
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[Es/FlightGear Newsletter March 2011]]
+
{{!}} http://gitorious.org/lockheed-l10-electra
+
{{!}} Switched to {{gitlab source|user=emilianh|repo=Lockheed-L10-Electra}}.
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter November 2011]]
+
{{!}} http://gitorious.org/flightgear-aircraft
+
{{!}} Switched to {{gitorious source}} and rephrased text slightly to help readers find the repositories.
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter October 2012]]
+
{{!}} http://gitorious.org/anders-hangar/mtb_20m/trees/master
+
{{!}} Switch to {{gitorious url|proj=anders-hangar|repo=mtb_20m}}
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter March 2013]]
+
{{!}} http://gitorious.org/fg/flightgear/blobs/next/scripts/java/FGClient/src/FGFSDemo.java
+
{{!}} Switched to {{gitorious url|proj=fg|repo=flightgear|path=scripts/java/FGClient/src/FGFSDemo.java}}.  This points to the old Gitorious repository to protect against path changes in the future.
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter September 2013]]
+
{{!}} http://gitorious.org/boeing/707
+
{{!}} Switched to {{gitorious source|proj=boeing|repo=707}}
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[Es/FlightGear Newsletter September 2013]]
+
{{!}} http://gitorious.org/boeing/707
+
{{!}} Switched to {{gitorious source|proj=boeing|repo=707}}
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter November 2013]]
+
{{!}} http://gitorious.org/fg/fgrun
+
{{!}} Switch to {{gitorious url|proj=fg|repo=fgrun}}
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[Es/FlightGear Newsletter November 2013]]
+
{{!}} http://gitorious.org/fg/fgrun
+
{{!}} Switch to {{gitorious url|proj=fg|repo=fgrun}}
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter July 2014]]
+
{{!}} http://gitorious.org/nasal-support/nasal-npp
+
{{!}} Switched to {{gitorious url|nasal-support|nasal-npp}}
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter April 2015]]
+
{{!}} http://gitorious.org
+
{{!}} Switched to {{tl|gitorious source}} without parameters for the Gitorious base URL, to future-protect it.
+
{{!}}}
+
 
+
https:...
+
{{{!}} class="wikitable"
+
! Fixed !! Newsletter !! Gitorious URL !! Notes
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter April 2011]]
+
{{!}} https://gitorious.org/papillon81/flightgear-custom-scenery/
+
 
+
https://gitorious.org/dvanmosselbeen/flightgear-custom-scenery
+
{{!}} Switched to {{gitorious source|dvanmosselbeen|flightgear-custom-scenery}} and {{gitorious source|papillon81|flightgear-custom-scenery}}
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[Es/FlightGear Newsletter April 2011]]
+
{{!}} https://gitorious.org/dvanmosselbeen/flightgear-custom-scenery
+
 
+
https://gitorious.org/papillon81/flightgear-custom-scenery/
+
{{!}} Switched to {{gitorious source|dvanmosselbeen|flightgear-custom-scenery}} and {{gitorious source|papillon81|flightgear-custom-scenery}}
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter July 2011]]
+
{{!}} https://gitorious.org/dvanmosselbeen/flightgear-custom-scenery
+
{{!}} Switched to {{gitorious source|dvanmosselbeen|flightgear-custom-scenery}}
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[Es/FlightGear Newsletter July 2011]]
+
{{!}} https://gitorious.org/dvanmosselbeen/flightgear-custom-scenery
+
{{!}} Switched to {{gitorious source|dvanmosselbeen|flightgear-custom-scenery}}
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter December 2011]]
+
{{!}} https://gitorious.org/dvanmosselbeen/flightgear-custom-scenery
+
{{!}} Switched to {{gitorious source|dvanmosselbeen|flightgear-custom-scenery}}
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[Fr/Nouvelles du projet FlightGear - décembre 2011]]
+
{{!}} https://gitorious.org/dvanmosselbeen/flightgear-custom-scenery
+
{{!}} Switched to {{gitorious source|dvanmosselbeen|flightgear-custom-scenery}}
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter April 2012]]
+
{{!}} https://gitorious.org/fg/fgdata/blobs/master/Aircraft/Instruments-3d/garmin196/README
+
 
+
https://gitorious.org/fg/fgdata/blobs/master/Aircraft/Instruments-3d/garmin196/doc/doc-en.htm
+
{{!}} Switched to {{fgdata source|path=Aircraft/Instruments-3d/garmin196/README|full=1}} and {{fgdata source|path=Aircraft/Instruments-3d/garmin196/doc/doc-en.htm|full=1}} to point to the current FGData locations and removed the name "Gitorious" to make the text of the Garmin 196 GPS section still relevant
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter August 2012]]
+
{{!}} https://gitorious.org/mil-mi-6
+
{{!}} Switched to {{gitorious url|proj=mil-mi-6|repo=mi6dev}}, and changed from the non-existent project page to the main repository.
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter October 2012]]
+
{{!}} https://gitorious.org/fgradar
+
{{!}} Switched from the project page to the direct repository {{gitorious url|fgradar|fgradar}}.
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter March 2013]]
+
{{!}} https://gitorious.org/fg/flightgear/commit/913727239d6776c0508d206f395e16c265413ec3
+
 
+
https://gitorious.org/fg/flightgear/commit/eba03b5e469824ee8f1494723fcddbbc56155a08
+
{{!}} Switched to {{flightgear url|commit=913727239d6776c0508d206f395e16c265413ec3}} and {{flightgear url|commit=eba03b5e469824ee8f1494723fcddbbc56155a08}}This deliberately points to the current repository.
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter April 2013]]
+
{{!}} https://gitorious.org/fg-radi/osm2city
+
 
+
https://gitorious.org/scenery-france-850
+
{{!}} Switched to the new GitLab repository {{gitlab source|proj=fg-radi|repo=osm2city|full=1}}
+
 
+
and removed the no longer existent scenery-france-850 repository, replacing it with "<s>Scenery repository (Gitorious)</s>".
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter October 2013]]
+
{{!}} https://gitorious.org/fg/galvedros-fgdata
+
{{!}} Switch to {{gitorious url|proj=fg|repo=galvedros-fgdata}}
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[Es/FlightGear Newsletter October 2013]]
+
{{!}} https://gitorious.org/fg/galvedros-fgdata
+
{{!}} Switch to {{gitorious url|proj=fg|repo=galvedros-fgdata}}
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter November 2013]]
+
{{!}} https://gitorious.org/ec130/
+
{{!}} Switched from the project page to the direct repository {{gitorious source|ec130|ec130}}.
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[Es/FlightGear Newsletter November 2013]]
+
{{!}} https://gitorious.org/ec130/
+
{{!}} Switched from the project page to the direct repository {{gitorious source|ec130|ec130}}.
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter February 2014]]
+
{{!}} https://gitorious.org/fg/philosophers-fgdata/source/022bef27f05d4837d720f63c6507b47466ff2a59:Nasal/console/repl.nas#L436
+
 
+
https://gitorious.org/fg/philosophers-fgdata/source/nasal-console:Nasal/console
+
 
+
https://gitorious.org/fg/fgdata/commit/eaaf816b772649d5b0826a1d0bdd166dbc5b968f
+
 
+
https://gitorious.org/fg/flightgear/commit/34ed79e5f88ffdfc5e651a1fe3e639cb8f4d3353
+
 
+
https://gitorious.org/fg/flightgear/commit/5eee5e42ae4f5cf56283b3bf5a3be46efc2b51c4
+
 
+
https://www.gitorious.org/fg/flightgear/merge_requests/26
+
{{!}} Switched to {{gitorious source|proj=fg|repo=philosophers-fgdata|branch=nasal-console|path=Nasal/console/repl.nas|line=708}}
+
 
+
{{gitorious url|proj=fg|repo=philosophers-fgdata|branch=nasal-console|path=Nasal/console|view=tree}}
+
 
+
{{fgdata-old url|commit=eaaf816b772649d5b0826a1d0bdd166dbc5b968f}}
+
 
+
{{flightgear commit|34ed79e5f88ffdfc5e651a1fe3e639cb8f4d3353}}
+
 
+
{{gitorious merge request|mr=54}}
+
 
+
{{gitorious merge request|mr=26}}
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[Es/FlightGear Newsletter February 2014]]
+
{{!}} https://gitorious.org/fg/philosophers-fgdata/source/022bef27f05d4837d720f63c6507b47466ff2a59:Nasal/console/repl.nas#L436
+
 
+
https://gitorious.org/fg/philosophers-fgdata/source/nasal-console:Nasal/console
+
 
+
https://gitorious.org/fg/fgdata/commit/eaaf816b772649d5b0826a1d0bdd166dbc5b968f
+
 
+
https://gitorious.org/fg/flightgear/commit/34ed79e5f88ffdfc5e651a1fe3e639cb8f4d3353
+
 
+
https://gitorious.org/fg/flightgear/commit/5eee5e42ae4f5cf56283b3bf5a3be46efc2b51c4
+
 
+
https://www.gitorious.org/fg/flightgear/merge_requests/26
+
{{!}} Changes match the English article.
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter April 2014]]
+
{{!}} https://gitorious.org/fg/fgdata/flightgear?p=fg/fgdata:flightgear.git;a=blob;f=keyboard.xml
+
 
+
https://gitorious.org/fg/fgdata?p=fg:fgdata.git;a=commit;h=f8c56dcc52ffd3d6dfca1d39dc4a72b6b3478368
+
 
+
https://gitorious.org/fg/hoorays-flightgear?p=fg:hoorays-flightgear.git;a=shortlog;h=refs/heads/topics/cppbind-fgprotocol
+
{{!}} This first link was the broken {{tl|git link}} template (see the table below).  The other two links are not in the article?!
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter June 2014]]
+
{{!}} https://gitorious.org/eddp-custom-scenery/eddp-custom-scenery/
+
{{!}} Switched to {{tl|gitorious clone}} to provide functional '''git clone''' instructions.
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter November 2014]]
+
{{!}} https://gitorious.org/fg/hoorays-fgdata/source/2857d8fc9fcfe2bb162a9eb9d3dcca4d41b3a876:Nasal/ai/aim9/aim9.fdm#L9
+
{{!}} Switch to {{gitorious url|proj=fg|repo=hoorays-fgdata|commit=2857d8fc9fcfe2bb162a9eb9d3dcca4d41b3a876|path=Nasal/ai/aim9/aim9.fdm|line=9}}
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter January 2015]]
+
{{!}} https://gitorious.org/fg/canvas-hackers-fgdata/source/f59c42134a5a77e343981dcff8278c3e2f094e87
+
{{!}} Switch to {{gitorious url|proj=fg|repo=canvas-hackers-fgdata|commit=f59c42134a5a77e343981dcff8278c3e2f094e87|view=summary}}
+
{{!}}}
+
 
+
Broken templates:...
+
{{{!}} class="wikitable"
+
! Fixed !! Newsletter !! Template !! Notes
+
{{!-}}
+
{{!}} {{tick}}
+
{{!}} [[FlightGear Newsletter April 2014]]
+
{{!}} {{tlx|Git link|gitorious|fg/fgdata|master|keyboard.xml|pre=$FG_ROOT/}}
+
{{!}} Switched to {{fgdata source|path=keyboard.xml|pre=$FG_ROOT}} to fix the Gitorious link created by the broken and depreciated {{tl|git link}} template.
+
{{!}}}
+
 
+
}}
+
 
+
::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 12:06, 9 March 2016 (EST)
+
 
+
:::: I've added a '''notes''' column to help a little.
+
 
+
:::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 12:30, 9 March 2016 (EST)
+
 
+
=== Elimination of the dead Gitorious links ===
+
Thanks largely to the diversity and flexibility of the [[:Category:Repository link templates|{{obr}}repo link{{cbr}} family of templates]], I have now managed to eliminate almost every last dead Gitorious link in the FlightGear wiki!  The locked Newsletter articles, user pages, and talk pages are the only exceptions.  The page counts from the (Main) namespace are:
+
* [http://wiki.flightgear.org/index.php?target=http%3A%2F%2Fgitorious.org&namespace=0&title=Special%3ALinkSearch <nowiki>Special:LinkSearch for http://gitorious.org</nowiki>] &mdash; 37.  Of these, 17 are for the front page with the news of the Gitorious to SourceForge migration, and the rest are Newsletters.
+
* [http://wiki.flightgear.org/index.php?title=Special:LinkSearch&limit=500&offset=0&target=https%3A%2F%2Fgitorious.org&namespace=0 <nowiki>Special:LinkSearch for https://gitorious.org</nowiki>] &mdash; 166.  Most of these links are valid and created by the {{obr}}gitorious *{{cbr}} subtemplates of {{tl|repo link}}.  The remaining broken links are all in the locked Newsletters.
+
The Howto:* pages are not in the (Main) wiki namespace, but I've knocked those out too.
+
 
+
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 13:54, 10 March 2016 (EST)
+
 
+
: thanks for doing all this unglamorous work - I am sorry that Gijs was apparently too busy to follow up on my suggestion to either provide you with admin access around here, or at least to help you run a Python script to do all this work in an automated, rather than manual, fashion. Hopefully, things will work out better next time. Again, thank you. Like I said, I think you should definitely be given admin access on the wiki, especially given your recent contributions - and I would gladly have my wiki status downgraded accordingly. In fact, if I was able to directly promote accounts accordingly, I would have done so months ago - however, it seems that Gijs is the only one to have those privileges, and he mentioned off-list that he's kinda busy with RL/exams etc, so it is to be expected that he's going to become a bottleneck more often - hopefully, this will be recongized as an actual issue, so that there will be more people able to promote new wiki admins. Sorry that things didn't work out better this time, and thanks so much for doing all this stuff manually. -[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 14:49, 10 March 2016 (EST)
+
 
+
:: No problems!  As for automating this, that would not have been possible.  If you look at the changes, you'll see that each one is different <sup>[http://wiki.flightgear.org/index.php?title=Special:RecentChanges&to=20160310210655&limit=500]</sup>.  I had to check each one, and update the link as required.
+
 
+
:: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 16:08, 10 March 2016 (EST)
+
 
+
::: There's three of us actually (Curt, Simon and myself), no need to wait on me. See http://wiki.flightgear.org/index.php?title=Special%3AListUsers&username=&group=bureaucrat&limit=100 (Sek is inactive nowadays) ;-)
+
::: Please note that forum pms are really not the best way to contact me. I very much prefer email over forum pms as it's a lot easier to filter out the huge amounts of nonsense I'm receiving from stuff requiring actual attention.
+
::: Anyhow I've just  promoted Bugman so he can edit locked articles.
+
::: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 05:06, 11 March 2016 (EST)
+
 
+
:::: Thank you.  I'll try to preserve the original intent of the Newsletters while fixing the broken links (maybe even preserving any original URLs as Mediawiki link text, while pointing to the new URL).  I will use the {{obr}}gitorious *{{cbr}} templates to point to the historical sources, and will probably use this for all of the Gitorious URLs so that we have full control over any future URL breakages via the single location of {{tl|repo link}}.  For example, if they change the gitorious.org domain name to a https://archive.org subdomain (i.e. gitorious.archive.org).
+
  
:::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 06:40, 11 March 2016 (EST)
+
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 03:33, 9 September 2020 (EDT)
  
=== Regex parsing of template parameters? ===
+
: Hi Edward,
 +
: I somehow missed all these previous reports :-( Sorry!
 +
: You're right. The database is in latin1. We're actually currently in the process of migrating some of our server work and updating. I will take care of setting the correct collation on that occasion.
 +
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 04:24, 9 September 2020 (EDT)
  
For the {{tl|repo link}} template, I am currently trying to work out what to do for git branches and tags on the SourceForge infrastructureThe problem is that the presence of the character <code>/</code> within a branch or tag name requires the text <code>/~</code> to be appended to that name in the URL, for example:
+
:: Great, that sounds exactly like this problem.  Only pages with 'latin1' characters in their names can be edited.  I really hope switching the collation to UTF-8 will fix the problemThere must have been a MySQL server migration many years ago where the old database was UTF-8 and the import automatically changed the language to the server default of 'latin1', as many pages were created on this wiki with non-latin1 characters in the past.  I see this with my MySQL database too - I have to switch back to UTF-8 after import into the new SQL database.
  
* Tag <code>version/2016.1.1</code>: https://sourceforge.net/p/flightgear/simgear/ci/version/2016.1.1/~/tree/simgear/ephemeris/ephemeris.cxx
+
:: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 06:00, 9 September 2020 (EDT)
* Branch <code>release/2016.1</code>: https://sourceforge.net/p/flightgear/simgear/ci/release/2016.1/~/tree/simgear/ephemeris/ephemeris.cxx
+
  
I haven't found out a way to use regex to parse the <code>tag</code> or <code>branch</code> template parameters to automate this, hence I am thinking of just giving the instruction for the template user to append this text to the <code>tag</code> or <code>branch</code> parameter text themselves.  However this is not ideal - a change of this behaviour on the SourceForge side requires end pages with SourceForge URLs to be updated, rather than just updating {{tl|repo link}}. I was wondering about possibility of installing the extension:
+
== Needing an extra pair of eyes ==
 +
There is a problem with automatic categorization in {{tl|Autoflight Navigation}} that I can not seem to solve.
  
* [https://www.mediawiki.org/wiki/Extension:RegexParserFunctions Extension:RegexParserFunctions]
+
For details see [[Template talk:Autoflight Navigation#Automatic categorization seem broken]].
  
Though I'm not 100% sure if that will work.  Or does someone else know an alternative?  Cheers!
+
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 10:26, 10 September 2020 (EDT)
  
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 12:09, 22 April 2016 (EDT)
+
: All done!  In summary, the {{tl|howto other}} template logic was completely broken and was operating as the {{tl|main other}} template instead!  Checking if the {{obr}}NAMESPACE{{cbr}} is set to {{obr}}ns:0{{cbr}} is not how you check for the "Howto" namespace.  As I don't know the numeric value of this namespace, I switched to comparing {{obr}}NAMESPACE{{cbr}} to the simple string 'Howto'.  So the template is now fixed.  We should see a lot of auto-categorisation additions and fixes now.  I also switched {{tl|Autoflight Navigation}} to use {{tl|namespace detect}} to simplify its logic.
  
: not a solution, just a potential workaround would be checking for the most common prefix strings used in tags/branches (e.g. version, release, topic, topics) and explicitly rewrite the URL accordingly to append the /~ suffix -[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 12:59, 22 April 2016 (EDT)
+
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 06:14, 11 September 2020 (EDT)
  
:: That might be a solutionBut I don't know how to do that without regex ;)  We really only have #ifeq statements, but that has to match the whole string.
+
:: Thank you som much for fixing that. :-)
 +
:: Did not think of comparing the namespace numbers between the templates.
 +
:: I was wondering where I found the numbers, but could not quite rememberIf I figure it out I will probably add the source for those at a suitable place, like under ''Technical details'' in ducumentation for {{tl|namespace detect}} or something like that, though using full names of the namespaces is probably the safer option.
 +
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 02:07, 12 September 2020 (EDT)
  
:: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 13:44, 22 April 2016 (EDT)
+
== The Howto namespace ==
 +
: ''Copied here from [[Template talk:Autoflight Navigation]].''
  
== Discussion about quotes on the wiki ==
+
To be honest, from the start I have considered the Howto namespace to be an abomination.  There is absolutely no need for it, as one could simply have articles in the main namespace with a Howto: prefix (IIRC they call this "user administered namespaces" or "pseudo namespaces" on Wikipedia). To not have to type the prefix, one could simply create redirects. Creating a separate Howto namespace have caused issues in the past, like that the search function per default only looks for articles in the Main namespaceIt is not entirely unlikely that what we see here might be some configuration issue as well.
{{usr|Hooray}} have started a page now at [[FlightGear wiki:Quoting Guidelines]] ([http://wiki.flightgear.org/index.php?title=FlightGear_wiki:Quoting_Guidelines&oldid=96104 perm]) for a discussion regarding guidelines for the use of quotes on the wikiJoin the discussion.
+
  
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:17, 21 March 2016 (EDT)
+
Sorry for the rant. And thanks again.
  
 +
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 06:29, 11 September 2020 (EDT)
  
In slight relation to this I have tried to make the wiki more consistently use the most common spelling and case, "Instant-Cquotes" and have changed the automatic categorization accordinglyAll articles using the {{tl|FGCquote}} template can now be found in [[:Category:Articles containing Instant-Cquotes]] (currently some ~250 articles).
+
: I wouldn't call that a rant.  It would be better on [[FlightGear wiki:Village pump]] though.  To me 'Howto' here is simply a categorisation.  Why is that categorisation even needed in the page title?  I never liked this namespace, specifically because the default search misses it, and there is a significant grey area of what you would categorise as a 'howto' or notI think it would be better managed with a basic {{tl|howto}} template at the start of each of these articles which automatically adds [[:Category:Howto]].  If you take your discussion above over to the village pump, I'll copy this over there as well.
  
[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 08:21, 23 March 2016 (EDT)
+
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 07:56, 11 September 2020 (EDT)
  
== Reorganizing the Git articles ==
+
== Space shuttle screenshots category need cleanup ==
I've noticed that the [[Category:Git|Git articles]] suffer from duplication and are in part obsolete (especially with regard to the instructions for running Git on Windows). Thus, I propose the following reorganization:
+
There currently are quite a number of misplaced files in the [[Special:CategoryTree/Space Shuttle screenshots|Space Shuttle screenshot categories]], possibly making it harder to find screenshots and other images. For example external screenshots in the [[:Category:Space Shuttle cockpit detail screenshots|cockpit detail category]], that preferably should be closeup images of panels and displays, and screenshots of large portions of the cockpit in the cockpit detail category.
* [[Development workflow]]: reorganization to explain how the patch submission process is organized from a high-level point of view (forking the repository from SourceForge, developing, pushing the commits to the personal fork, submitting a merge request/sending a patch to the mailing list);
+
* [[FlightGear Git]]: leave as is;
+
* '''Installing and configuring Git''' - new article about installing Git and configuring it (setting the username/e-mail address); merge the contents of [[FlightGear Git on Windows]] and [[Resources WRT running git on Win32]] here;
+
* [[FlightGear Git for laymen]] - make it follow [[FGW:MOS]], merge the contents of [[Howto:Start using git]] here;
+
* [[FlightGear Git: core developers]] and [[FlightGear Git: data developers]] - I'm uncertain about what I should do with them: the only piece information that would not be written in other articles is the list of alternative methods for cloning FGData;
+
* [[FlightGear Git: gitiquette]] and [[FlightGear Git: tips]] - make them follow [[FGW:MOS]].
+
Any comments? -- [[User:Elgaton|ElGaton]] ([[User talk:Elgaton|<tt>talk</tt> to me]]) 06:11, 13 May 2016 (EDT)
+
  
: This is sorely needed!  For [[FlightGear Git: core developers]] and [[FlightGear Git: data developers]], maybe these can be merged into something like [[FlightGear Git: working with the repositories]]?  The only real difference is the URL, but that is a minor difference with the [[:Category:Repository link templates]].  This could be generalised into a set of instructions for working with all git repositories for the core infrastructure, including forking and merge requests, with a current focus on the SourceForge web and non-web interfaces.
+
I do expect some overlap between the cockpit categories and the custom dialog categories as dialogs are featured in a lot of those.
  
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 08:17, 13 May 2016 (EDT)
+
There are also a lot of diagrams with no part of the Space Shuttle at all in the screenshot categories, those are more at home in the [[:Category:Space Shuttle diagrams|Space Shuttle diagrams]] category.
  
:: Yes, I was thinking about a similar solution as well. -- [[User:Elgaton|ElGaton]] ([[User talk:Elgaton|<tt>talk</tt> to me]]) 10:16, 13 May 2016 (EDT)
+
[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 20:10, 3 November 2020 (EST)
  
: For the reorganisation of the articles, it would be good to make a lot of use of the {{tl|Project infrastructure}} template.  This will abstract away the SourceForge infrastructure (well some instructions will be 100% SourceForge specific, so it won't be perfect).  I would like to however have [[Template talk:Project infrastructure#Slight variation of the current architecture|Johan's design]] implemented first, as it would be quite beneficial.
+
Have done a little cleanup, a lot left to do.
  
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 18:43, 14 May 2016 (EDT)
+
If my recategorization edits fill up [[Special:RecentChanges|recent changes]], click ''Hide minor edits''. When (re)categorizing, I mark my edits as minor edit so they can be filtered away if they fill up recent changes (I have gotten frustrated comments on my edits filling up recent changes before).
:: Thanks, didn't know it existed. Right now I'm fixing some last-minute bugs before the release, but I'll have a look at this. -- [[User:Elgaton|ElGaton]] ([[User talk:Elgaton|<tt>talk</tt> to me]]) 09:05, 15 May 2016 (EDT)
+
  
== UTF-8 language pages cannot be edited ==
+
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 21:23, 3 November 2020 (EST)
  
This is a continuation of [[FlightGear wiki:Village pump/Archive 2015#UTF-8 language pages cannot be edited]].  I can see that wiki editors are [[Zh/FlightGear Wiki|forced to create workarounds]], as the [[Main page]] in Chinese [http://wiki.flightgear.org/index.php?title=Zh/%E9%A6%96%E9%A1%B5&action=edit cannot be edited]. I think it is quite important to solve this ''"A database query error has occurred. This may indicate a bug in the software"'' issue.  As the fix is quite dangerous (see {{mediawiki|Topic:S1q54kosfdkhz6w1}}), do we have a backup system?  Do we have regular mysql and ftp dumps that can be backed up locally using rsync?
+
Also added [[:Category:Screenshots of Earthview]] to relevant Space Shuttle screenshots up to and including [[:File:Shuttle-tutorial2-01.jpg]].
  
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 05:16, 15 May 2016 (EDT)
+
[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 05:08, 6 November 2020 (EST)

Latest revision as of 05:08, 6 November 2020


Archives
2012, 2013
2014, 2015
2016, 2017
2018, 2019

Shortcut
FGW:VP

Welcome to the Village Pump. This page is used to discuss the technical issues, operations and guidelines of the FlightGear wiki.

Please add new topics to the bottom of this page.

Old discussions should be moved to a FlightGear wiki:Village pump/Archive YEAR. These discussions can then be moved to a relevant talk page if appropriate.

New Portal: Embedded or Hardware (02/2020)

Suggestion: Dedicated portal for articles relating to embedded/hardware topics (which would be in line with numerous threads on the forum, as well as existing articles on the wiki). - Hooray (talk) 11:59, 17 February 2020 (EST)

That is slightly less complicated than you might think. What you would do is to create a new page with the prefix Portal: and a suitable name, say for example Portal:Hardware development, Portal:Cockpit hardware or Portal:DIY cockpit hardware, or maybe Portal:Hardware if you would also like to see commercial hardware there, and then copy and modify the content from a similar portal.
Hint: There is actually not a portal namespace, it is just a prefix. The portal pages are actually in the main namespaces, and thus function just like any other article page on the wiki.
Johan G (Talk | contribs) 13:35, 10 March 2020 (EDT)
Though I think your Portal:Embedded might be more diffuse than Portal:Hardware for people that do not know what embedded software This is a link to a Wikipedia article is, I have still added it to the main page and added Category:Portals to it. It will get more use if people can find it. :-P
Johan G (Talk | contribs) 04:16, 14 March 2020 (EDT)

Use as few categories as possible

Always use as few categories as possible. Categories are a place in a structure rather than tags. Putting each page in a lot of categories will put a lot of of pages in each category. There is in particular no need to put a page in both a category and then in each category above that category.

Please see advice in Help:Your first article#Categories and maybe also Help:categories.

Johan G (Talk | contribs) 13:04, 15 March 2020 (EDT)

Meta template and templates for commonly used logotypes and icons

Through a placeholder page (ugh!) and a edit summary Hooray suggested making a template for commonly used logotypes.

Cquote1.png placeholder/stub for all sorts of wiki related logos that may need to be updated over time, but that are referenced on multiple pages - so that we don't need to edit each and every page here.
Cquote2.png
Cquote1.png @Johan: could use your help with this, unless I can write the heuristics in Php or JavaScript ;-)
— Hooray, 11 April 2020‎, 08:04
Cquote2.png

I would guess you also intend it to be used for icons as well, for example the ready icons? Logotype/icon templates might not be a bad idea. Less typing is almost always good.

{{logo}} should probably be a meta template, a template used by other templates in this case by logotype templates. Meta templates are pretty common on MediaWiki wikis.

Essentially, there could be a set of logotype and icon templates, for example {{Compositor logo}}, {{FGInterface logo}}, {{Air refueling ready icon}} etc, that pass the image for the logotype, an alt text (for accessibility and when the image is not shown, for example due to browser settings) and a link to a relevant wiki page to {{logo}}. Possibly also optional parameters like other sizes etc. The meta template would then add the boilerplate stuff around that and set the size.

I would advise that having a suffix indicating the type of template, for example logo, icon like mentioned above or navigation (for navigation boxes), in essence having less ambiguous names, is generally a good idea.

I should mention that I am generally against placeholder pages.

Johan G (Talk | contribs) 06:44, 12 April 2020 (EDT)

UTF-8 language pages cannot be edited (cont. from 2015)

While migrating my own unrelated MediaWiki instance, I may have stumbled upon "a" SQL issue blocking the creation of pages with non-latin characters in their titles. See:

If someone has access to the MySQL backend (command line or phpMyAdmin), could you check what the "Collation" of our database is set to? For example:

USE dbname;
SELECT @@character_set_database, @@collation_database;

Or in phpMyAdmin the collation is given in the database listing. My guess is that we are not using UTF-8. That can be changed (after a backup) with:

ALTER DATABASE dbname CHARACTER SET utf8 COLLATE utf8_general_ci;

Or in phpMyAdmin, select the databse of this wiki, click on the "Operations" tab, in the "Collation" box select "utf8_general_ci", and finally click on "Go". Hopefully this is the cause of this long standing and painful issue.

Bugman (talk) 03:33, 9 September 2020 (EDT)

Hi Edward,
I somehow missed all these previous reports :-( Sorry!
You're right. The database is in latin1. We're actually currently in the process of migrating some of our server work and updating. I will take care of setting the correct collation on that occasion.
Gijs (talk) 04:24, 9 September 2020 (EDT)
Great, that sounds exactly like this problem. Only pages with 'latin1' characters in their names can be edited. I really hope switching the collation to UTF-8 will fix the problem. There must have been a MySQL server migration many years ago where the old database was UTF-8 and the import automatically changed the language to the server default of 'latin1', as many pages were created on this wiki with non-latin1 characters in the past. I see this with my MySQL database too - I have to switch back to UTF-8 after import into the new SQL database.
Bugman (talk) 06:00, 9 September 2020 (EDT)

Needing an extra pair of eyes

There is a problem with automatic categorization in {{Autoflight Navigation}} that I can not seem to solve.

For details see Template talk:Autoflight Navigation#Automatic categorization seem broken.

Johan G (Talk | contribs) 10:26, 10 September 2020 (EDT)

All done! In summary, the {{howto other}} template logic was completely broken and was operating as the {{main other}} template instead! Checking if the {{NAMESPACE}} is set to {{ns:0}} is not how you check for the "Howto" namespace. As I don't know the numeric value of this namespace, I switched to comparing {{NAMESPACE}} to the simple string 'Howto'. So the template is now fixed. We should see a lot of auto-categorisation additions and fixes now. I also switched {{Autoflight Navigation}} to use {{namespace detect}} to simplify its logic.
Bugman (talk) 06:14, 11 September 2020 (EDT)
Thank you som much for fixing that. :-)
Did not think of comparing the namespace numbers between the templates.
I was wondering where I found the numbers, but could not quite remember. If I figure it out I will probably add the source for those at a suitable place, like under Technical details in ducumentation for {{namespace detect}} or something like that, though using full names of the namespaces is probably the safer option.
Johan G (Talk | contribs) 02:07, 12 September 2020 (EDT)

The Howto namespace

Copied here from Template talk:Autoflight Navigation.

To be honest, from the start I have considered the Howto namespace to be an abomination. There is absolutely no need for it, as one could simply have articles in the main namespace with a Howto: prefix (IIRC they call this "user administered namespaces" or "pseudo namespaces" on Wikipedia). To not have to type the prefix, one could simply create redirects. Creating a separate Howto namespace have caused issues in the past, like that the search function per default only looks for articles in the Main namespace. It is not entirely unlikely that what we see here might be some configuration issue as well.

Sorry for the rant. And thanks again.

Johan G (Talk | contribs) 06:29, 11 September 2020 (EDT)

I wouldn't call that a rant. It would be better on FlightGear wiki:Village pump though. To me 'Howto' here is simply a categorisation. Why is that categorisation even needed in the page title? I never liked this namespace, specifically because the default search misses it, and there is a significant grey area of what you would categorise as a 'howto' or not. I think it would be better managed with a basic {{howto}} template at the start of each of these articles which automatically adds Category:Howto. If you take your discussion above over to the village pump, I'll copy this over there as well.
Bugman (talk) 07:56, 11 September 2020 (EDT)

Space shuttle screenshots category need cleanup

There currently are quite a number of misplaced files in the Space Shuttle screenshot categories, possibly making it harder to find screenshots and other images. For example external screenshots in the cockpit detail category, that preferably should be closeup images of panels and displays, and screenshots of large portions of the cockpit in the cockpit detail category.

I do expect some overlap between the cockpit categories and the custom dialog categories as dialogs are featured in a lot of those.

There are also a lot of diagrams with no part of the Space Shuttle at all in the screenshot categories, those are more at home in the Space Shuttle diagrams category.

Johan G (Talk | contribs) 20:10, 3 November 2020 (EST)

Have done a little cleanup, a lot left to do.

If my recategorization edits fill up recent changes, click Hide minor edits. When (re)categorizing, I mark my edits as minor edit so they can be filtered away if they fill up recent changes (I have gotten frustrated comments on my edits filling up recent changes before).

Johan G (Talk | contribs) 21:23, 3 November 2020 (EST)

Also added Category:Screenshots of Earthview to relevant Space Shuttle screenshots up to and including File:Shuttle-tutorial2-01.jpg.

Johan G (Talk | contribs) 05:08, 6 November 2020 (EST)