Factorio:Wiki rules: Difference between revisions

From Official Factorio Wiki
Jump to navigation Jump to search
(Fixed grammar mistakes, fixed incorrect syntax, improved clarity for English readers. Tried to keep all ideas intact.)
Line 7: Line 7:
If you  need more rights to the wiki (deletion, moving...) you need to ask the devs directly, or ask in the forum board.
If you  need more rights to the wiki (deletion, moving...) you need to ask the devs directly, or ask in the forum board.


==  How to understand the wiki? ==
==  Understanding the wiki ==


There is currently an forum article, which should give you a good introduction, how this wiki works: http://www.factorioforums.com/forum/viewtopic.php?f=50&t=5994&p=46947#p46749
There is currently a forum article which should give you a good introduction to how the wiki works: http://www.factorioforums.com/forum/viewtopic.php?f=50&t=5994&p=46947#p46749


== How to contribute? ==
== Contributing to the wiki ==


This wiki is the work of a team. The people like to add information or bring it into better context, or they are doing videos, or design web pages.
This wiki is the work of a team. The goal is for people to add information or bring it into better context, do videos, or design the layout of the pages.


The team communicates through the talk-pages ("Discussion" folder at the top) or through the forum ( http://www.factorioforums.com/forum/viewforum.php?f=50 ). It is very important to look into the "Recent changes", so that you see, if someone modified a page (especially a talk:-page), in which you are interested.
The team communicates through the talk-pages ("Discussion" folder at the top) or through the forum ( http://www.factorioforums.com/forum/viewforum.php?f=50 ). It'ss very important to look at the "Recent changes", so that you see if someone modified a page (especially a talk:-page), in which you are interested.


(BTW: You can change the shown results in the preferences!)
(BTW: You can change the shown results in the preferences!)


There are different jobs you can do. We begin from simple to complex.
There are different jobs you can do. This list is from simple to complex.


=== Corrector ===
=== Corrector ===


Read through the pages (of your language) and correct mistakes or bad language use. If it sounds ugly then change it. If you do so, you'll see walls of text. This is how mediawiki works. Sorry, but it's the way you'll learn to do more. :)
Read through the pages (of your language) and correct mistakes or bad language use. If it sounds ugly then change it. If you're new to wiki's it might be difficult at first, but keep at it and you'll learn to do more. :)  


=== Translator ===
=== Translator ===


Take an English page, copy the content into a subpage (see down, what we mean!) and translate.
Take an English page, copy the content into a subpage (see below for an explanation) and translate.


=== Writer and Linker ===
=== Writer and Linker ===


If someone asks something in the forum, and there is a good answer, it's a good idea to add that information into the wiki. No special knowledge is needed for that, just search the right page, the right chapter or add a new and write and if it is ok, it isn't deleted by the next. :)
If you find good information in the forums, it's a good idea to add that information to the wiki. No special knowledge is needed, just search the right page, the right chapter, or add a new page and make it. If it isn't okay the next user will take care of it. :)
Sometimes you don't have time for writing it all out. That's okay, just follow the steps below. Someone else might see it and add the relevant information.


Sometimes you don't have time for that, but you read an interesting fact about Factorio, you found something interesting fact? Some quite interesting information in the forum?
* Step 1: Simply copy the link and put it into the right page under "See also". This is to document the link for later usage.
 
* Step 2: The next person who sees it and has time will take the information from the linked page and will add it to the wiki.
* Stage 1: Simply copy the link and put it into the right page under "See also". This is to document: look, this belongs also to this page, but I don't have time yet.
* Step 3: If the sub information is too big or too long, then move it to a subpage. (There are some examples in the wiki on how to use subpages, in general it's just adding a "/subpage name" to the existing page.)
* Stage 2: the next, who reads it, and has time, takes the condensed information from that link writes it into the page. That should normally be enough.
* Stage 3: if that sub information is too big, or if there are some more information about that, then move it to a subpage. (There are some examples in the wiki, how to use subpages, in general it's just adding a "/subpage name" to the existing.)


=== News-maker ===
=== News-maker ===


There are the [[News]]-page. Just add new links, as interesting new information comes out. The rest is explained into the page as comment, just make it equally.
There is the [[News]]-page. Just add new links as new interesting information comes out. The rest is explained in the page as comments.


Is this a news or not? Good question. See it from historical point of view: when you will go back to the older news, will your news be still relevant?
Ask yourself: Is this news or not? See it from historical point of view: When you go back to older news, will it still relevant?


=== Designer ===
=== Designer ===
Line 49: Line 48:
This is about the look and feel of this wiki. It is quite interesting what can be done with such relatively simple nesting. But it is also quite confusing. :)
This is about the look and feel of this wiki. It is quite interesting what can be done with such relatively simple nesting. But it is also quite confusing. :)


