This HTML5 document contains 5 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

PrefixNamespace IRI
n7http://dbkwik.webdatacommons.org/ontology/
dctermshttp://purl.org/dc/terms/
n5http://dbkwik.webdatacommons.org/resource/qgLeCK5q5w24ZfTpSOL3Sw==
n2http://dbkwik.webdatacommons.org/resource/g5iVx9DqwrQSuO-QNbUhrQ==
rdfshttp://www.w3.org/2000/01/rdf-schema#
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
xsdhhttp://www.w3.org/2001/XMLSchema#
n6http://dbkwik.webdatacommons.org/resource/rPWM0Ah4VNgTcg8ghTOZJg==
Subject Item
n2:
rdfs:label
Yu-Gi-Oh!:Translation
rdfs:comment
Translation can be a very large problem for any project that has to deal with more than one language, and our own project is no exception. This page attempts to set forth exactly how editors are expected to approach translation, mainly between Japanese and English, but also for translating to other languages as needed.
dcterms:subject
n5: n6:
n7:abstract
Translation can be a very large problem for any project that has to deal with more than one language, and our own project is no exception. This page attempts to set forth exactly how editors are expected to approach translation, mainly between Japanese and English, but also for translating to other languages as needed. The type of information which tends to be most contentious when being translated is names: mostly card names, but any name can generate discussion and spark controversy over the "best" translation to use. As a result, most of the advice on this page is presented specifically with translating names in mind. It should be noted that, contrary to this page's name, its content does not exclusively prescribe translation. Rather, depending on the material and language(s) in question, the appropriate action could be any of translation, transliteration, or localization—and, most often, will be a mixture of all three.