Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Complete list of current guidelines, and writing conventions. #857

Open
Ragunaga opened this issue Aug 12, 2015 · 1 comment
Open

Complete list of current guidelines, and writing conventions. #857

Ragunaga opened this issue Aug 12, 2015 · 1 comment

Comments

@Ragunaga
Copy link
Contributor

I've collected a complete list of guidelines, and writing conventions that should be used to make everything come together nicer.

I hope this helps those who are confused about various edits they should make.


Guidelines and writing consistencies.

  1. Please use the latest files when you edit.
  2. Edit/review lines in groups.
    Limit your range to chunks of 50, 100(max) lines.
  3. Please send separate pull requests for each file.
  4. Indicate lines you are working on, so others will not be looking into the same lines at the same time.
    Make sure to check others before starting, and to close your issue when you finish.
  5. Indicate the lines you reviewed in the pull request title.
  6. Always write a summary.
    Write down the section you reviewed in the commit summary.
    Explain the type of edit performed.
    Definitely explain your edit if you're doing a mass search and replace.
  7. Any new important Keywords, or changes to Keywords, must be immediately reported and explained for addition to the translation glossary.
  8. Add an "x" Mark in front of line code For Edited / Reviewed so others would not repeat the same lines.
  9. Keep translations literal, names/locations included.
  10. Additional questions can be asked by opening an issue, or in the ToS Korean to English discord channel that can be found here; https://discord.gg/0RoYSiES4f4zwAk8
    We suggest that you browse or search the Issues when you encounter any problem.
    When in doubt, always ask a question.

Writing and Grammatical Consistencies/Standardizations

SKILLS

  1. "per attribute level" when refering to skill's descriptions.
  2. "Holy Attribute," "Fire Attribute," etc.
  3. Use uppercase letters when refering to skills.

QUESTS/DIALOGUE

  1. [Class] Master is a title, and should be pre-empted by "the." eg. The Bokor Master.
  2. Lines for the player should include punctuation, if they are actual dialogue. eg. "I accept the fight." Actions should not. eg. "Accept the duel"
  3. Area/Item/NPC names should be a direct translation, or a romanization if it is Lithuanian in origin.
  4. Unless it a common noun, and not directly named, use "to [Area]"; not "to the [Area]." eg. "Go to Fallen Worry Forest." "Go to the store."

NAMES

  1. Keep naming consistent, and do not change names unless deemed important/needed.
    If you do change a name make sure to consult another contributor and to make it clear that you have changed something,
    so the wiki and other files can be updated.
  2. As said in QUESTS/DIALOGUE names are a literal transation, unless Lithuanian.
  3. Titles should be Capitalized. AKA. Bokor Master
  4. When the name is a title, pre-empt it with the. eg. "Go to the Bokor Master." "Go see Jeff."

I should probably add this,
Please remember this is a TRANSLATION first, and not a LOCALIZATION.
We're translating files and text, not adding space, flavour, or odd names/language problems.

.

If you wish to have it in a .txt file for whatever reason, here you go;
https://www.dropbox.com/s/qnv37xs89re0v9q/Guidelines%20and%20Writing%20Consistencies.txt?dl=0


If you see anything that's missing, or needs to be changed please tell me!

@samuelhnrq
Copy link

Is there are a rule or number of max characters per line before {nl} or does the game have auto line wrapper and the {nl} just forces it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants