Help:Subwikis

This article aims to guide (prospective) translators along the process of opening a new Dead by Daylight subwiki.

What is a Subwiki?

A subwiki is essentially a translation of the Dead by Daylight Wiki into another language. Our existing subwikis can be accessed through the main page of this wiki.

If you do not find your native language there, you can contribute to the wiki by creating a subwiki for it! How exactly to do so will be explained further in this article.

Requirements for Translators

• Excellent knowledge of both English and the target language (CEFR C1+, preferably C2).
• Decent knowledge of the syntax used on the wiki.
  • Coding experience is helpful but not required (Modules).
• Plenty of spare time (the translation process takes longer than one might anticipate).
• Owning a copy of Dead by Daylight is recommended but not required.
• Good teamwork and communication skills.

Getting Started

Technical Fundamentals

If you are new to the wiki, please read this help article to learn about the ins and outs of the platform.

First of all, you should find out what the language suffix for your language is, you are going to be using it a lot. Please refer to this table. If you do not find your language in it, please let us know and we will add it.

Before starting off with the editing, you should make sure you understand the syntax used in the Datatable modules. A bulk of the information displayed on the wiki is stored there. In a nutshell:

• Non-code text fragments in programming are called strings. Strings are typed out in "" or '' (e. g. "Dead by Daylight").
• A "block" is contained within {}. Opening curly brackets should always be closed at the end of the block.
• Parentheses are mostly used to enclose the parameters of a function. Functions generally use the format name(param1, param2, ...) and implement some functionality; b("bold"), for instance, prints out bold. For detailed explanations on functions, please refer to this documentation.
• Variables are stored values that can be accessed from multiple locations. Modules mainly deal with Global string variables. We store elements such as punctuation marks and line breaks as variables. General string variables can be accessed by simply writing out their names (without ""). Examples include:
  • dot - .
  • space -
  • nl - New line (the following text gets printed out in the next line)
  • dnl - Double new line
  • nlp - New line paragraph
  • comma - ,
• Other variables stored as arrays need to be accessed using the format arrName.varName, for instance ils.chest for the IconLink String (The string itself will not return the icon with its respective formatting, but instead a correct string which can be used as a parameter for the IconLink function.) for Chests.

• In order to print out a complete line using modules, we often need to combine normal text (Strings) with function outputs and variables. Multiple fragments can be joined together using .., a process referred to as String concatenation in technical terms.

Example:

"This " .. func(" is ") .. " a " .. strings.concatenatedString (We assume that there is a table strings with the value concatenatedString.) .. dot

First Steps

• Your first actual editing steps should be to copy over all data and functional Modules (see Modules) into articles named the following way: Module:name/lang_code, switch out lang_code for the language suffix of your language. Do not edit the contents of the modules just yet.

• After you are done, create the respective documentations for all the module articles you have created (Module:name/lang_code/doc). Please add [[Category: lang_name translation]] to all documentations you create; lang_name is the name of your language in this table. The category should be the very last line of source code of the documentation.

• Now you are all set to get translating. Start with Module:Datatable/Loadout/Descriptions/lang_code.
  • WARNING: Please keep in mind to only edit the module containing your language code and not the English version. Tampering with the English modules improperly is considered heavy vandalism and we reserve the right to take immediate action as per our rules.

• In order to check the progress achieved and verify if the syntax is correct, use {{#Invoke:Loadout/lang_code|getPerkDescription|perkname}}, for instance, on your user page, and check if the perk description is printed out correctly. Do not create new pages just yet. In case you encounter errors you cannot trace, please contact us. Other test functions include getItemDescription, getAddonDescription, getOfferingDescription.

• If everything works out, please contact one of our English Wiki Guardians and we will greenlight the creation of a "main page" for your language. What this entails is essentially copying over the main page of the English wiki into a separate article marked with your language code. Make sure to translate your main page fully. Note that dead links should not yet be taken care of.

• Once you are done, continue on with the other data modules (see Modules).

And then?

The Bulk of the Translation

• Once all data modules are fully translated, the creation of regular articles for the translation will be greenlit upon request after a quick check by one of our Wiki Guardians.

Please remember to add the [[Category: lang_name translation]] category to any new pages you create (Redirect and documentation pages are included as well.) . Reminder: lang_name is the name of your language as per this table.

At this point, the following articles linked to from the main page are required to be fully translated in order for a new Subwiki to be able to be created:

• Every article of the Unlockables section
• Every article of the Game section (Note: individual Patch notes do not have to be translated.)
• Every article of the Currencies section
• Every article of the Unlockables section
• Every article of the Character Progression & HUD Overlay section
• Every article of the Stores section
• Every article of the Interactables section
• Killers
• Survivors
• Unlockables
• Realms
• Downloadable Content
  • Note that the pages listed above may contain dead links (Links with no page created.) .

The following articles are optional and may be translated freely if desired. Note that they will not be included in the final assessment:

• Individual Survivor articles
• Individual Killer articles
• Individual Map articles
• Individual Realm articles
• Individual Perk, Add-on, Offering, and Item articles
• Individual DLC articles
• Individual patch notes on Patches.
• The Current Event(s) and Past Events sections of the main page.
• Redirects

Subwiki Assessment

Once all of the above requirements are met, translators may request the Wiki Guardians to evaluate the potential for the creation of a brand-new Subwiki, which will be done through a simple vote.

PASS:

• Individual steps will follow.
• In any case you will be asked to put forth suggestions for potential Wiki Guardians of the new Subwiki, considering that it needs to be moderated and maintained. A vote on the suitability of the candidate will then be held. Keep in mind that this vote requires unanimous consent to pass.
  • In case multiple candidates are up for the position, the Wiki Guardians will hold two votes; one deciding which candidate is more suitable, and one approval vote for that respective candidate.
• All involved parties will get briefed about the results of the voting process by our Mentor to Junior Wiki Guardians.
  • PASS: The Subwiki is created and the candidate in question becomes a Wiki Guardian for that Subwiki.
  • FAIL: The translators will be asked to make a new suggestion. If no suitable candidate is found, the Subwiki creation process will be put on hold.

FAIL:

• Translators will receive a message comprised of the result of the vote and a detailed list of concerns and requirements.
• Once those are addressed, a new vote will take place.

NOTE: The Wiki Guardians reserve the right to put translation processes on hold or cancel them outright should they go inactive or have no prospect of being completed within a reasonable timeframe.

Our Tips

• Ask for help if you need it! We understand it might be a little overwhelming at times, so we are happy to assist you. Many of us were translators like yourself.
• Listen to Wiki Guardians' advice and requests.
• Do not jump the gun: it is really helpful to get acquainted with the ins and outs of the wiki and its syntax before starting off with the translation.
• Stay active: try translating regularly. Going inactive for long periods could lead to the eventual cancellation of the translation.
• Plan out your translation: since the workload is high, it is a good idea to allocate a little time regularly to translating instead of trying to do it all in one go.
• Translate schematically and in a structured way so you can keep track of your progress.
• Get some backup: splitting up the work if possible is imperative in completing the translation swiftly.
• Be nice and respectful to everyone: getting on people's good side can never hurt.

Contact

• Jouki - Everything surrounding modules and automation, technical questions and support.

• Fichte - Questions about Subwiki creation, the translation process, and Wiki Guardian applications.

• Doc - General questions about the Dead by Daylight Wiki.