Deep knowledge of Mediawiki's template system is not really needed, but will help. For the beginning just try to understand, how the current templates work. Make your own test-page in your user-space and try to program around. It can make really fun, cause this task is more or less like programming.
Deep knowledge of Mediawiki's template system is not really needed, but will help. For the beginning just try to understand how the current templates work. Make your own test-page in your user-space and try to program around. It can make really fun because this task is more or less like programming.
 
Look here for  a first idea, how it works: http://www.factorioforums.com/forum/viewtopic.php?f=50&t=5994&p=46947#p46749


Look here for some help: http://www.mediawiki.org/wiki/Help:Contents
And for some extra help: http://www.factorioforums.com/forum/viewtopic.php?f=50&t=5994&p=46947#p46749
=== Tutor for beginners ===
=== Tutor for beginners ===


This is about writing tutorials. How to make things in factorio. This is currently a problem, cause the game changes and will change. The plans are to be about "ready" in summer 2015. So if you write a tutorial now it will be outdated in a few month.
This is about writing tutorials. Helping beginners understand the game and explain how to do things in-game. This is currently a problem since the game changes. The plan is to be about ready in summer 2015. So if you write a tutorial now it will be outdated in a few months. But don't let this discourage you. If an update makes your tutorial obsolete, just update the tutorial to fit the most recent update.


Nonetheless this job is needed, cause more and more will ask for beginner tutorials and it shows up more and more, that this is really read and used, so by writing/recording (videos are welcome) you can influence how the community will play this game.
Pictures and videos are encouraged since they make understanding a tutorial a lot easier.


=== Architect ===
=== Architect ===


The wiki is created in an agile process: writing, reading, playing. :) When you found out, that this process is somehow inefficient, cause the things are not, where you expect them, then you need to change the wiki in general.
The wiki is created in an agile process: writing, reading, testing. :) If you find out that this process is somehow inefficient, for example the changes are in the wrong place, then you need to change the wiki in general.


This is for example currently the case for the whole "networks" they are not longer a good idea. The logistic network and robotic network are in truth a "robotic system", which contains a construction- and a logistic-area. And the logistic area can be extended over the logistic network.
This is for example currently the case for the whole "networks". They are no longer a good idea. The logistic network and robotic network are in truth a "robotic system", which contains a construction- and a logistic-area. And the logistic area can be extended over the logistic network.


So the job of an architect is to bring the existing pages into the right context by adding some new pages and/or renaming existing, then change the links to the pages. And sometimes old stuff must be deleted.
So the job of an architect is to bring the existing pages into the right context by adding some new pages and/or renaming existing pages, and then changing the links to the pages. And sometimes old stuff must be deleted.


=== Dowhateveryouwant ===
=== Dowhateveryouwant ===


These "roles" are not fixed! Of course. There is no rule saying, that a translator cannot write poems about the deep insights he has gained by playing Factorio. And there are eventually also a audience, which will like that. (I mean that seriously.)
These "roles" are not fixed! There is no rule saying, that a translator cannot write poems about the deep insights he has gained by playing Factorio. And there will eventually also be an audience which will like that. (I mean that seriously.)


So, if you have an idea:
So, if you have an idea:
* '''Don't be afraid: There is nothing, which you can really break, because the wiki has a version history.
* '''Don't be afraid: There is nothing which you can really break, the wiki has a version history.
* If you are still afraid: You can use first a test page in your home-space. That's the pages beginning with "User:<your user name>". You can add a subpage like "User:<your user name>/MyTests". Ask others, what they think about it. Communicate!
* If you are still afraid: You can use the a test page in your home-space. That's the page beginning with "User:<your user name>". You can add a subpage like "User:<your user name>/MyTests". Ask others what they think about it. Communicate!
* Begin with slight changes. The others will watch (the "Recent changes" is important). If after a week or two is no response/follow up change, your change was good. Keep going, make bigger changes.
* Begin with slight changes. The others will watch (the "Recent changes") and help you out. If after a week or two is no response/follow up change, your change was good. Keep going, make bigger changes.


