Message translations
From VbGORE Visual Basic Online RPG Engine
Contents |
What "Messages"?
The Messages in vbGORE refers to the messages that the client displays. These messages are for the most part constant, sometimes with one or multiple variables in them in defined locations.
For example, the message:
Bandit appears to be no longer weakened.
Would be written in the message file as:
<npcname> appears to be no longer weakened.
When the server wants to send the text to a client, instead of sending the whole text as displayed in the first example, a number is set along with any required variables. In our example, the number 1 will be sent, followed by a string (being the NPC's name, "Bandit").
To edit the messages (or translate it), you need to work with the <yourlanguage>.ini that is located in data/messages folder. It's important to remind that if you want to translate to a language, just copy the original file, rename it, open, edit and save it.
How to edit
The message files have some very important rules to follow.
- [MAIN] tag
- This tag must remain at the very top as-is. Do not translate.
- NumMessages tag
- This tag tells how many messages there is. This won't ever need to be changed when doing translations. This value should reflect the highest number value in the file to the left of the = sign. Do not translate.
- In-text tags
- There are multiple in-text tags, such as <exp>, <name>, and <amount>. These can be moved to any part of the text needed, but the tag themselves must never change, so do not translate these! They are designed to be moved to appropriately fit the translation.
The following rules will not break or change the way the translation functions, but are still important:
- Grammar / Punctuation
- Use as proper grammar and punctuation as possible. These translations are designed to be good translations, not the quality an automatic translator gives you.
- Number order
- Please leave the number order in ascending order for organizational purposes.
The following are little tips and facts about the system that would be helpful to know:
- Comments
- Comments are signified by the -- in front of them. This is here just for reading purposes, though. Please leave them in tact. Comments do not have to be translated, and it is recommended you do not translate them unless you want to.
- Getting stuck
- If you get stuck on a translation, just skip it and make clear note that you did not translate it. Unfinished translations should have a (Unfinished) tag in their header (ex: English (Unfinished) ) to show that they are unfinished. At the very start, before the <pre> tag, write what is left to be translated.
- Formatting the code
- Please use the <pre> and </pre> on this page at the very start and very end of the language translation. This will put a box around the code. For an example, just refer to the currently existing translations.
Translations
English
See Message translations English.
Spanish
See Message translations Spanish.
Portuguese (Brazillian)
See Message translations Portuguese, NPC chat, Sign translations
German
See Message translations German, NPC chat, Sign translations
Dutch
See Message translations Dutch.
Swedish (Incomplete)
See Message translations Swedish.
Italian
See Message translations Italian, NPC chat, Sign translations
Polish
See Message translations Polish, NPC chat, Sign translations