Clannad:Guidelines
If you wish to make a translation contribution and cannot abide by the Guidelines for any reason, post the text in <pre> tags, and mark the top of the page with {{Clannad:Cleanup}}. A Project Editor will handle the transfer into an acceptable format.
Pages will be marked at the top, either by:
- {{Clannad:Translating}}, to indicate translation is underway. Pages are categorized under Category:ClannadTranslating.
- {{Clannad:Cleanup}}, to indicate cleanup is necessary. Pages are categorized under Category:ClannadCleanup.
- {{Clannad:Recode}}, to indicate that the page needs or has undergone Kepago cleanup. Pages are categorized under Category:ClannadRecode.
- {{Clannad:Alternate}}, to indicate that an alternative translation is available.
As part of the Clannad Translation project, the following guidelines here must be adhered to, if you are an Editor or Translator. Its parent page stems from the Suzumiya Haruhi Project Guidelines, but has the following amendments:
Translators
- Any number of translators can translate the same file at any given time. However, if the link already has a translation, translators are advised to make changes to the current file and post in the Talk page for the respective SEEN file.
- Anonymous translation contributers are required to inform a Project Editor, Translator, or Administrator before any major contribution.
- If you translate a line and believe the line requires a checkover, please add a "*" beside the line. Someone more experienced may then look it over for you.
- If you cannot translate a line at all, and can only guess what the line is, DO NOT TRANSLATE THE LINE. Instead, leave a comment with your name indicating what you think the line should be translating to. Making a guess makes it very difficult for translators to revise the text, that and if you knew it was going to be a guess, you should have put a "*" at the end of the translation in the first place.
- Only Japanese -> English translation is allowed in the Clannad Translation Project.
Editors
- Anonymous editing is not allowed for finalized pages. If you wish to make a contribution, please make a comment in the discussion page for a SEEN file for review by the Project Translation Team.
Tenses
For the most part, when Tomoya speaks in narration, he will be speaking in present tense, unless the context applies to him talking about the past. The Illusionary World will also involve present tense where necessary.
SEEN Page Format
All SEEN pages on the wiki are to follow this format:
{{Clannad:Translating}}
Return to the main page [[Clannad|here]].
== Translation ==
*[[User:yournamehere|yournamehere]]
== Text ==
<div class="clannadbox">
<pre>
insert your content here
</pre>
</div>
== Script Chart ==
{{Clannad:ScriptChart}}
The content to be inserted is of the format below.
Dialogue/Narration Syntax
- The default format for the final kepago text files is:
// Resources for <FILE>
#character <name in english>
// name in Japanese
#character <name2 in english>
// name2 in Japanese
<0001> some narration
// narration in Japanese
<0002> \{Man} "oh hey i said something"
// \{男}「おお、俺が言っていた」 {-yeah, that's what he says-}
<0003> \{Man} (and then some)
// \{男}（etc. etc.）
Please make use of the "//" for comments where needed. Spacing between \{Man} and "quote" does not appear to matter.
- Dialogue will always be enclosed in quotation marks "".
- Comments to oneself or whispering to others will be done in parenthesis brackets ().
- Ellipses "..." can only happen in groups of three. So if there are six of them, it should be "......"
- Immediately after a set of ellipses, any words following shouldn't be capitalized, and there should be a space between (e.g., "... what?").
- As the game is happening in realtime, present tense should be used unless past events are being discussed. So when Tomoya is in class and the class has ended, Tomoya should speak about how the class has ended in the present tense. However, if he talks about how he got injured by his father from long ago, that should be spoken in past tense.
- Event tags such as "\size{}", "\p", "\r", etc. should be preserved at all times. If different positioning is required for creative/technical reasons, don't hesitate to make such changes.
- Unless the Japanese text has used it, "\r" and "\n" cannot be used at all. We already have automatic line breaking in place, so there's no need to do line breaking on your part, unless the script calls for it (for example, two people speak at the same time).
- If "Tomoya" appears anywhere in the text, it must be replaced with "\m{B}". If "Okazaki" appears anywhere, it must be replaced with "\m{A}". The reason is that the game stores the name in an A,B format for Okazaki,Tomoya. \m{} calls the name. For consistency reasons, this must be followed.
Character Set
When RLdev compiles for dynamic lineation, it requires that all resource strings follow a specific format; that is, any string following <xxxx> must follow CP1252 in order to allow the Western encoding mode to run perfectly with rlBabel.
After some further research, the character map listed for Windows-1252 reveals that the following characters are not supported under the RLdev system when compiling for dynamic lineation:
| Unicode | Replacement |
|---|---|
| … | ... |
| ～ | ~ |
| ㎝ | cm |
| ♪ | |
| ♂ | |
| ♀ |
If any of the items listed above are blank, it means that currently an image is being looked into, in order to allow the character to appear. Please be patient until a character has been made. If a character already exists as a replacement, please use it.
Characters that must be substituted will use the \em{} command (not \e{}). More details on how this command works is available at Haeleth's development site.
Event Codes
- For people with voice patches... if the script calls for certain event tags such as pauses to be replaced by \wait{} due to some issues from transferring the PS2 script to PC, please make those changes and comment them in as necessary.
- Emphasis codes (\b and \u) are allowed; this means that text such as "R2D2! It \bis\u you!" will end up looking like "R2D2! It is you!". NOT to be confused with bold or underlined. Refer to this page for more details.
- When you use \b the italiced text is canceled out when it detects \p, so if the line is like this "\bSentence 1...\p Sentence 2\u" sentence 1 will be italiced but sentence 2 will not be... to fix this, you should use "\bSentence 1...\u\p \bSentence 2\u"
- Hyperlinking is allowed. The plan is that these hyperlinks will act as the "TL Notes" window in the game. Please see this section for more details on the \g{} command.
Naming Conventions
The following namelist is suggested for all naming (additions can be made at any given time):
| Last Names | First Names | Important | ||
|---|---|---|---|---|
|
|
|
||
| Other | ||||
|
|
|||
Special Case: Baseball Scenario
For the baseball scenario and the sake of standardization, all terminology should come from:
Special Case: Fuuko's Third Person
Fuuko speaks in third person, and in fact this notion is taken into consideration from SEEN1418:
<0211> \{Female Student} "This is what Fuuko wants to do."
// \{女生徒} 「風子がそうしたいんです」
<0212> \{Female Student} "So please leave Fuuko alone."
// \{女生徒} 「放っておいてください」
<0213> \{\m{B}} "That Fuuko you're talking about, is that your name?"
// \{\m{B}} 「風子っていうの、おまえ？」
<0214> \{Fuuko} "Yes... Ibuki Fuuko."
// \{風子} 「はい…伊吹風子です」