== Basic ==
== Basic ==
Line 80: Line 79:
** If you don't like something, change it.
** If you don't like something, change it.
** If you find typos, change it.
** If you find typos, change it.
** If you find something is wrong described, make a prove, that it is wrong and change it.
** If you find something is wrong described, make a proof that it is wrong and change it.


== Advanced ==
== Advanced ==


* Add missing information at the right place.
* Add missing information in the right places.
: This is in most cases easy, but sometimes could be really difficult. Ask for help if you don't know.
: This is in most cases easy, but sometimes could be really difficult. Ask for help if you're unsure.


* Split the information on big pages into subpages.
* Split the information on big pages into subpages.
: See for example the [[Railway network]].
: See for example the [[Railway network]].


* If you find that a topic belongs to two pages, then don't copy the information into the two pages, but create a new page and link.
* If you find that a topic belongs to two pages, then don't copy the information into the two pages, but create a new page and link them.
: Best example for this is the [[Power Production]] page.
: Best example for this is the [[Power Production]] page.


* Take the right words.
* Use the right words.
: Factorio has a set of words, which have a fixed meaning. For example: an entity can be mined, an item can be picked up. Removing them means something different! Ask the factorio wiki, if you are unsure.
: Factorio has a set of words which have a fixed meaning. For example: an entity can be mined, an item can be picked up. Removing them means something different! Ask the users if you are unsure which is which.


* A picture says more than 1000 words.
* A picture says more than a thousand words.
: Make pictures, if possible. In some case use GIFs! See down.
: Use pictures if possible. In some case use GIFs! See below.


* You can also go to the [[Wiki To-do List]] and look, if there is a job you like.
* You can also go to the [[Wiki To-do List]] and see if there is a job you like.


== Discussions ==
== Discussions ==
Line 107: Line 106:
=== Existing discussions ===
=== Existing discussions ===


In the descending order of date:
In descending order of date:


http://www.factorioforums.com/forum/viewtopic.php?f=5&t=2047
http://www.factorioforums.com/forum/viewtopic.php?f=5&t=2047
Line 127: Line 126:
=== This is how it should work ===
=== This is how it should work ===


This method is used by the Mediawiki-Team and we want to adapt it. Example:
This method is used by the Mediawiki-Team and we want to adapt it. Examples:


http://www.mediawiki.org/wiki/Help:Navigation The english default
http://www.mediawiki.org/wiki/Help:Navigation The English default


http://www.mediawiki.org/wiki/Help:Navigation/es Spanish translation
http://www.mediawiki.org/wiki/Help:Navigation/es Spanish translation
   
   
http://www.mediawiki.org/wiki/Help:Navigation/de German tranlation
http://www.mediawiki.org/wiki/Help:Navigation/de German translation


http://www.mediawiki.org/wiki/Help:Navigation/ru Russian translation
http://www.mediawiki.org/wiki/Help:Navigation/ru Russian translation
Line 141: Line 140:
* The default language is English.
* The default language is English.
* Any other language has no right to obtain a pagename, which collides with English.
* Any other language has no right to obtain a pagename, which collides with English.
* No other language has the right to use a pagename, which means the same or something different in another language.
* No other language has the right to use a pagename which means the same or something different in another language.


==== This is the logical consequence of the above rules ====
==== This is the logical consequence of the above rules ====


