Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G

Difference between revisions of "FlightGear wiki:Village pump"

From FlightGear wiki
Jump to: navigation, search
(Reorganizing the Git articles)
m (Automated translation for the wikipedia template: Spelling in own post)
 
(97 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]]}}
 
{{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? ==
+
== Welcoming template ==
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.
+
I have had a shelved draft of a welcoming template laying in a subpage for quite a while that I have dusted off and rewritten.
  
It should welcome the (new) user
+
It has a welcoming message and some links I hope will be useful to new users (and perhaps not so new ones as well).  The idea is that when some of us sees that there is a new user we will add that template to the top of the new users discussion page.  I am not sure about whether we should wait till the user have made some edits (to see if it is a bot) or if we should add it at once.
  
In addition, it should probably mention and/or link to pages mentioning:
+
I would like to have some more eyes on it to see for example if I should have some more or some less links, or if there is something I did not think of.  I tried to use as few links as possible, while also keeping ones a new user might hope is there, but do not know where to look for.
* 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
+
* 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.
+
When I feel content with it I will move it to the template namespace and add a site notice linking to it for a while, as I am not sure if you all look here or on [[Special:RecentChanges]].
  
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 20:31, 30 January 2016 (EST)
+
<s>Anyway here is my current draft (do not hesitate to add suggestions on its discussion page): User:Johan G/Template:Welcome to the wiki</s>
  
: I think this is a great idea.  A nice concise summary with links to help a new user navigate the FlightGear jungle would be a great addition.  It should however remain very short with simple sentences - while being complete - as many users are not native speakers.  So maybe there should be translations of the template with manually added links at the bottom for easy access to all the translations?
+
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 13:02, 15 April 2019 (EDT)
  
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 03:35, 12 February 2016 (EST)
+
:: The template is now moved to {{tl|Welcome to the wiki}}
 +
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:19, 17 April 2019 (EDT)
  
:: 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]].
+
: Hi Johan,
:: 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).
+
: The template looks good to me!
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 14:47, 4 March 2016 (EST)
+
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 06:48, 16 April 2019 (EDT)
  
:: I now consider
+
: It looks good to me too.  What about using [https://www.mediawiki.org/wiki/Extension:Create_User_Page Extension:Create User Page] to fully automate the process?
::* A Welcome message
+
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 09:57, 16 April 2019 (EDT)
::* 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.
+
:: If you mean as in automatically creating a user discussion page and adding the welcome template?  Though it would probably be a good idea, as likely no one will be left without a welcome, it kind of feels better if it is done by a being of flesh and blood than if it was done by a bot.  Consider me undecided. ;-)
:: 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.
+
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:13, 17 April 2019 (EDT)
:: 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]]
+
::: It is a worry that the automation will not seem personal.  However I just counted the [[Special:Log/newusers|new user registrations]] from 17/04/2018 to 17/04/2019.  There are 113 registrations!  Maybe 5% are not bots, but identifying these is hard.  I think it will be too overwhelming for any individual to manually do this.
:: —[[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:
+
::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 01:43, 18 April 2019 (EDT)
::: * 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]].
+
:::: One registration every second day.  Automation might not be such a bad idea after all.
 +
:::: I noticed though that [https://www.mediawiki.org/wiki/Extension:Create_User_Page Extension:Create User Page] does not create the user ''discussion'' page, which is where such messageboxes typically are placed. Maybe not a big problem.
 +
:::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 12:46, 19 April 2019 (EDT)
  
Should you wish to create or edit some articles, ''do so''! Here are some resources to get you started:
+
:::: A site notice is now up with the text "Hi fellow wiki users!
* [[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!
+
:::: To help new users get more familiar with the wiki (and maybe older users too) there is now a {{tl|Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).
</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 ==
+
:::: I have tried to keep the template short, but meaningful. /{{usr|Johan G}}"
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)
+
:::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 06:13, 26 April 2019 (EDT)
  
: 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.
+
I just noticed [https://www.mediawiki.org/wiki/Extension:NewUserMessage Extension:NewUserMessage] which seems perfectly suited to be used the way Bugman mentioned  [https://www.mediawiki.org/wiki/Extension:Create_User_Page Extension:Create User Page] above on 16 April. This extension automatically creates a discussion page with a message for new users.
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 03:20, 12 February 2016 (EST)
+
[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 10:44, 22 June 2019 (EDT)
  
:: 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.
+
: I think we should really use such an extension. There are just too many new user subscriptions to do this manually (and my experience from [http://wiki.nmr-relax.com/ my own wiki] is that 99% of subscriptions are failed bots). I say install it asap.  It would really benefit real new users who might be lost under the load of failed bot registrations. Can you install it yourself Johan?
:: -- [[User:Elgaton|ElGaton]] ([[User talk:Elgaton|<tt>talk</tt> to me]]) 06:26, 13 February 2016 (EST)
+
  
::: 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.
+
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 03:50, 2 July 2019 (EDT)
  
::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 12:04, 14 February 2016 (EST)
+
:: No, I can not install wiki extensions (I am a wiki admin just like you).  Simon, the maintainer, can for sure do it and I think that maybe Gijs could do do it.
 +
:: [[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 10:21, 4 July 2019 (EDT)
  
:::: 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.
+
:: Sent a mail to Gijs and Simon, with a copy to you.
 +
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 12:24, 4 July 2019 (EDT)
  
::::: 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.
+
=== Adding it to all user discussion pages? ===
 +
I have started to wonder if we maybe should add the template to all of the user discussion pages (but not archived ones of course).
  
::::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 14:36, 19 February 2016 (EST)
+
What would be the advantages and disadvantages of that.  Personally I see more advantages than disadvantages with that.
  
:: 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)
+
This would be a bot job of course.
  
== WIP vs. Under construction ==
+
[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 08:50, 21 June 2019 (EDT)
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}}.
+
== The lead section, or first section, as I have called it ==
 +
Most of the time when I have been writing help pages I have tried to use the terminology used on Wikipedia and its sister projects, but somehow I have called the [https://en.wikipedia.org/w/index.php?title=Wikipedia:Manual_of_Style/Lead_section&oldid=895095452 lead section] (or ''lead'' or ''introduction'') ''first section'' and done that consistently.  I have gone through the help pages and changed that.
  
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]]) 08:56, 23 May 2019 (EDT)
  
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 10:11, 17 February 2016 (EST)
 
  
== [[Fr/Pilote automatique]] ==
+
== Automated translation for the wikipedia template ==
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.
+
Just for the record, I attempted to modify {{tl|wikipedia}} to automatically determine the page language and point to the non-english Wikipedia page without the {{param|lang}} parameter. I have recently added the {{param|wikipedia}} parameter to {{tl|infobox aircraft}} and was hoping to use the language auto-detection to have the wikipedia infobox link point to the correct translation at Wikipedia. I could not use <code>{{obr}}PAGELANGUAGE{{cbr}}</code> as this required MediaWiki >= 1.29 (see [https://www.mediawiki.org/wiki/Help:Magic_words#Technical_metadata]).  So I unsuccessfully attempted to use the same logic as the {{tl|LangSwitch}} parameter.  I reverted all changes as there appears to be no way to correctly detect the page language (other than wait for the next MediaWiki upgrade to expose <code>{{obr}}PAGELANGUAGE{{cbr}}</code>).
  
Cordialement, et Hop ! --[[User:F-WTSS|F-WTSS]] ([[User talk:F-WTSS|talk]]) 15:30, 18 February 2016 (EST)
+
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 05:51, 24 May 2019 (EDT)
  
== MediaWiki updated to 1.26.2 ==
+
: Note that this means that the aircraft infobox wikipedia link can only point to the English page until an upgrade occurs (this is not urgent though).
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)
+
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 06:01, 24 May 2019 (EDT)
  
: 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]].
+
:: <code><nowiki>{{lc: {{#titleparts: {{PAGENAME}} | 1}} }}</nowiki></code> should return the language code needed for the '''lang=''' parameter.
  
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 10:54, 19 February 2016 (EST)
+
:: Note that you will only be able to pull this of where the article title is ''exactly the same'' in another language.  If a model for example have have another name in one country (like cars sometimes have) the link will fail.  If the title is transcribed the link will fail.  Etc.
  
:: Hm, looks that will require quite some attention indeed. I'm afraid that'll has to wait for now.
+
:: [[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 07:16, 24 May 2019 (EDT)
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 12:29, 19 February 2016 (EST)
+
  
=== Nasal Syntaxhighlighting ===
+
== Expansion of the upload licence list and uploading errors ==
: 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/
+
I've always been concerned that we do not present enough licence choices for the graphics uploaded to the wiki. In testing this, I've noticed that I can no longer upload graphics to the wiki!  I see a red exclamation mark and the text <code>Unknown error: "unknown"</code>, <code>None of the uploads were successful.</code>, the button <code>Retry failed uploads</code>, and <code>0 of 1 file uploaded</code>.  Has any one else seen this?
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 12:29, 19 February 2016 (EST)
+
  
::: Hi Gijs,
+
Also, is there a reason we don't update [[MediaWiki:Licenses]]?  I think I'll add the CC v4.0 licenses so those can be selected.  I'll probably also add the GPL.
::: 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)
+
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 04:22, 27 May 2019 (EDT)
  
:::Hi Gijs,
+
: While I have not tested uploading, according the [http://wiki.flightgear.org/index.php?title=Special%3ALog&type=upload&user=&page=&year=&month=-1&tagfilter=&hide_patrol_log=1&hide_tag_log=1 upload log] files were uploaded as recent as the 26th.
:::Here's the code for a Nasal lexer. Be warned, it's thoroughly untested, but has the following features:
+
: Regarding the licenses it might be a good idea to add any missing [[:Category:License templates|license templates]].
:::* Full support for all three string types (backtick, single quote, and double quote), including escapes and formatting strings (e.g., for {{func link|sprintf}}).
+
: [[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 08:39, 28 May 2019 (EDT)
:::* 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
+
== Conversion of direct forum links and URLs to templates ==
:::<syntaxhighlight lang="python" enclose="div">
+
# -*- coding: utf-8 -*-
+
"""
+
Lexer for Nasal.
+
"""
+
  
from pygments.lexer import RegexLexer, words, include, inherit, bygroups, using
+
I'll continue the discussions of [[Template talk:Forum link#Usable as replacement for cite web used for forum links?]] here. After much editing of {{tl|project infrastructure}}, {{tl|project infrastructure option}}, {{tl|forum url}}, and {{tl|forum link}}, I have now gone through the wiki [http://wiki.flightgear.org/index.php?title=Special:Search&search=forum.flightgear.org&fulltext=Search&profile=all] [http://wiki.flightgear.org/index.php?title=Special:Search&limit=500&offset=0&profile=all&search=flightgear.org] and converted almost all direct links and URLs to the forum to use these new templates.  I used macros in ''vim'' to simplify and semi-automate the process.  There should now be almost no direct references to forum.flightgear.org left. If I have missed anything obvious please point it out to me.
from pygments.token import Text, Keyword, Name, String, Number, Operator, Punctuation, Comment
+
from pygments.lexers.html import XmlLexer
+
  
__all__ = ['NasalLexer', 'XMLNasalLexer']
+
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 09:49, 6 June 2019 (EDT)
  
class NasalLexer(RegexLexer):
+
: I've found more direct forum links and converted those.  However I've also noticed that [[Special:Search]] does not reveal all instances of ''forum.flightgear.org'' or ''flightgear.org/forums''!?  Does anyone know how to hunt down every last direct link?  Cheers!
  
name = 'Nasal'
+
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 06:17, 7 June 2019 (EDT)
aliases = ['nasal']
+
filenames = ['*.nas']
+
  
tokens = {
+
:: That was huge amount of work.  Side note: In disbelief I looked at some of the edits where using the template decreased the article size by several kilobytes.
'formatters': [
+
:: There is a special page for looking for external links, [[Special:LinkSearch]], that might be useful. Unfortunately it only looks for the domain, so you will have to sift though the results for the relevant hits. ([http://wiki.flightgear.org/index.php?target=*.flightgear.org&namespace=&title=Special%3ALinkSearch External link search for "*.flightgear.org"].)
(r'%[-#0 +]*(?:[0-9]+)?(?:\.[0-9]+)?[dis%couxXeEfFgG]', String.Interpol),
+
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 10:19, 7 June 2019 (EDT)
],
+
'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):
+
::: Those articles with big diffs were usually the poor-quality articles pumped full of {{tl|cite web}} text.  I used vim macros to quickly convert them, but had to manually check every change to be sure as there were some issues.
"""
+
For Nasal code embedded in XML files.
+
"""
+
  
name = 'XML-Nasal'
+
::: I'd completely forgotten about [[Special:LinkSearch]].  I had used that previously to convert all repository links to convert the entire wiki to use the [[:Category:Repository link templates]] template family.  I now see that the forum link conversion is a much, much, much bigger job!  I currently see:
aliases = ['xml-nasal', 'xml-ns']
+
:::* <code><nowiki>http://forum.flightgear.org</nowiki></code>: [http://wiki.flightgear.org/index.php?title=Special:LinkSearch&limit=3000&offset=0&target=http%3A%2F%2Fforum.flightgear.org 2,386 hits].
 +
:::* <code><nowiki>https://forum.flightgear.org</nowiki></code>: [http://wiki.flightgear.org/index.php?title=Special:LinkSearch&limit=3000&offset=0&target=https%3A%2F%2Fforum.flightgear.org 2,029 hits].
 +
:::* <code><nowiki>http://flightgear.org/forums</nowiki></code>: [http://wiki.flightgear.org/index.php?title=Special:LinkSearch&limit=500&offset=0&target=http%3A%2F%2Fflightgear.org%2Fforums 295 hits]
 +
:::* <code><nowiki>https://flightgear.org/forums</nowiki></code>: [http://wiki.flightgear.org/index.php?title=Special:LinkSearch&limit=500&offset=0&target=https%3A%2F%2Fflightgear.org%2Fforums 0 hits]
  
tokens = {
+
::: Unfortunately in converting all the direct links I found via the normal search, I know that we won't be able to automate/script this.  There are far too many different ways these forum links are presented.  For example a link ending with the anchor <code>#p1234</code> or simply having <code>p=1234</code> in the URL can have all other elements (''t'', ''f'', ''sid'', etc.) removed and drop to simply <code>{{obr}}forum link{{!}}p=1234{{cbr}}</code>, with either the {{param|text}} or {{param|title}} parameters specified as needed. Some forum links are unnecessarily long. A link to a post only needs {{param|p}}, a link to a topic only {{param|t}} and a link to a subforum only {{param|f}}.  The exception being ''hilit''.  However ''hilit'' is often present in the URL without any keywords.  Then there is also a mix of using <code>=</code> and <code><nowiki>{{=}}</nowiki></code> in the URLs.  And it is not always completely obvious if {{tl|forum url}} or {{tl|forum link}} should be used.  The only regularity is in the {{tl|cite web}} usage, but that also appears to have 3 or 4 forms that have evolved over time.
'root': [
+
(r'(<(?:load|unload|script)>)(<!\[CDATA\[)?(.*?)(]]>)?(</(?:load|unload|script)>)', bygroups(Name.Tag, Comment.Preproc, using(NasalLexer), Comment.Preproc, Name.Tag),
+
inherit,
+
],
+
}
+
</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)
+
::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 11:28, 7 June 2019 (EDT)
  
:: 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)
+
=== Update ===
  
==== References ====
+
I've eliminated all <code>flightgear.org/forums</code> hard links on the wiki to use {{tl|forum url}} and {{tl|forum link}}.  The numbers are now:
<references />
+
* <code><nowiki>http://forum.flightgear.org</nowiki></code>: [http://wiki.flightgear.org/index.php?title=Special:LinkSearch&limit=5000&offset=0&target=http%3A%2F%2Fforum.flightgear.org 1,918 hits].
 +
* <code><nowiki>https://forum.flightgear.org</nowiki></code>: [http://wiki.flightgear.org/index.php?title=Special:LinkSearch&limit=5000&offset=0&target=https%3A%2F%2Fforum.flightgear.org 3,016 hits].
 +
* <code><nowiki>http://flightgear.org/forums</nowiki></code>: [http://wiki.flightgear.org/index.php?title=Special:LinkSearch&limit=500&offset=0&target=http%3A%2F%2Fflightgear.org%2Fforums 0 hits]
 +
* <code><nowiki>https://flightgear.org/forums</nowiki></code>: [http://wiki.flightgear.org/index.php?title=Special:LinkSearch&limit=500&offset=0&target=https%3A%2F%2Fflightgear.org%2Fforums 0 hits]
  
== The repository link templates ==
+
For reference, here are my vim macros.  These are placed into the <code>~/.vimrc</code> file:
=== 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:
+
<syntaxhighlight lang=vim>
 +
" --- FlightGear forum conversions ---
 +
" Link: Convert [http://www.flightgear.org/forums forums] to {{forum link|text=forums}}.
 +
let @f='/[http.*forum^Mv/ ^Mc{{forum link|text=^[/]^Mvc}}^[/forum^MN'
 +
" Link: Convert [http://flightgear.org/forums/viewforum.php?f=13 section of our forum] to {{forum link|f=13|text=section of our forum}}.
 +
let @g='/[http.*forum^Mv/f=^Mhc{{forum link|^[/ ^Mvc|text=^[/]^Mvc}}^[/forum^MN'
 +
" Link: Convert [http://flightgear.org/forums/viewtopic.php?f=5&t=7485#p102005] to {{forum link|p=102005}}.
 +
let @p='/[http.*forum^Mv/#^Mc{{forum link|^[la=^[/]^Mvc}}^[/forum^MN'
 +
" Link: Convert [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14254 thread] to {{forum link|t=14254|text=thread}}.
 +
let @t='/[http.*forum^Mv/t=^Mhc{{forum link|^[/ ^Mvc|text=^[/]^Mvc}}^[/forum^MN'
 +
" Link: Convert [http://flightgear.org/forums/viewtopic.php?f=42&t=15267#p149971 this short essay] to {{forum link|p=149971|text=this short essay}}.
 +
let @s='/[http.*forum^Mv/#^Mc{{forum link|^[la=^[/ ^Mvc|text=^[/]^Mvc}}^[/forum^MN'
 +
" Link: Convert [http://flightgear.org/forums/viewtopic.php?f=2&t=1697&p=12549 ARINC] to {{forum link|p=12549|text=ARINC}}.
 +
let @r='/[http.*forum^Mv/p=^Mhc{{forum link|^[/ ^Mvc|text=^[/]^Mvc}}^[/forum^MN'
 +
" Link: Convert [http://forum.flightgear.org/viewtopic.php?f=79&t=22840] to {{forum link|t=22840}}.
 +
let @l='/[http.*forum^Mv/t=^Mhc{{forum link|^[/]^Mvc}}^[/forum^MN'
 +
" Link: Convert [http://flightgear.org/forums/viewtopic.php?f=28&t=10488&p=144233&hilit=snapshot#p144233 at the forum] to {{forum link|hilit=snapshot|p=144233|text=at the forum}}.
 +
let @i='/[http.*forum^Mv/hilit^Mhc{{forum link|^[/#^Mxi|^[la=^[/ ^[vc|text=^[/]^Mvc}}^[/forum^MN'
 +
" Link: Convert [http://flightgear.org/forums/viewtopic.php?f=17&t=20214&p=186020&hilit=xml+french#p185963] to {{forum link|hilit=xml+french|p=185963}}.
 +
let @j='/[http.*forum^Mv/hilit^Mhc{{forum link|^[/#^Mxi|^[la=^[/]^Mvc}}^[/forum^MN'
  
* {{tl|flightgear file}},
+
" URL: Convert http://flightgear.org/forums/viewtopic.php?f=6&t=14758 to {{forum url|t=14758}}.
* {{tl|simgear file}},
+
let @w='/http.*forum^Mv/t=^Mhc{{forum url|^[llea}}^[/forum^MN'
* {{tl|fgdata file}},
+
" URL: Convert http://flightgear.org/forums/viewtopic.php?f=17&t=2766&p=26459&hilit=generic+protocol#p26459 to {{forum url|hilit=generic+protocol|p=26459}}.
* {{tl|fgaddon file}}.
+
let @h='/http.*forum^Mv/hilit^Mhc{{forum url|^[/#^Mxi|^[la=^[ea}}^[/forum^MN'
 +
" URL: Convert http://flightgear.org/forums/viewtopic.php?f=2&t=3430&start=0&st=0&sk=t&sd=a&hilit=oscillations+x to {{forum url|t=3430|hilit=oscillations+x}}
 +
let @b='/http.*forum^Mv/t=^Mhc{{forum url|^[llelv/hilit^Mhxi|^[/.[\n ]^[a}}^[/forum^MN'
 +
" URL: Convert http://www.flightgear.org/forums/viewtopic.php?f=4&t=6890 to {{forum url|t=6890}}.
 +
let @v='/http.*forum^Mi{{forum url|^[lv/t=^Mhxllea}}^[/forum^MN'
 +
" URL: Convert http://flightgear.org/forums/viewtopic.php?f=6&t=3085&p=28982#p28982 to {{forum url|p=28982}}.
 +
let @x='/http.*forum^Mv/#^Mc{{forum url|^[la=^[ea}}^[/forum^MN'
 +
" URL: Convert http://flightgear.org/forums/viewtopic.php?f=6&t=5814&p=44566 to {{forum url|p=44566}}.
 +
let @y='/http.*forum^Mv/p=^Mhc{{forum url|^[llea}}^[/forum^MN'
  
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.
+
" Member: Convert [http://www.flightgear.org/forums/memberlist.php?mode=viewprofile&u=510 Gijs] to {{forum list|type=member|u=510|text=Gijs}}.
 +
let @m='/[http.*forum^Mv/member^Mhc{{forum link|type=^[/list^[v/u=^Mhc|^[/ ^[xi|text=^[/]^Mvc}}^[/forum^MN'
  
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 15:05, 25 February 2016 (EST)
+
" Search: Convert [http://www.flightgear.org/forums/search.php?st=0&amp;sk=t&amp;sd=d&amp;sr=posts&amp;keywords=head+tracking head tracking] to {{forum list|type=search|keywords=head+tracking|text=head tracking}}.
 
+
let @a='/[http.*forum^Mv/search^Mhc{{forum link|type=^[/.php^[v/keywords=^Mhc|^[/ ^[xi|text=^[/]^Mvc}}^[/forum^MN'
: 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)
+
</syntaxhighlight>
 
+
:: 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)
+
 
+
=== Regex parsing of template parameters? ===
+
 
+
For the {{tl|repo link}} template, I am currently trying to work out what to do for git branches and tags on the SourceForge infrastructure.  The 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:
+
 
+
* Tag <code>version/2016.1.1</code>:  https://sourceforge.net/p/flightgear/simgear/ci/version/2016.1.1/~/tree/simgear/ephemeris/ephemeris.cxx
+
* 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:
+
 
+
* [https://www.mediawiki.org/wiki/Extension:RegexParserFunctions Extension:RegexParserFunctions]
+
 
+
Though I'm not 100% sure if that will work.  Or does someone else know an alternative?  Cheers!
+
 
+
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 12:09, 22 April 2016 (EDT)
+
 
+
: 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)
+
 
+
:: That might be a solution.  But I don't know how to do that without regex ;)  We really only have #ifeq statements, but that has to match the whole string.
+
 
+
:: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 13:44, 22 April 2016 (EDT)
+
  
== Discussion about quotes on the wiki ==
+
The <code>^[</code> and <code>^M</code> characters have to be converted into the escape and enter escape sequences for this to work (using e.g. {{key press|i}}, {{key press|ctrl|v}}, {{key press|esc}}, {{key press|esc}} and {{key press|i}}, {{key press|ctrl|v}}, {{key press|enter}}, {{key press|esc}}).  These handle the <code>forum.flightgear.org</code> hard links as well, but only cover maybe 90% of all hard links. One link that often needs manual intervention is when ''start=X'' is in the URLThis requires following the link, finding the post number, and then supplying the {{param|p}} parameter, which is absent from the original URL, to the templates.
{{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)
+
'''Roadmap:'''  Once all the <code>http</code> links are converted, all links will be present in the <code>https</code> search.  Then the {{tl|project infrastructure}} template can be modified to produce <code>http</code> forum URLs rather than <code>https</code>.  This will cause only the unconverted <code>https</code> links in be present in the <code>https</code> search.
  
 +
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 04:19, 11 June 2019 (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 accordingly. All articles using the {{tl|FGCquote}} template can now be found in [[:Category:Articles containing Instant-Cquotes]] (currently some ~250 articles).
+
: Here is a test of the http to https switch.  Before the switch:
 +
:* <code><nowiki>http://forum.flightgear.org</nowiki></code>: [http://wiki.flightgear.org/index.php?title=Special:LinkSearch&limit=5000&offset=0&target=http%3A%2F%2Fforum.flightgear.org 1,914 hits].
 +
:* <code><nowiki>https://forum.flightgear.org</nowiki></code>: [http://wiki.flightgear.org/index.php?title=Special:LinkSearch&limit=5000&offset=0&target=https%3A%2F%2Fforum.flightgear.org 3,060 hits].
 +
:* <code><nowiki>http://flightgear.org/forums</nowiki></code>: [http://wiki.flightgear.org/index.php?title=Special:LinkSearch&limit=500&offset=0&target=http%3A%2F%2Fflightgear.org%2Fforums 0 hits]
 +
:* <code><nowiki>https://flightgear.org/forums</nowiki></code>: [http://wiki.flightgear.org/index.php?title=Special:LinkSearch&limit=500&offset=0&target=https%3A%2F%2Fflightgear.org%2Fforums 0 hits]
  
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 08:21, 23 March 2016 (EDT)
+
: And after the switch:
 +
:* <code><nowiki>http://forum.flightgear.org</nowiki></code>: [http://wiki.flightgear.org/index.php?title=Special:LinkSearch&limit=5000&offset=0&target=http%3A%2F%2Fforum.flightgear.org 4,127 hits].
 +
:* <code><nowiki>https://forum.flightgear.org</nowiki></code>: [http://wiki.flightgear.org/index.php?title=Special:LinkSearch&limit=5000&offset=0&target=https%3A%2F%2Fforum.flightgear.org 835 hits].
 +
:* <code><nowiki>http://flightgear.org/forums</nowiki></code>: [http://wiki.flightgear.org/index.php?title=Special:LinkSearch&limit=500&offset=0&target=http%3A%2F%2Fflightgear.org%2Fforums 0 hits]
 +
:* <code><nowiki>https://flightgear.org/forums</nowiki></code>: [http://wiki.flightgear.org/index.php?title=Special:LinkSearch&limit=500&offset=0&target=https%3A%2F%2Fflightgear.org%2Fforums 0 hits]
  
== Reorganizing the Git articles ==
+
: So there are 1914 <code>http://</code> and 835 <code>https://</code> forum hard links still to convert!
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:
+
* [[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.
+
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 09:42, 2 July 2019 (EDT)
  
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 08:17, 13 May 2016 (EDT)
+
== Language flags on the main page ==
  
:: 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)
+
While activating "Português do Brasil" as a new language on the wiki (via [[Special:Interwiki]]), I decided to use a generic white flag for the language on the [[main page]].  As an experiment I have added this generic flag for all translations.  It is not pretty, but it does better advertise the languages where a flag makes zero sense.  Please have a look and see what you think!
  
: 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.
+
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 04:35, 7 June 2019 (EDT)
  
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 18:43, 14 May 2016 (EDT)
+
: I would also like to point out that it is still impossible to edit the wiki in certain languages. See [[FlightGear wiki:Village pump/Archive 2016#UTF-8 language pages cannot be edited]].  We really need to fix this database error issue.
:: 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:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 05:34, 7 June 2019 (EDT)
  
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"'' issueAs 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?
+
: Don't worry about the white flag, I've now uploaded public domain icons, taken from Wiki Commons SVG files, for all language flagsFor Persian, I've used the Iranian flagAnd for Arabic I've used the neutral Arab League flagSo now we have flag icons for all current translations.
  
[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 05:16, 15 May 2016 (EDT)
+
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 05:59, 7 June 2019 (EDT)

Latest revision as of 13:23, 12 August 2019


Archives
2012, 2013
2014, 2015
2016, 2017
2018

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.

Welcoming template

I have had a shelved draft of a welcoming template laying in a subpage for quite a while that I have dusted off and rewritten.

It has a welcoming message and some links I hope will be useful to new users (and perhaps not so new ones as well). The idea is that when some of us sees that there is a new user we will add that template to the top of the new users discussion page. I am not sure about whether we should wait till the user have made some edits (to see if it is a bot) or if we should add it at once.

I would like to have some more eyes on it to see for example if I should have some more or some less links, or if there is something I did not think of. I tried to use as few links as possible, while also keeping ones a new user might hope is there, but do not know where to look for.

When I feel content with it I will move it to the template namespace and add a site notice linking to it for a while, as I am not sure if you all look here or on Special:RecentChanges.

Anyway here is my current draft (do not hesitate to add suggestions on its discussion page): User:Johan G/Template:Welcome to the wiki

Johan G (Talk | contribs) 13:02, 15 April 2019 (EDT)

The template is now moved to {{Welcome to the wiki}}
Johan G (Talk | contribs) 18:19, 17 April 2019 (EDT)
Hi Johan,
The template looks good to me!
Gijs (talk) 06:48, 16 April 2019 (EDT)
It looks good to me too. What about using Extension:Create User Page to fully automate the process?
Bugman (talk) 09:57, 16 April 2019 (EDT)
If you mean as in automatically creating a user discussion page and adding the welcome template? Though it would probably be a good idea, as likely no one will be left without a welcome, it kind of feels better if it is done by a being of flesh and blood than if it was done by a bot. Consider me undecided. ;-)
Johan G (Talk | contribs) 18:13, 17 April 2019 (EDT)
It is a worry that the automation will not seem personal. However I just counted the new user registrations from 17/04/2018 to 17/04/2019. There are 113 registrations! Maybe 5% are not bots, but identifying these is hard. I think it will be too overwhelming for any individual to manually do this.
Bugman (talk) 01:43, 18 April 2019 (EDT)
One registration every second day. Automation might not be such a bad idea after all.
I noticed though that Extension:Create User Page does not create the user discussion page, which is where such messageboxes typically are placed. Maybe not a big problem.
Johan G (Talk | contribs) 12:46, 19 April 2019 (EDT)
A site notice is now up with the text "Hi fellow wiki users!
To help new users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).
I have tried to keep the template short, but meaningful. /Johan G"
Johan G (Talk | contribs) 06:13, 26 April 2019 (EDT)

I just noticed Extension:NewUserMessage which seems perfectly suited to be used the way Bugman mentioned Extension:Create User Page above on 16 April. This extension automatically creates a discussion page with a message for new users. —Johan G (Talk | contribs) 10:44, 22 June 2019 (EDT)

I think we should really use such an extension. There are just too many new user subscriptions to do this manually (and my experience from my own wiki is that 99% of subscriptions are failed bots). I say install it asap. It would really benefit real new users who might be lost under the load of failed bot registrations. Can you install it yourself Johan?
Bugman (talk) 03:50, 2 July 2019 (EDT)
No, I can not install wiki extensions (I am a wiki admin just like you). Simon, the maintainer, can for sure do it and I think that maybe Gijs could do do it.
Johan G (Talk | contribs) 10:21, 4 July 2019 (EDT)
Sent a mail to Gijs and Simon, with a copy to you.
Johan G (Talk | contribs) 12:24, 4 July 2019 (EDT)

Adding it to all user discussion pages?

I have started to wonder if we maybe should add the template to all of the user discussion pages (but not archived ones of course).

What would be the advantages and disadvantages of that. Personally I see more advantages than disadvantages with that.

This would be a bot job of course.

Johan G (Talk | contribs) 08:50, 21 June 2019 (EDT)

The lead section, or first section, as I have called it

Most of the time when I have been writing help pages I have tried to use the terminology used on Wikipedia and its sister projects, but somehow I have called the lead section (or lead or introduction) first section and done that consistently. I have gone through the help pages and changed that.

Johan G (Talk | contribs) 08:56, 23 May 2019 (EDT)


Automated translation for the wikipedia template

Just for the record, I attempted to modify {{wikipedia}} to automatically determine the page language and point to the non-english Wikipedia page without the lang parameter. I have recently added the wikipedia parameter to {{infobox aircraft}} and was hoping to use the language auto-detection to have the wikipedia infobox link point to the correct translation at Wikipedia. I could not use {{PAGELANGUAGE}} as this required MediaWiki >= 1.29 (see [1]). So I unsuccessfully attempted to use the same logic as the {{LangSwitch}} parameter. I reverted all changes as there appears to be no way to correctly detect the page language (other than wait for the next MediaWiki upgrade to expose {{PAGELANGUAGE}}).

Bugman (talk) 05:51, 24 May 2019 (EDT)

Note that this means that the aircraft infobox wikipedia link can only point to the English page until an upgrade occurs (this is not urgent though).
Bugman (talk) 06:01, 24 May 2019 (EDT)
{{lc: {{#titleparts: {{PAGENAME}} | 1}} }} should return the language code needed for the lang= parameter.
Note that you will only be able to pull this of where the article title is exactly the same in another language. If a model for example have have another name in one country (like cars sometimes have) the link will fail. If the title is transcribed the link will fail. Etc.
Johan G (Talk | contribs) 07:16, 24 May 2019 (EDT)

Expansion of the upload licence list and uploading errors

I've always been concerned that we do not present enough licence choices for the graphics uploaded to the wiki. In testing this, I've noticed that I can no longer upload graphics to the wiki! I see a red exclamation mark and the text Unknown error: "unknown", None of the uploads were successful., the button Retry failed uploads, and 0 of 1 file uploaded. Has any one else seen this?

Also, is there a reason we don't update MediaWiki:Licenses? I think I'll add the CC v4.0 licenses so those can be selected. I'll probably also add the GPL.

Bugman (talk) 04:22, 27 May 2019 (EDT)

While I have not tested uploading, according the upload log files were uploaded as recent as the 26th.
Regarding the licenses it might be a good idea to add any missing license templates.
Johan G (Talk | contribs) 08:39, 28 May 2019 (EDT)

Conversion of direct forum links and URLs to templates

I'll continue the discussions of Template talk:Forum link#Usable as replacement for cite web used for forum links? here. After much editing of {{project infrastructure}}, {{project infrastructure option}}, {{forum url}}, and {{forum link}}, I have now gone through the wiki [2] [3] and converted almost all direct links and URLs to the forum to use these new templates. I used macros in vim to simplify and semi-automate the process. There should now be almost no direct references to forum.flightgear.org left. If I have missed anything obvious please point it out to me.

Bugman (talk) 09:49, 6 June 2019 (EDT)

I've found more direct forum links and converted those. However I've also noticed that Special:Search does not reveal all instances of forum.flightgear.org or flightgear.org/forums!? Does anyone know how to hunt down every last direct link? Cheers!
Bugman (talk) 06:17, 7 June 2019 (EDT)
That was huge amount of work. Side note: In disbelief I looked at some of the edits where using the template decreased the article size by several kilobytes.
There is a special page for looking for external links, Special:LinkSearch, that might be useful. Unfortunately it only looks for the domain, so you will have to sift though the results for the relevant hits. (External link search for "*.flightgear.org".)
Johan G (Talk | contribs) 10:19, 7 June 2019 (EDT)
Those articles with big diffs were usually the poor-quality articles pumped full of {{cite web}} text. I used vim macros to quickly convert them, but had to manually check every change to be sure as there were some issues.
I'd completely forgotten about Special:LinkSearch. I had used that previously to convert all repository links to convert the entire wiki to use the Category:Repository link templates template family. I now see that the forum link conversion is a much, much, much bigger job! I currently see:
Unfortunately in converting all the direct links I found via the normal search, I know that we won't be able to automate/script this. There are far too many different ways these forum links are presented. For example a link ending with the anchor #p1234 or simply having p=1234 in the URL can have all other elements (t, f, sid, etc.) removed and drop to simply {{forum link|p=1234}}, with either the text or title parameters specified as needed. Some forum links are unnecessarily long. A link to a post only needs p, a link to a topic only t and a link to a subforum only f. The exception being hilit. However hilit is often present in the URL without any keywords. Then there is also a mix of using = and {{=}} in the URLs. And it is not always completely obvious if {{forum url}} or {{forum link}} should be used. The only regularity is in the {{cite web}} usage, but that also appears to have 3 or 4 forms that have evolved over time.
Bugman (talk) 11:28, 7 June 2019 (EDT)

Update

I've eliminated all flightgear.org/forums hard links on the wiki to use {{forum url}} and {{forum link}}. The numbers are now:

For reference, here are my vim macros. These are placed into the ~/.vimrc file:

" --- FlightGear forum conversions ---
" Link: Convert [http://www.flightgear.org/forums forums] to {{forum link|text=forums}}.
let @f='/[http.*forum^Mv/ ^Mc{{forum link|text=^[/]^Mvc}}^[/forum^MN'
" Link: Convert [http://flightgear.org/forums/viewforum.php?f=13 section of our forum] to {{forum link|f=13|text=section of our forum}}.
let @g='/[http.*forum^Mv/f=^Mhc{{forum link|^[/ ^Mvc|text=^[/]^Mvc}}^[/forum^MN'
" Link: Convert [http://flightgear.org/forums/viewtopic.php?f=5&t=7485#p102005] to {{forum link|p=102005}}.
let @p='/[http.*forum^Mv/#^Mc{{forum link|^[la=^[/]^Mvc}}^[/forum^MN'
" Link: Convert [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14254 thread] to {{forum link|t=14254|text=thread}}.
let @t='/[http.*forum^Mv/t=^Mhc{{forum link|^[/ ^Mvc|text=^[/]^Mvc}}^[/forum^MN'
" Link: Convert [http://flightgear.org/forums/viewtopic.php?f=42&t=15267#p149971 this short essay] to {{forum link|p=149971|text=this short essay}}.
let @s='/[http.*forum^Mv/#^Mc{{forum link|^[la=^[/ ^Mvc|text=^[/]^Mvc}}^[/forum^MN'
" Link: Convert [http://flightgear.org/forums/viewtopic.php?f=2&t=1697&p=12549 ARINC] to {{forum link|p=12549|text=ARINC}}.
let @r='/[http.*forum^Mv/p=^Mhc{{forum link|^[/ ^Mvc|text=^[/]^Mvc}}^[/forum^MN'
" Link: Convert [http://forum.flightgear.org/viewtopic.php?f=79&t=22840] to {{forum link|t=22840}}.
let @l='/[http.*forum^Mv/t=^Mhc{{forum link|^[/]^Mvc}}^[/forum^MN'
" Link: Convert [http://flightgear.org/forums/viewtopic.php?f=28&t=10488&p=144233&hilit=snapshot#p144233 at the forum] to {{forum link|hilit=snapshot|p=144233|text=at the forum}}.
let @i='/[http.*forum^Mv/hilit^Mhc{{forum link|^[/#^Mxi|^[la=^[/ ^[vc|text=^[/]^Mvc}}^[/forum^MN'
" Link: Convert [http://flightgear.org/forums/viewtopic.php?f=17&t=20214&p=186020&hilit=xml+french#p185963] to {{forum link|hilit=xml+french|p=185963}}.
let @j='/[http.*forum^Mv/hilit^Mhc{{forum link|^[/#^Mxi|^[la=^[/]^Mvc}}^[/forum^MN'

" URL: Convert http://flightgear.org/forums/viewtopic.php?f=6&t=14758 to {{forum url|t=14758}}.
let @w='/http.*forum^Mv/t=^Mhc{{forum url|^[llea}}^[/forum^MN'
" URL: Convert http://flightgear.org/forums/viewtopic.php?f=17&t=2766&p=26459&hilit=generic+protocol#p26459 to {{forum url|hilit=generic+protocol|p=26459}}.
let @h='/http.*forum^Mv/hilit^Mhc{{forum url|^[/#^Mxi|^[la=^[ea}}^[/forum^MN'
" URL: Convert http://flightgear.org/forums/viewtopic.php?f=2&t=3430&start=0&st=0&sk=t&sd=a&hilit=oscillations+x to {{forum url|t=3430|hilit=oscillations+x}}
let @b='/http.*forum^Mv/t=^Mhc{{forum url|^[llelv/hilit^Mhxi|^[/.[\n ]^[a}}^[/forum^MN'
" URL: Convert http://www.flightgear.org/forums/viewtopic.php?f=4&t=6890 to {{forum url|t=6890}}.
let @v='/http.*forum^Mi{{forum url|^[lv/t=^Mhxllea}}^[/forum^MN'
" URL: Convert http://flightgear.org/forums/viewtopic.php?f=6&t=3085&p=28982#p28982 to {{forum url|p=28982}}.
let @x='/http.*forum^Mv/#^Mc{{forum url|^[la=^[ea}}^[/forum^MN'
" URL: Convert http://flightgear.org/forums/viewtopic.php?f=6&t=5814&p=44566 to {{forum url|p=44566}}.
let @y='/http.*forum^Mv/p=^Mhc{{forum url|^[llea}}^[/forum^MN'

" Member: Convert [http://www.flightgear.org/forums/memberlist.php?mode=viewprofile&u=510 Gijs] to {{forum list|type=member|u=510|text=Gijs}}.
let @m='/[http.*forum^Mv/member^Mhc{{forum link|type=^[/list^[v/u=^Mhc|^[/ ^[xi|text=^[/]^Mvc}}^[/forum^MN'

" Search: Convert [http://www.flightgear.org/forums/search.php?st=0&amp;sk=t&amp;sd=d&amp;sr=posts&amp;keywords=head+tracking head tracking] to {{forum list|type=search|keywords=head+tracking|text=head tracking}}.
let @a='/[http.*forum^Mv/search^Mhc{{forum link|type=^[/.php^[v/keywords=^Mhc|^[/ ^[xi|text=^[/]^Mvc}}^[/forum^MN'

The ^[ and ^M characters have to be converted into the escape and enter escape sequences for this to work (using e.g. i, ctrl+v, esc, esc and i, ctrl+v, Enter, esc). These handle the forum.flightgear.org hard links as well, but only cover maybe 90% of all hard links. One link that often needs manual intervention is when start=X is in the URL. This requires following the link, finding the post number, and then supplying the p parameter, which is absent from the original URL, to the templates.

Roadmap: Once all the http links are converted, all links will be present in the https search. Then the {{project infrastructure}} template can be modified to produce http forum URLs rather than https. This will cause only the unconverted https links in be present in the https search.

Bugman (talk) 04:19, 11 June 2019 (EDT)

Here is a test of the http to https switch. Before the switch:
And after the switch:
  • http://forum.flightgear.org: 4,127 hits.
  • https://forum.flightgear.org: 835 hits.
  • http://flightgear.org/forums: 0 hits
  • https://flightgear.org/forums: 0 hits
So there are 1914 http:// and 835 https:// forum hard links still to convert!
Bugman (talk) 09:42, 2 July 2019 (EDT)

Language flags on the main page

While activating "Português do Brasil" as a new language on the wiki (via Special:Interwiki), I decided to use a generic white flag for the language on the main page. As an experiment I have added this generic flag for all translations. It is not pretty, but it does better advertise the languages where a flag makes zero sense. Please have a look and see what you think!

Bugman (talk) 04:35, 7 June 2019 (EDT)

I would also like to point out that it is still impossible to edit the wiki in certain languages. See FlightGear wiki:Village pump/Archive 2016#UTF-8 language pages cannot be edited. We really need to fix this database error issue.
Bugman (talk) 05:34, 7 June 2019 (EDT)
Don't worry about the white flag, I've now uploaded public domain icons, taken from Wiki Commons SVG files, for all language flags. For Persian, I've used the Iranian flag. And for Arabic I've used the neutral Arab League flag. So now we have flag icons for all current translations.
Bugman (talk) 05:59, 7 June 2019 (EDT)