From Touhou Patch Center
Jump to: navigation, search

Recent changes

22 November 2022

    22:23Th175/Yuuma's Scenario/en ‎(8 changes; hist; +31) ‎    ‎[Sqrt‎×8]

13 November 2022

    20:08Th175/Yuuma's Scenario/en ‎(129 changes; hist; +317) ‎    ‎[Sqrt‎×129]
    11:54Th175/Images/en ‎(4 changes; hist; +117) ‎    ‎[StoneHalation‎×4]

12 November 2022

    11:21Th175/Images/en ‎(11 changes; hist; +2,338) ‎    ‎[StoneHalation‎×11]

10 November 2022

     23:02Th175/Yuuma's Scenario/en ‎(diff; hist; +2) ‎    ‎SqrtShow user links ‎ ‎

7 November 2022

    21:07Th175/Yuuma's Scenario/en ‎(331 changes; hist; +9,591) ‎    ‎[Applesaucers‎×21; Sqrt‎×310]

6 November 2022

    17:04Th175/Yuuma's Scenario/en ‎(16 changes; hist; +374) ‎    ‎[Sqrt‎×16]

A note about copy-pasting

Language statistics

Check how far the language progress is.

Licenses of existing English translations and patches

In a fandom like Touhou, this really shouldn't be an issue. However, some groups just want to keep their translations to themselves for whatever reason, and others may accuse us of stealing content. So, here's a brief overview of the licensing conditions of all well-known sources of translated Touhou game content:

Touhou Wiki touhouwiki.png

All text content from there is licensed under CC-BY-SA touhouwiki.png and can therefore freely used anywhere else, provided the original source is attributed. If you want to go the extra mile, use the template {{Copy-paste text}} and specify the exact page version and all the original authors.

PC-98 games

Patch project led by xJeePx. OK to reuse any content with attribution, equivalent to CC-BY-NC.

Icon th06.png Embodiment of Scarlet Devil, Icon th07.png Perfect Cherry Blossom

Patch projects led by Simon Elén (S") (th06, th07). No license given, but the image translations were originally uploaded to Touhou Wiki and are therefore implicitly licensed under CC-BY-SA as well. As the current Touhou Wiki administration is overzealous about deleting "obsolete content", and because they messed up the image credits when moving to their own server, Wikia is the better source in this case.

Icon th08.png Imperishable Night

Patch project led by Non-Directional Translations (NDT). Similar situation as with the Icon th07.png Perfect Cherry Blossom patch, but only a few image translations were ever uploaded to Touhou Wiki. Considering that the original authors are long gone, it seems OK to use the rest of the content as well.


Halbarad explicitly denied us the right to reuse the images from their patches, citing "possible legal issues with fan translation". This applies to the following games:

Icon th09.png Phantasmagoria of Flower View

Patch project led by Rufus. No license given, and Rufus is nowhere to be found. So... just go ahead?

Icon th095.png Shoot the Bullet, Icon th125.png Double Spoiler

Patch projects led by drywall. (th095, th125). A source code distribution is available for both patches (th095, th125). Each of those contains (at least) two licenses: the GPL v2 and GPL v3 for th095, and the GPL v3 and BSD 2-clause license for th125. This creates a rather unclear situation:

  • It is never clearly explained which license applies to which data.
  • Each one of the Python source code files, however, do reproduce one of the licenses at the beginning of the file.

This suggests that these licenses were merely copy-pasted straight from xarnonymous' and S"'s code used in these patches, and are not meant to apply to the translated data. However, since any of the licenses given grants us the right to reuse the translations anyway, it seems fine to do so.

Language variety policy

The translations in the base en language code are to be fully in American English (hence that the American flag is used to represent the English language here). For new translations in en, please try to follow American spelling and vocabulary where possible, but don't think too much about it - spelling discrepancies can always be corrected later.

This is to ensure consistency among the translations and the MediaWiki software, which actually does not define a separate en-us translation in its code.

In case you clearly want to create translations which use spelling or vocabulary from a different variety of English, please use a separate language code for your edits where you put only the differences between American English and your variety. These can then be combined by the end users using the patch stacking feature to form one fully localized translation.