* Let's say we have a page named [[Transport network]].  
* Let's say we have a page named [[Transport network]].  
* Now someone translate that page to German: Because he doesn't know better, he names the page "[[Transport netzwerk]]".
* Now someone translates that page to German: Because he doesn't know better, he names the page "[[Transport netzwerk]]".
* This is a mess! Because for example in Swedish (it's just an example) this is also the translated pagename.
* This is a mess! Because for example in Swedish (it's just an example) this is also the translated pagename.
* What's now right? Is [[Transport netzwerk]] now a German or a Swedish page?
* What's now right? Is [[Transport netzwerk]] now a German or a Swedish page?
Line 158: Line 157:
''Yes, but it is the only way to keep the namespace clean.''
''Yes, but it is the only way to keep the namespace clean.''


And there is nothing about making a redirect page [[Transport netzwerk]] which redirects to [[Transport network/de]]. Or make a page where the user can choose if he wants the German or Swedish page.
And there is nothing wrong about making a redirect page [[Transport netzwerk]] which redirects to [[Transport network/de]]. Or make a page where the user can choose if he wants the German or Swedish page.


=== So what do I need to do now? ===
=== So what do I need to do now? ===
Line 164: Line 163:
* If you want to translate a page, then do not rename the page, just add a "/" and the [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes standard macro-language-code] to the pagename.
* If you want to translate a page, then do not rename the page, just add a "/" and the [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes standard macro-language-code] to the pagename.
: "Inserters" becomes "Inserters/fr" for France, "Inserters/ru" for Russian etc.
: "Inserters" becomes "Inserters/fr" for France, "Inserters/ru" for Russian etc.
* If you are working on a page, which has a translated pagename then rename (Move) it! Search the orginal pagename, add the language-code (see above) and move it to the new pagename. A redirect is automatically left for the old pagename!
* If you are working on a page, which has a translated pagename then rename (Move) it! Search the original pagename, add the language-code (see above), and move it to the new pagename. A redirect is automatically left for the old pagename!


(More to explain, language macro, see main-page at top right)
(More to explain, language macro, see main-page at top right)
Line 172: Line 171:
=== Picture formats ===
=== Picture formats ===


For making it simple we should use only formats based on 100. This is to avoid different sized pics which look staggered. This is especially important for the width, for the height it is not that problem. For example: 200x200, 300x100, 400x232. For existing pics (old pics use often a width of 256 px) reduce the with in text to 200 px (and analogous).
For making things simple we should use only formats based on 100. This is to avoid different sized pics which look staggered. This is especially important for the width, for the height it is not that problem. For example: 200x200, 300x100, 400x232. For existing pics (old pics use often a width of 256 px) reduce the text to 200 px (and analogous).


* (100 - 200) x (100-300) px
* (100 - 200) x (100-300) px
: for flowing in the text, pictures which explain the text, the browser can embed this into it's own rendering. You can put them left or right, the text should flow around.
: For flowing with the text, pictures which explain the text, the browser can embed this into it's own rendering. You can put them left or right, the text should flow around.
* (400 - 600) x (100 - 600) px
* (400 - 600) x (100 - 600) px
: Something like a banner. A big pic which stays alone in its line. You may put simply a ":" in front of it to intend the pic and keep it away from flowing text.
: Something like a banner. A big picture which stays alone in its line. You may put simply a ":" in front of it to indent the picture and keep it away from flowing text.
* 300 x 300 px
* 300 x 300 px
: This is especially for gif animations. Gif animations cannot be reduced in size, cause mediawiki re-renders the picture and the result is the first frame of the gif! See for example these pics: http://www.factorioforums.com/wiki/index.php?limit=200&ilsearch=Mpstark&user=&title=Special%3AListFiles
: This is especially for gif animations. Gif animations cannot be reduced in size, because mediawiki re-renders the picture and the result is the first frame of the gif! See for example these pics: http://www.factorioforums.com/wiki/index.php?limit=200&ilsearch=Mpstark&user=&title=Special%3AListFiles
* the biggest format for flowing text should be: 600x600px
* The biggest format for flowing text should be: 600x600px


=== Making pictures out of the game ===
=== Making pictures out of the game ===
Line 186: Line 185:
Do's:
Do's:


* Take pictures at day! [[Lua/Game#alwaysday|Turn on daylight]]! Use night or dawn only, if needed to explain something.
* Take pictures at day! [[Lua/Game#alwaysday|Turn on daylight]]! Use night or dawn only if you need to explain something that only works at night.
* Turn off clouds! The shadows are especially in GIF-animations not useful.
* Turn off clouds! The shadows in GIF-animations are not useful.
* Steam/smoke is also not so useful.
* Steam/smoke is also not so useful.
* Use god mode! [[Lua/Player#controllertype]]. You can go to every place and don't stand in the way of the picture.
* Use god mode! [[Lua/Player#controllertype]]. You can go to every place and won't stand in the way of the picture.
* You can [[Lua/Game#speed|slowdown the game]] to find the right moment for the picture. Slowdown is also useful, if you use Gifcam, which makes screenshoot in 30 frames/sec only.
* You can [[Lua/Game#speed|slowdown the game]] to find the right moment for the picture. Slowdown is also useful, if you use Gifcam, which makes screenshot in 30 frames/sec only.
* You can use also the [[Lua/Game#peacefulmode]], to be not disturbed by the natives.
* You can use also the [[Lua/Game#peacefulmode]], to be not disturbed by the natives.
* You can stop the game in the right moment using SHIFT-SPACE key. That also blends the grid in.
* You can stop the game in the right moment using SHIFT-SPACE key. That also blends the grid in.
* Learn how to use the [[Debug mode]] to add relevant information into this picture.
* Learn how to use the [[Debug mode]] to add relevant information into the picture.
* Go into the highest zoom level you possibly can, without missing any vital information.
* Go into the highest zoom level you possibly can without missing any vital information.
* A good in-game picture should be rebuilt, so that only the relevant entities/items are shown. Every repetition, every unneeded element will complicate it.
* A good in-game picture should be rebuilt so that only the relevant entities/items are shown. Every repetition, every unneeded element will complicate it.


Dont's
Dont's


* Don't make pictures of ultra-complicated stuff! Add only as much elements, which are needed to understand, how that might work. Exception: if you show how that could ''look'' in the end.
* Don't take pictures of clutter! Add only as many elements as which are needed to understand the picture; remove anything else. Any more than is necessary is distracting. Exception: If you show how the setup could ''look'' in the end.
* Don't just take a screenshot. Try to remove all unneeded informations from the picture.
* Don't just take a screenshot. Try to remove all unneeded information from the picture.
* Try to make a picture without the character, except if to show something; then face the character to it.
* Try to make a picture without the character, except if to show something; then face the character to it.


Line 215: Line 214:


* Cut as much as possible/nice.
* Cut as much as possible/nice.
* Resolution should not normally be higher than 600x600 px. If that seems too small, then you should rethink what you want to do.
* Resolution should not normally be higher than 600x600 px. If that seems too small, then you should rework the photo to fit 600x600 px.
* ''Do not add textual information into the pictures! ''Instead add numbers or letters in it and add the text on the wiki-page; otherwise, it isn't searchable information,if it is written into the pic.
* ''Do not add text to the photos''Write any needed text outside the photo on the wiki. You cannot search text that is in a photo, and users might not find what they are looking for.
* Sharpen the pictures. For the wiki it looks quite better to sharpen the pictures one or two times.
* Sharpen the pictures. For the wiki it looks a lot better to sharpen the pictures one or two times.


=== Making animations ===
=== Making animations ===


This has to be tested a bit:
This hasn't been tested fully yet:


: [http://blog.bahraniapps.com/?page_id=21 Gifcam] (PC only)
: [http://blog.bahraniapps.com/?page_id=21 Gifcam] (PC only)

Revision as of 15:33, 20 December 2014

This page is used for contributors on this wiki.

Get an account

Just follow the instructions for registering. It takes normally one or two days to be added, because every user is added by hand to avoid spam.

If you need more rights to the wiki (deletion, moving...) you need to ask the devs directly, or ask in the forum board.

Understanding the wiki

There is currently a forum article which should give you a good introduction to how the wiki works: http://www.factorioforums.com/forum/viewtopic.php?f=50&t=5994&p=46947#p46749

Contributing to the wiki

This wiki is the work of a team. The goal is for people to add information or bring it into better context, do videos, or design the layout of the pages.

The team communicates through the talk-pages ("Discussion" folder at the top) or through the forum ( http://www.factorioforums.com/forum/viewforum.php?f=50 ). It'ss very important to look at the "Recent changes", so that you see if someone modified a page (especially a talk:-page), in which you are interested.

(BTW: You can change the shown results in the preferences!)

There are different jobs you can do. This list is from simple to complex.

Corrector

Read through the pages (of your language) and correct mistakes or bad language use. If it sounds ugly then change it. If you're new to wiki's it might be difficult at first, but keep at it and you'll learn to do more. :)

Translator

Take an English page, copy the content into a subpage (see below for an explanation) and translate.

Writer and Linker

If you find good information in the forums, it's a good idea to add that information to the wiki. No special knowledge is needed, just search the right page, the right chapter, or add a new page and make it. If it isn't okay the next user will take care of it. :) Sometimes you don't have time for writing it all out. That's okay, just follow the steps below. Someone else might see it and add the relevant information.

  • Step 1: Simply copy the link and put it into the right page under "See also". This is to document the link for later usage.
  • Step 2: The next person who sees it and has time will take the information from the linked page and will add it to the wiki.
  • Step 3: If the sub information is too big or too long, then move it to a subpage. (There are some examples in the wiki on how to use subpages, in general it's just adding a "/subpage name" to the existing page.)

News-maker

There is the News-page. Just add new links as new interesting information comes out. The rest is explained in the page as comments.

Ask yourself: Is this news or not? See it from historical point of view: When you go back to older news, will it still relevant?

Designer

This is about the look and feel of this wiki. It is quite interesting what can be done with such relatively simple nesting. But it is also quite confusing. :)

Deep knowledge of Mediawiki's template system is not really needed, but will help. For the beginning just try to understand how the current templates work. Make your own test-page in your user-space and try to program around. It can make really fun because this task is more or less like programming.

Look here for some help: http://www.mediawiki.org/wiki/Help:Contents And for some extra help: http://www.factorioforums.com/forum/viewtopic.php?f=50&t=5994&p=46947#p46749

Tutor for beginners

This is about writing tutorials. Helping beginners understand the game and explain how to do things in-game. This is currently a problem since the game changes. The plan is to be about ready in summer 2015. So if you write a tutorial now it will be outdated in a few months. But don't let this discourage you. If an update makes your tutorial obsolete, just update the tutorial to fit the most recent update.

Pictures and videos are encouraged since they make understanding a tutorial a lot easier.

Architect

The wiki is created in an agile process: writing, reading, testing. :) If you find out that this process is somehow inefficient, for example the changes are in the wrong place, then you need to change the wiki in general.

This is for example currently the case for the whole "networks". They are no longer a good idea. The logistic network and robotic network are in truth a "robotic system", which contains a construction- and a logistic-area. And the logistic area can be extended over the logistic network.

So the job of an architect is to bring the existing pages into the right context by adding some new pages and/or renaming existing pages, and then changing the links to the pages. And sometimes old stuff must be deleted.

Dowhateveryouwant

These "roles" are not fixed! There is no rule saying, that a translator cannot write poems about the deep insights he has gained by playing Factorio. And there will eventually also be an audience which will like that. (I mean that seriously.)

So, if you have an idea:

  • Don't be afraid: There is nothing which you can really break, the wiki has a version history.
  • If you are still afraid: You can use the a test page in your home-space. That's the page beginning with "User:<your user name>". You can add a subpage like "User:<your user name>/MyTests". Ask others what they think about it. Communicate!
  • Begin with slight changes. The others will watch (the "Recent changes") and help you out. If after a week or two is no response/follow up change, your change was good. Keep going, make bigger changes.

Basic

  • Read the wiki pages.
    • If you don't like something, change it.
    • If you find typos, change it.
    • If you find something is wrong described, make a proof that it is wrong and change it.

Advanced

  • Add missing information in the right places.
This is in most cases easy, but sometimes could be really difficult. Ask for help if you're unsure.
  • Split the information on big pages into subpages.
See for example the Railway network.
  • If you find that a topic belongs to two pages, then don't copy the information into the two pages, but create a new page and link them.
Best example for this is the Power Production page.
  • Use the right words.
Factorio has a set of words which have a fixed meaning. For example: an entity can be mined, an item can be picked up. Removing them means something different! Ask the users if you are unsure which is which.
  • A picture says more than a thousand words.
Use pictures if possible. In some case use GIFs! See below.

Discussions

I (ssilk) prefer the forum for discussions and I hope this is not a problem, because I think, discussions on wiki-pages is to high-end for most potential wiki-writers.

Existing discussions

In descending order of date:

http://www.factorioforums.com/forum/viewtopic.php?f=5&t=2047

http://www.factorioforums.com/forum/viewtopic.php?f=5&t=3205

http://www.factorioforums.com/forum/viewtopic.php?f=5&t=2429

http://www.factorioforums.com/forum/viewtopic.php?f=5&t=2255

Translations

For translating the game the dev-team uses https://crowdin.com/project/factorio

This is about translating the wiki.

This is currently a mess!

This is how it should work

This method is used by the Mediawiki-Team and we want to adapt it. Examples:

http://www.mediawiki.org/wiki/Help:Navigation The English default

http://www.mediawiki.org/wiki/Help:Navigation/es Spanish translation

http://www.mediawiki.org/wiki/Help:Navigation/de German translation

http://www.mediawiki.org/wiki/Help:Navigation/ru Russian translation


First some rules

  • The default language is English.
  • Any other language has no right to obtain a pagename, which collides with English.
  • No other language has the right to use a pagename which means the same or something different in another language.

This is the logical consequence of the above rules

  • Let's say we have a page named Transport network.
  • Now someone translates that page to German: Because he doesn't know better, he names the page "Transport netzwerk".
  • This is a mess! Because for example in Swedish (it's just an example) this is also the translated pagename.
  • What's now right? Is Transport netzwerk now a German or a Swedish page?

Solution to this

The right pagename is Transport network/de for the German and Transport network/sv for the Swedish page.

Whuuaaaa... "Transport network" - that's not German!

Yes, but it is the only way to keep the namespace clean.

And there is nothing wrong about making a redirect page Transport netzwerk which redirects to Transport network/de. Or make a page where the user can choose if he wants the German or Swedish page.

So what do I need to do now?

"Inserters" becomes "Inserters/fr" for France, "Inserters/ru" for Russian etc.
  • If you are working on a page, which has a translated pagename then rename (Move) it! Search the original pagename, add the language-code (see above), and move it to the new pagename. A redirect is automatically left for the old pagename!

(More to explain, language macro, see main-page at top right)

Pictures

Picture formats

For making things simple we should use only formats based on 100. This is to avoid different sized pics which look staggered. This is especially important for the width, for the height it is not that problem. For example: 200x200, 300x100, 400x232. For existing pics (old pics use often a width of 256 px) reduce the text to 200 px (and analogous).

  • (100 - 200) x (100-300) px
For flowing with the text, pictures which explain the text, the browser can embed this into it's own rendering. You can put them left or right, the text should flow around.
  • (400 - 600) x (100 - 600) px
Something like a banner. A big picture which stays alone in its line. You may put simply a ":" in front of it to indent the picture and keep it away from flowing text.
  • 300 x 300 px
This is especially for gif animations. Gif animations cannot be reduced in size, because mediawiki re-renders the picture and the result is the first frame of the gif! See for example these pics: http://www.factorioforums.com/wiki/index.php?limit=200&ilsearch=Mpstark&user=&title=Special%3AListFiles
  • The biggest format for flowing text should be: 600x600px

Making pictures out of the game

Do's:

  • Take pictures at day! Turn on daylight! Use night or dawn only if you need to explain something that only works at night.
  • Turn off clouds! The shadows in GIF-animations are not useful.
  • Steam/smoke is also not so useful.
  • Use god mode! Lua/Player#controllertype. You can go to every place and won't stand in the way of the picture.
  • You can slowdown the game to find the right moment for the picture. Slowdown is also useful, if you use Gifcam, which makes screenshot in 30 frames/sec only.
  • You can use also the Lua/Game#peacefulmode, to be not disturbed by the natives.
  • You can stop the game in the right moment using SHIFT-SPACE key. That also blends the grid in.
  • Learn how to use the Debug mode to add relevant information into the picture.
  • Go into the highest zoom level you possibly can without missing any vital information.
  • A good in-game picture should be rebuilt so that only the relevant entities/items are shown. Every repetition, every unneeded element will complicate it.

Dont's

  • Don't take pictures of clutter! Add only as many elements as which are needed to understand the picture; remove anything else. Any more than is necessary is distracting. Exception: If you show how the setup could look in the end.
  • Don't just take a screenshot. Try to remove all unneeded information from the picture.
  • Try to make a picture without the character, except if to show something; then face the character to it.

See http://www.factorioforums.com/forum/viewtopic.php?f=6&t=2472 for more.

Taking screenshoots, animations and videos

Taking screenshoots

Optimizing the picture before upload

  • Cut as much as possible/nice.
  • Resolution should not normally be higher than 600x600 px. If that seems too small, then you should rework the photo to fit 600x600 px.
  • Do not add text to the photosWrite any needed text outside the photo on the wiki. You cannot search text that is in a photo, and users might not find what they are looking for.
  • Sharpen the pictures. For the wiki it looks a lot better to sharpen the pictures one or two times.

Making animations

This hasn't been tested fully yet:

Gifcam (PC only)
Licecap (also for Mac)
Good example pictures: http://www.factorioforums.com/forum/viewtopic.php?f=5&t=3920

Making videos/streaming

Youtubin' & Streamin'

In-game API for screenshots

http://www.factorioforums.com/forum/viewtopic.php?f=25&t=4109#p30605

Looks like a plan: create a world. Walk through the world. Start a replay of this walk and then add making screenshots.

More or less like the method used in the demo-video, but take only some gif-animations or single pictures.