EarthMC:Entry Naming

From EarthMC
Revision as of 06:59, 13 January 2023 by 181cm (talk | contribs) (Created page with "This guide is used to name the normative entries (namespace=0/Classic:/Nova:/Aurora:, excluding disambiguation pages and redirection pages). The naming of disambiguation pages and categories can refer to this guide appropriately. The entry name is the '''actual title of the entry'''. You can create a link through two opposite brackets (<code>entry name</code>). The URL also contains the entry name (which may be escaped). It is '''not necessarily''' t...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

This guide is used to name the normative entries (namespace=0/Classic:/Nova:/Aurora:, excluding disambiguation pages and redirection pages). The naming of disambiguation pages and categories can refer to this guide appropriately.

The entry name is the actual title of the entry. You can create a link through two opposite brackets ([[entry name]]). The URL also contains the entry name (which may be escaped). It is not necessarily the display title. The display title can be changed with Template:Title replacement. (The function has not been implemented yet)

Entry names are case-sensitive, but the first letter is always uppercase. The space in the entry name is equivalent to the underscore, and is displayed as a space on the page title.

To determine an entry name, you need to go through #Naming Principle and #The Processing of Symbol and Infrequent Characters:

  1. A reasonable entry name should meet at least one of the #Naming Principle, and should meet as many principles as possible. If a certain entry name meets more principles than other entry names, it will be preferred.
  2. The name selected by the naming principle may contain various symbols and uncommon words, which can be used as the entry name after processing.

If it is impossible to choose a better item name in this way, the relevant editors should negotiate and discuss it.

Naming Principle

Server partition

Because Earthmc already has three different servers, Classic (the oldest server), Terra Nova (the old server) and Terra Aurora (the new server), among which there may be content with the same name, the entry name should be added with the namespace of the server to which the entry belongs (Classic:, Nova:, Aurora:).

If the entry has content that spans multiple servers, there are generally two processing methods:

  • If the content is similar and related to multiple different servers' things (for example, the Aurora country, which is the successor of a country in Nova, writes its own content in a chapter of Nova one's page). You should split the content into multiple different pages and add corresponding namespaces respectively.
  • If it is the same content in multiple servers (such as players or organizations), it can be written on the same page, but chapter planning should be done. In this case, the namespace may can not need be used.

Note appended:

See Help:Redirection for details.

If a thing only exists on a single server (such as "Ronne"), you can create a page for it without a namespace's entry name. However, you should also redirect this page to a page with a namespace.

If a thing exists on multiple servers (such as "Spain"), its entries that do not have a namespace but can be determined to belong to which server should also be redirected to the page with a namespace (such as "Spain(Nova)" needs to be redirected to "Nova:Spain"). Unable to determine which server the entry belongs to should use Disambiguation.

Common use name priority principle

The title should use the most common then relatively formal name as much as possible. For example, the country name was need tries to use the name of its name in the game, instead of "full name", alias or abbreviation.

English priority principle

In principle, the entry name of Earthmc Wiki can only be used in English. If it is a page that needs to create a corresponding page of another language, the entry name should be named 【entry name/corresponding language】(like Ronne and Ronne/简体中文)and use {{Title replacement}} to change the display title. The display title can be in the same language as the page language.(The function has not been implemented yet)

Redirection for other languages

Because Earthmc has a high proportion of non-English players, so it is allowed to have redirection pages is other languages of entry names.

However, please note that when creating a non-English redirection page for things in Earthmc Wiki, please make sure that your translation has been widely recognized by the majority of users of this language in Earthmc (for example, the Chinese translation redirection page "Aurora:龙尼" of "Aurora:Ronne").

Otherwise, in principle, it is not allowed to create such a redirect page (for example, it is not allowed to create a redirect page with the Japanese translation of "Aurora:竜廻" or "Aurora:ロニー" for "Aurora:Ronne". If you want to create a Japanese redirect page of "Aurora:Ronne", you should use the translation like "Aurora:リネン" which is recognized by most Japanese players in Earthmc)

If your page has multilingual support, you can directly redirect to the page in the corresponding language (for example, "Aurora:龙尼" to "Aurora:Ronne/简体中文" instead of "Aurora:Ronne").

Read moreHelp:Multi-language support for Entries(Help documents supported by multiple languages)

Principle of handling duplicate names

