Talk:Main Page/Archive/2006-2011: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
m (adding requests for new mediawiki extension: http://www.mediawiki.org/wiki/Extension:Drafts)
(Switch to the {{forum link}} template for all "flightgear.org/forum" forum links.)
 
(34 intermediate revisions by 8 users not shown)
Line 1: Line 1:
{{talk archive}}
= MediaWiki Extension Requests against SPAMING =
Every day a new spam are edit on this WIKI, It's so Boring. Personnaly i havn't right to delete account, and can only delete the Spam.
But if administrator of the wiki can install some of this extension to prevent spamming, it could be very nice... I know there some Capcha installed, apparently is not enough
* http://www.mediawiki.org/wiki/Anti-spam_features
and please read this page http://www.mediawiki.org/wiki/Manual:Combating_spam
Thanks. --[[User:Lolalilo|Lolalilo]] 01:58, 11 February 2011 (EST)
= MediaWiki Extension Requests =
= MediaWiki Extension Requests =
* 02/2010: http://www.mediawiki.org/wiki/Extension:Pdf_Export - exporting to PDF files
* 02/2010: http://www.mediawiki.org/wiki/Extension:Pdf_Export - exporting to PDF files
* 02/2010: http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi - syntax highlighting
* 02/2010: http://www.mediawiki.org/wiki/Extension:Drafts - allow users to save drafts of articles
* 02/2010: http://www.mediawiki.org/wiki/Extension:Drafts - allow users to save drafts of articles
''<small>—This unsigned comment was added by</small>''<small> [[User:MILSTD|MILSTD]] ([[User talk:MILSTD|talk]] • [[Special:Contributions/MILSTD|changes]]) 17:01, 20 February 2010  (UTC)</small>


= CVS vs. Addon-aircraft =
= Translating the wiki (10/2009) =
I notice that the wiki is filled with aircraft projects which are not available per CVS. A lot of are Addons but it keeps unclear where to get them or if they part of the official hangar.
There needs to be a dedicated article about translating individual articles, especially about prioritizing certain articles (based on the [[Special:Statistics|stats]]) and about translation strategies. Also, there should probably be a couple of new templates specifically to be used for translation efforts, such as "translation request" and "translation in progress", as well as "translation help or review required".--[[User:MILSTD|MILSTD]] 18:10, 1 October 2009 (UTC)
Shoulden't be there maybe better a split between CVS and Addon here in the wiki?
[[User:HHS|HHS]] 15:29, 26 October 2009 (UTC)
: Hi,
: it is already possible to add a download link to the aircraft infobox. This should lead to the most up-to-date version of the aircraft (whether that is FlightGear.org, your own website or another third party host. CVS aircraft do not need a download link, as you will get it from the repository anyway. However, I do agree with you that it should be more clear. Do you prefer an "Addon" template (such as [[Template:Stub]]) or an extra option in the infobox? I am open to any idea.<br>Oh, and please sign your messages with four tildes (~) ;)<br>
: [[User:Gijs|Gijs]] 16:38, 26 October 2009 (UTC)
 
::Hi,
::seems, that most of the authors don't know the option of adding a link to their work in the aircraft infobox.
::I would prefer an "Addon"-Template, as it seems to me that a certain number of developers don't want or can't add their work to CVS. This might other developers prevent from developing for CVS. At least it helps to prevent confusion, as people can now see more clear which aircrafts are available per CVS/ official flightgear.org Download page or somewhere else.
::It might be maybe a bit difficult to sort out and convince people to make use of the new template.
::[[User:HHS|HHS]] 17:11, 26 October 2009 (UTC)


:::The template has been created and is available through [[Template:non-stable]]. Please add it to every article that covers an area (whether aircraft, feature, scenery or model) that is not commited to CVS and thus to any stable release. This includes aircraft under licences other than [[GNU GPL]].
Ok, apparently there's something in the works [[Help:Translate]] ''<small>—This unsigned comment was added by</small>''<small> [[User:MILSTD|MILSTD]] ([[User talk:MILSTD|talk]] [[Special:Contributions/MILSTD|changes]]) 18:12, 1 October 2009 (UTC)</small>
:::Regards, [[User:Gijs|Gijs]] 20:57, 26 October 2009 (UTC)


= Translating the wiki (10/2009) =
Also see: {{mediawiki|Extension:Translate}} ''<small>—This unsigned comment was added by</small>''<small> [[User:MILSTD|MILSTD]] ([[User talk:MILSTD|talk]] • [[Special:Contributions/MILSTD|changes]]) 17:01, 20 February 2010  (UTC)</small>
There needs to be a dedicated article about translating individual articles, especially about prioritizing certain articles (based on the [http://wiki.flightgear.org/index.php/Special:Statistics stats]) and about translation strategies. Also, there should probably be a couple of new templates specifically to be used for translation efforts, such as "translation request" and "translation in progress", as well as "translation help or review required".--[[User:MILSTD|MILSTD]] 18:10, 1 October 2009 (UTC)
:: Ok, apparently there's something in the works [[Help:Translate]]
 
Also see: http://www.mediawiki.org/wiki/Extension:Translate


= Planned Wiki Changes & Todo =
= Planned Wiki Changes & Todo =
Please see [[Wiki Plans and Todo]]
Please see [[Wiki Plans and Todo]] ''<small>—This unsigned comment was added by</small>''<small> [[User:MILSTD|MILSTD]] ([[User talk:MILSTD|talk]] • [[Special:Contributions/MILSTD|changes]]) 15:45, 8 April 2009  (UTC)</small>


= Making the manual accessible via wiki software =
= Making the manual accessible via wiki software =
Line 34: Line 29:
A possible approach might be to import the underlying LaTex sources in docbook format into some sort of docbook based wiki (i.e. http://sourceforge.net/projects/doc-book/).
A possible approach might be to import the underlying LaTex sources in docbook format into some sort of docbook based wiki (i.e. http://sourceforge.net/projects/doc-book/).


As the manual is maintained in LaTex, is would be very hard to translate the wiki notes to include them in the manual. I suspect that this will be a "Won't Fix" as it is easier to copy and paste the text from the wiki and go from there. I am open to ideas though. [[User:Gorilla|Gorilla]] 06:33, 2 March 2008 (EST)
''<small>—This unsigned comment was added by</small>''<small> [[User:Melchior FRANZ|Melchior FRANZ]] ([[User talk:Melchior FRANZ|talk]] • [[Special:Contributions/Melchior FRANZ|changes]]) 12:48, 18 July 2006  (UTC)</small>
 
:As the manual is maintained in LaTex, is would be very hard to translate the wiki notes to include them in the manual. I suspect that this will be a "Won't Fix" as it is easier to copy and paste the text from the wiki and go from there. I am open to ideas though. [[User:Gorilla|Gorilla]] 06:33, 2 March 2008 (EST)


= Using a dedicated FAQ database =
= Using a dedicated FAQ database =
Also, I feel there are some sections covered in the wiki that aren't really optimally handled by a wiki: most notably the "FAQ" section should preferably be implemented via some sort of dynamic FAQ system (i.e. http://www.phpmyfaq.de), likewise the sections titled "Bugs", "TODO", "Feature Requests", "ideas" etc. could probably all be handled far more effectively by using a real bug tracker such as bugzilla (http://www.bugzilla.org/), phpbugtracker (http://phpbt.sourceforge.net/) or mantis (http://www.mantisbt.org).
Also, I feel there are some sections covered in the wiki that aren't really optimally handled by a wiki: most notably the "FAQ" section should preferably be implemented via some sort of dynamic FAQ system (i.e. http://www.phpmyfaq.de), likewise the sections titled "Bugs", "TODO", "Feature Requests", "ideas" etc. could probably all be handled far more effectively by using a real bug tracker such as bugzilla (http://www.bugzilla.org/), phpbugtracker (http://phpbt.sourceforge.net/) or mantis (http://www.mantisbt.org).


= Using a dedicated bug tracker =
''<small>—This unsigned comment was added by</small>''<small> [[User:Melchior FRANZ|Melchior FRANZ]] ([[User talk:Melchior FRANZ|talk]] • [[Special:Contributions/Melchior FRANZ|changes]]) 12:48, 18 July 2006  (UTC)</small>


A couple of days ago I started setting up a local test bugZilla installation, while I am currently unable to provide reliable hosting, I would really not mind installing it on whatever webspace is available, likewise I can provide the preconfigured database dump if someone else wants to use the preconfigured Flightgear specific categories.--[[User:FlightZilla|FlightZilla]] 17:59, 17 June 2006 (EDT)
* how to define and limit editing rights for certain users? ''<small>—This unsigned comment was added by</small>''<small> [[User:Alfozavr|Alfozavr]] ([[User talk:Alfozavr|talk]] • [[Special:Contributions/Alfozavr|changes]]) 10:57, 17 June 2007 (UTC)</small>
 
NOTE: As of 02/2010, a google code tracker is used for bug tracking:
Also, see this wikimedia extension: http://www.mediawiki.org/wiki/Extension:IssueTracker
 
* how to define and limit editing rights for certain users?
 
It's better to have one consolidated source of information for both bugs and descriptions. For now, user has to search through mailing lists, forums, user manuals (even not a single user manual, but several) and this wiki. It's absolutely not convinient for both users (they spend lot's of time searching required information) and developers (they spend lot's of time updating and syncronizing certain information in various sources).
 
This wiki is suitable for bug tracking too. Users can provide feedback in a convinient form. They just open the corresponding page and add their bug to the list. Developers can respond to the posted bugs right away. Mailing lists are a lot less user-friendly and effective and a lot less popular among users (not developers) in this regard, this is the reason why some bugs may stay unreported and why many users forget about FlightGear as soon as they run into a problem.
 
Unfortunately, it seems to me, this wiki is not popular among developers and users. -- [[User:Alfozavr|Alfozavr]] 06:59, 17 June 2007 (EDT)
 
10/2009: Bug tracking has -again- become an issue [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23799.html]


= Backups =
= Backups =
Line 60: Line 44:
--[[User:MILSTD|MILSTD]] 15:25, 4 February 2008 (EST)
--[[User:MILSTD|MILSTD]] 15:25, 4 February 2008 (EST)


Yes, there are daily backups of the [http://hellosimon.org/backups code] and of the [http://hellosimon.org/backups/mysql database].  We also have off-site backups.  [[User:Hellosimon|Hellosimon]] 17:04, 4 February 2008 (EST)
:Yes, there are daily backups of the [http://hellosimon.org/backups code] and of the [http://hellosimon.org/backups/mysql database].  We also have off-site backups.  [[User:Hellosimon|Hellosimon]] 17:04, 4 February 2008 (EST)
----


= Updates =
= Updates =
Line 68: Line 51:


The wiki has moved to a new server which should relieve the performance problems.  [[User:Hellosimon|Hellosimon]] 11:26, 10 June 2008 (EDT)
The wiki has moved to a new server which should relieve the performance problems.  [[User:Hellosimon|Hellosimon]] 11:26, 10 June 2008 (EDT)
== Regressions ==
* code passages (i.e. XML) are not highlighted anymore


= Proposed Additions =
= Proposed Additions =
Line 78: Line 58:
* needs screenshots
* needs screenshots
* needs better layout
* needs better layout
== Syntax Highlighting ==
''<small>—This unsigned comment was added by</small>''<small> [[User:MILSTD|MILSTD]] ([[User talk:MILSTD|talk]] [[Special:Contributions/MILSTD|changes]]) 03:32, 16 May 2009  (UTC)</small>
* what about some sort of true syntax-highlighting module, that would properly highlight XML & C++ ?
:: This can be achieved using the [http://qbnz.com/highlighter/ GeSHi] syntax highlighting module for php.
::: With XML, C, C++ and Nasal source code being increasingly used on various wiki pages, this would be an important and huge step towards improving this wiki!
 
== Main Page Addition ==
 
* Add Link on Main Page to the list of howtos
 
[[:Category:Howto|List of all Howtos]]
 
Do edits of the main page warrant discussion or do people just to it?


I Just did it...
:Also a template for the FlightGear news would be perfect to keep them synchronized on the different pages (especially the translations of the Main Page) ''<small>—This unsigned comment was added by</small>''<small> [[User:Hamster|Hamster]] ([[User talk:Hamster|talk]] • [[Special:Contributions/Hamster|changes]]) 21:42, 17 September 2011  (UTC)</small>
::I've just created a [[Template:News|news template]] and added it to all main pages. Please check for your own language whether this works and is up to date (some are not). For the other templates, we do have [[Template:Cleanup]]. And I just created [[Template:Image requested]] and added a "reason" variable to the cleanup template (where you can say it needs a spelling check)
::[[User:Gijs|Gijs]] 07:12, 18 September 2011 (EDT)
::PS: Please sign your messages on talk pages with <nowiki>~~~~</nowiki>


== PDF Export ==
== PDF Export ==
*  PDF Export - [http://sourceforge.net/projects/wikipdf/ Wikimedia plugin to export to PDF]
*  PDF Export - [http://sourceforge.net/projects/wikipdf/ Wikimedia plugin to export to PDF] ''<small>—This unsigned comment was added by</small>''<small> [[User:MILSTD|MILSTD]] ([[User talk:MILSTD|talk]] • [[Special:Contributions/MILSTD|changes]]) 14:38, 31 January 2008  (UTC)</small>
* http://www.mediawiki.org/wiki/Extension:WikiPDF - WikiPDF is an extension for MediaWiki, which converts MediaWiki-articles to LaTeX or PDF.
:* {{mediawiki|Extension:WikiPDF}} - WikiPDF is an extension for MediaWiki, which converts MediaWiki-articles to LaTeX or PDF. ''<small>—This unsigned comment was added by</small>''<small> [[User:MILSTD|MILSTD]] ([[User talk:MILSTD|talk]] • [[Special:Contributions/MILSTD|changes]]) 15:07, 28 December 2009  (UTC)</small>




Line 105: Line 77:
--[[User:FlightZilla|FlightZilla]] 17:21, 19 June 2006 (EDT)
--[[User:FlightZilla|FlightZilla]] 17:21, 19 June 2006 (EDT)


Hello, guys. If I get it right, you're discussing various documentation types here.
:Hello, guys. If I get it right, you're discussing various documentation types here.


I think, this wiki is a lot more convenient than any other form of keeping documentation and at the same time communicating. It can be edited fast and easily and maintained up-to-date. However, the following questions need be solved:
:I think, this wiki is a lot more convenient than any other form of keeping documentation and at the same time communicating. It can be edited fast and easily and maintained up-to-date. However, the following questions need be solved:
* how to convert it to an offline version (maybe .pdf) so that it could be bundled with the FlightGear base package?
:* how to convert it to an offline version (maybe .pdf) so that it could be bundled with the FlightGear base package?
:''<small>—This unsigned comment was added by</small>''<small> [[User:Alfozavr|Alfozavr]] ([[User talk:Alfozavr|talk]] • [[Special:Contributions/Alfozavr|changes]]) 10:57, 17 June 2007  (UTC)</small>


07/2009: Even more talk about the merits of supporting PDF exports for wiki articles: [http://flightgear.org/forums/viewtopic.php?f=6&t=5201&p=39847#p39847]
::07/2009: Even more talk about the merits of supporting PDF exports for wiki articles: {{forum link|p=39847}} ''<small>—This unsigned comment was added by</small>''<small> [[User:MILSTD|MILSTD]] ([[User talk:MILSTD|talk]] • [[Special:Contributions/MILSTD|changes]]) 14:36, 9 July 2009  (UTC)</small>


12/2009: Also see [http://www.mediawiki.org/wiki/DocBook_XML_export] for details about exporting to docbook/XML
:::12/2009: Also see {{mediawiki|DocBook XML export}} for details about exporting to docbook/XML ''<small>—This unsigned comment was added by</small>''<small> [[User:MILSTD|MILSTD]] ([[User talk:MILSTD|talk]] • [[Special:Contributions/MILSTD|changes]]) 15:05, 28 December 2009  (UTC)</small>


= Issues =  
= Issues =  


== 12/2009: 503 Error Resource limit exceeded ==
== Image Upload Rules ? ==
The wiki needs to be relocated to a different server, maybe it could be directly hosted on flightgear.org?
If you are seeing this page, your site is exceeding the allowed resources on the server.
[[User:MILSTD|MILSTD]]


==Formatting problem==
I have noticed that many imagess on the wiki are .png files. We could save several GBs just by converting .pngs to .jpeg files.  
The POTD does not format correctly at 1024x768 in Firefox, the text on most POTD creates a large space above and below the image. The POTD needs to either have a full page width, or much less text, or some other change in the formatting. [[User:Fg|Fg]] 15:50, 29 September 2008 (EDT)
Would it be an idea to discourage people to upload .png files, and to upload .jpegs?
: I will see what I can do about this tomorrow. Maybey I will add the picture above the text. In the meantime, please leave the colors as they are. Green is still FlightGear's main color... Thanks, [[User:Gijs|Gijs]] 17:17, 29 September 2008 (EDT)
--[[User:Armchair Ace|Armchair Ace]] 08:51, 25 April 2010 (UTC)
:Pictures are now centered above the text. Is it okay now? Btw: you could add more to! Just be sure you don't copy old ones. [[User:Gijs|Gijs]] 07:35, 1 October 2008 (EDT)
::Great! That fixed it and I will add some POTD. Also, I would prefer grey or blue for main color. [[User:Fg|Fg]] 15:16, 2 October 2008 (EDT)
:::Ok, that's nice. About the color: if we make it blue, the whole page is blue, because the links are also blue. Grey is in no way connected to FlightGear. Since we already have a different logo than the main FlighGear project it would be nice to have some sort of recognition for our users. I also don't like the standard style of this wiki (I use Monobook, like Wikipedia.org does), but that is probably an issue of taste. [[User:Gijs|Gijs]] 15:55, 2 October 2008 (EDT)
::I use monobook also and I agree about the standard style, but I would prefer some more variety in the color at some point. [[User:Fg|Fg]] 16:51, 2 October 2008 (EDT)
:::Well, give some arguments why we should have various colors? We could make a poll on the forum to see what others think... [[User:Gijs|Gijs]] 09:57, 3 October 2008 (EDT)
::::On this page here http://www.flightgear.org/Downloads/ or even here http://www.flightgear.org/introduction.html they use light grey in the headers rather than green( if the goal is to be like the website). I would enjoy any number of other colors though, if you had a interest in changing from the current green (even another shade of green for instance). I understand if you just want to continue with the current color though. [[User:Fg|Fg]] 16:48, 4 October 2008 (EDT)
:::::The content is already grey backgrounded. So a grey "header" color wouldn't be visible. Let's just keep it green and concentrate us on the index and quality of the articles and portals. Neverthless, thanks for all your help and sharing your thoughts! [[User:Gijs|Gijs]] 17:14, 4 October 2008 (EDT)

Latest revision as of 13:30, 6 June 2019

Replacement filing cabinet.png This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.


MediaWiki Extension Requests against SPAMING

Every day a new spam are edit on this WIKI, It's so Boring. Personnaly i havn't right to delete account, and can only delete the Spam. But if administrator of the wiki can install some of this extension to prevent spamming, it could be very nice... I know there some Capcha installed, apparently is not enough

and please read this page http://www.mediawiki.org/wiki/Manual:Combating_spam

Thanks. --Lolalilo 01:58, 11 February 2011 (EST)

MediaWiki Extension Requests

—This unsigned comment was added by MILSTD (talkchanges) 17:01, 20 February 2010 (UTC)

Translating the wiki (10/2009)

There needs to be a dedicated article about translating individual articles, especially about prioritizing certain articles (based on the stats) and about translation strategies. Also, there should probably be a couple of new templates specifically to be used for translation efforts, such as "translation request" and "translation in progress", as well as "translation help or review required".--MILSTD 18:10, 1 October 2009 (UTC)

Ok, apparently there's something in the works Help:Translate —This unsigned comment was added by MILSTD (talkchanges) 18:12, 1 October 2009 (UTC)

Also see: mw:Extension:Translate —This unsigned comment was added by MILSTD (talkchanges) 17:01, 20 February 2010 (UTC)

Planned Wiki Changes & Todo

Please see Wiki Plans and Todo —This unsigned comment was added by MILSTD (talkchanges) 15:45, 8 April 2009 (UTC)

Making the manual accessible via wiki software

On the other hand, I would recommend to also look into making "The Manual" editable via some sort of web based frontend, this would also ensure that people are able to easily contribute modifications to the manual, which is really the ultimate source for flightgear users. A possible approach might be to import the underlying LaTex sources in docbook format into some sort of docbook based wiki (i.e. http://sourceforge.net/projects/doc-book/).

—This unsigned comment was added by Melchior FRANZ (talkchanges) 12:48, 18 July 2006 (UTC)

As the manual is maintained in LaTex, is would be very hard to translate the wiki notes to include them in the manual. I suspect that this will be a "Won't Fix" as it is easier to copy and paste the text from the wiki and go from there. I am open to ideas though. Gorilla 06:33, 2 March 2008 (EST)

Using a dedicated FAQ database

Also, I feel there are some sections covered in the wiki that aren't really optimally handled by a wiki: most notably the "FAQ" section should preferably be implemented via some sort of dynamic FAQ system (i.e. http://www.phpmyfaq.de), likewise the sections titled "Bugs", "TODO", "Feature Requests", "ideas" etc. could probably all be handled far more effectively by using a real bug tracker such as bugzilla (http://www.bugzilla.org/), phpbugtracker (http://phpbt.sourceforge.net/) or mantis (http://www.mantisbt.org).

—This unsigned comment was added by Melchior FRANZ (talkchanges) 12:48, 18 July 2006 (UTC)

  • how to define and limit editing rights for certain users? —This unsigned comment was added by Alfozavr (talkchanges) 10:57, 17 June 2007 (UTC)

Backups

Is the database regularly backed up? What about hosting the wiki directly at flightgear.org? --MILSTD 15:25, 4 February 2008 (EST)

Yes, there are daily backups of the code and of the database. We also have off-site backups. Hellosimon 17:04, 4 February 2008 (EST)

Updates

I've updated MediaWiki to 1.11.1 so if you notice any regressions let me know. Hellosimon 15:03, 2 March 2008 (EST)

The wiki has moved to a new server which should relieve the performance problems. Hellosimon 11:26, 10 June 2008 (EDT)

Proposed Additions

New Templates

Some wiki pages are of relatively poor quality, having some templates to elicit help would be useful, such as for example:

  • needs review by native English speaker
  • needs screenshots
  • needs better layout

—This unsigned comment was added by MILSTD (talkchanges) 03:32, 16 May 2009 (UTC)

Also a template for the FlightGear news would be perfect to keep them synchronized on the different pages (especially the translations of the Main Page) —This unsigned comment was added by Hamster (talkchanges) 21:42, 17 September 2011 (UTC)
I've just created a news template and added it to all main pages. Please check for your own language whether this works and is up to date (some are not). For the other templates, we do have Template:Cleanup. And I just created Template:Image requested and added a "reason" variable to the cleanup template (where you can say it needs a spelling check)
Gijs 07:12, 18 September 2011 (EDT)
PS: Please sign your messages on talk pages with ~~~~

PDF Export

  • mw:Extension:WikiPDF - WikiPDF is an extension for MediaWiki, which converts MediaWiki-articles to LaTeX or PDF. —This unsigned comment was added by MILSTD (talkchanges) 15:07, 28 December 2009 (UTC)


Regarding the manual: isn't there a possibility to export wikimedia pages to PDF format? That way, we could maintain the whole manual via this wiki. Any thoughts?--FlightZilla 18:10, 17 June 2006 (EDT)

If you check out the following links, you'll see that there are extensions available that would make it possible to easily provide PDF exports for all contents stored here, that way it would also become feasible to consider migrating the entire manual over to this wiki, so that it would also become more maintainble in the end: http://meta.wikimedia.org/wiki/WikiPDF http://meta.wikimedia.org/wiki/PDF_Export --FlightZilla 17:21, 19 June 2006 (EDT)

Hello, guys. If I get it right, you're discussing various documentation types here.
I think, this wiki is a lot more convenient than any other form of keeping documentation and at the same time communicating. It can be edited fast and easily and maintained up-to-date. However, the following questions need be solved:
  • how to convert it to an offline version (maybe .pdf) so that it could be bundled with the FlightGear base package?
—This unsigned comment was added by Alfozavr (talkchanges) 10:57, 17 June 2007 (UTC)
07/2009: Even more talk about the merits of supporting PDF exports for wiki articles: [1] This is a link to the FlightGear forum. —This unsigned comment was added by MILSTD (talkchanges) 14:36, 9 July 2009 (UTC)
12/2009: Also see mw:DocBook XML export for details about exporting to docbook/XML —This unsigned comment was added by MILSTD (talkchanges) 15:05, 28 December 2009 (UTC)

Issues

Image Upload Rules ?

I have noticed that many imagess on the wiki are .png files. We could save several GBs just by converting .pngs to .jpeg files. Would it be an idea to discourage people to upload .png files, and to upload .jpegs? --Armchair Ace 08:51, 25 April 2010 (UTC)