In general, as long as the entry name complies with the provisions of #Server partition and #Common use name priority principle, it will not be repeated under normal circumstances, but if this happens, in addition to creating the disambiguation page, the determination of the entry name is also very important.

Generally speaking, if an entry name can have a more specific description and avoid duplicate names, it is appropriate to change the entry name to a more specific description, such as "kasana2003" (instead of "kasana")

However, in some cases, it may be a better choice to use names with duplicate names, including:

  • The specific description was too long, For example, "Antarctica (Country)" (instead of "Antarctic Best Nice Holy People's Republic"), "Bangkok (Asia City)" (instead of "Krungthepmahanakornamornratanakosinmahintarayutthayamahadilokphopnoppa-ratrajathaniburiromudomrajaniwesmahasatharnamornphimarnavatarnsathitsakkattiyavisanukamprasit")
  • Ambiguous names are more commonly used and more well-known, such as "CSA" (instead of "America").

Please handle flexibly according to the actual situation of the object described by the entry, and do not deliberately choose a name that is not used universally in order to avoid ambiguity.

The Processing of Symbol and Infrequent Characters

"Symbol and Infrequent Characters" here refers to all characters except Han characters*, Aa-Zz and 0-9.

*The Han characters(Including Chinese characters(Hanzi), Kanji, Hiragana, Katakana and Korean characters) here are characters in Unicode with the character attribute of "Unified_Ideograph" and "〇" (U+3007 ideological number zero). They are basically located in the CJK Unified Ideographs and its Extension section. If you are not sure, you can view the character properties in Unicode Unicode Utilities: Character Properties and confirm the value of "Unified_Ideograph".

When the name contains The Processing of Symbol and Infrequent Characters, the name should be processed step by step according to the following rules.

Retention of characters

Symbols and uncommon characters that meet one of the following attributes can be retained without technical restrictions:

  • ASCII punctuation and symbols can be used: "(Space) ! " $ % & ' ( ) * + , - . / : ; = ? @ \ ^ _ ` ~"(The characters that can be entered directly on the American keyboard are generally of this type.);
  • “。 ? ! , 、 ; : ( ) [ ] 〔 〕 【 】 — … “ ” ‘ ’ 「 」 『 』 ~ · 《 》 〈 〉 / ×”;
  • Greek letters* used in the item name to express specific meanings in astronomy, mathematics and other real sciences, such as "Little Bear α and dreams" "β receptor blockers and stars";

*The increment symbol "∆"(U+2206 increment)), the quadrature symbol "∏"(U+220F n-ary product)), and the sum symbol "∑"(U+2211 n-ary summation) do not count as Greek letters.

Other characters should be avoided. In particular, due to technical limitations, a page with a title containing one of "# < > [ ] | { }" or some specific combination of characters cannot be created.

Processing of unreserved characters

Processing of unreserved characters can flexible handling, such as:

  • Replace with characters with similar meaning or function: Emma★Orgast → Emma Orgast, Fujiko Yoshio Ⓐ →Fujiko Yoshio A;
  • Written description: 88☆彡 → 88 meteor;
  • Latinization (romanization) and the use of 26 Latin letters without additional symbols: Ϡ → Sampi,Japari Café → Japari Cafe;
  • The symbol mainly used for decoration is deleted or replaced with a space: 千恋*万花 → 千恋万花; 777☆SISTERS → 777 SISTERS;

The above is only an example, and is not limited to the above methods. There can be other more appropriate methods for specific entry.

  • In cases where the name is garbled, blank, etc., which is difficult to handle, it may be a better choice to use another name, that is, to re-select a name that conforms to as many #Naming Principle as possible as the entry name.

If adjusting only part of the characters will cause a conflict, you can choose to adjust the other parts together.

Exceptions

It is inappropriate for some entry name not to retain some characters, mainly due to lack of recognition. If the characters in the name of the entry to be processed that should not be retained (that is, without considering the rules) meets all the following conditions, it can be retained:

  • There is no clear meaning in the language to which it belongs, or the meaning in the entry name has nothing to do with the original meaning;
  • It is not a decoration, nor a word that uses its shape to form other languages (such as “φ” on "Next New Wφrld");
  • After processing these text in an appropriate way (without deliberately avoiding ambiguity), the entry name will be ambiguous with other existing entries. But there is no ambiguity in retaining these text.

If some characters in the name can be reserved for an entry, these characters can also be reserved when the object described by the entry is mentioned in other entry names.