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

Translation of Chinese Ancient text's #30

Open
karpalig opened this issue Nov 14, 2019 · 6 comments
Open

Translation of Chinese Ancient text's #30

karpalig opened this issue Nov 14, 2019 · 6 comments

Comments

@karpalig
Copy link

Hey Team,
I'm a Master student in Beijing Normal University study in Chinese Philosophy. I want personally create database of translation of Chinese text like ctext.org but in Russian language. As I have background as WordPress developer thought is not difficult however I was wrong.

Somehow I here and would like to understand what happening here and quickly try to use mine text based on your product. What is start point form me?

Best,
Alex

@PonteIneptique
Copy link
Member

Hey Alex,
Nice to meet you :)
I think the starting point would be to format your data in the same kind of XML that we use, ie. TEI XML following Capitains Guidelines. Unfortunately, I do not speak Chinese nor Russian, so I hope my example will be good:

<?xml version="1.0" encoding="UTF-8"?>
<?xml-model href="http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/tei_all.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?>
<?xml-model href="http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/tei_all.rng" type="application/xml"
	schematypens="http://purl.oclc.org/dsdl/schematron"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
  <teiHeader>
      <fileDesc>
         <titleStmt>
            <title>Analects</title>
            <author>Xian Jin</author>
            <editor>Karpalig</editor>
         </titleStmt>
         <publicationStmt>
            <p>Publication Information</p>
         </publicationStmt>
         <sourceDesc>
            <p>From https://ctext.org/analects/xian-jin</p>
         </sourceDesc>
      </fileDesc>
     <encodingDesc>
        <refsDecl n="CTS">
         <cRefPattern 
            n="level1"
            matchPattern="(\w+)"
            replacementPattern="#xpath(/tei:TEI/tei:text/tei:body/tei:div[@n='$1'])">
            <p>This pointer pattern extracts level1</p>
         </cRefPattern>
        </refsDecl>
     </encodingDesc>
  </teiHeader>
  <text xml:lang="unk" n="urn:cts:cText:authorId.textId.karpalig">
      <body>
         <div type="textpart" n="1">
            <p n="ch">子曰:「先進於禮樂,野人也;後進於禮樂,君子也。如用之,則吾從先進。」</p>
            <p n="en">The Master said, "The men of former times in the matters of ceremonies and music were rustics, it is said, while the men of these latter times, in ceremonies and music, are accomplished gentlemen. If I have occasion to use those things, I follow the men of former times."</p>
         </div>
         
         <div>
            <p n="ch">子曰:「從我於陳、蔡者,皆不及門也。」</p>
            <p n="en">The Master said, "Of those who were with me in Chen and Cai, there are none to be found to enter my door."</p>
         </div>
      </body>
  </text>
</TEI>

Does it make sense ?
Best,

@karpalig
Copy link
Author

karpalig commented Nov 16, 2019

Thank you for quick response. It make sense for sure. We can use oxygen to do that? Or what program like oxygen can be configured for this? Is template is useful?

2019-11-16_11-37-58

@karpalig
Copy link
Author

karpalig commented Nov 16, 2019

So I had choose all and hopefully was right header is the same, am i right?

I think you probably want to use xml:lang rather than n for the “ch” and “en” attributes on <p>
<p xml:lang="ch"> instead of <p n="ch">

What is better way to have more that 2 translators?

@karpalig
Copy link
Author

For instance I have prepare *.xls file with several translation for this text: https://ctext.org/dao-de-jing

image

@balmas
Copy link
Contributor

balmas commented Nov 18, 2019

I think yes, the TEI P5 template from oXygen should be what you want to use. Agree than the chinese language should be specified in the xml:lang attribute of any element (or ancestor) that contains chinese text (although maybe consider using the ISO 639-2 3 character code zho?)

Regarding multiple translations, the Capitains Guidelines recommending putting each translation in a separate file.

Hope this is helpful!

@karpalig
Copy link
Author

karpalig commented Jan 18, 2020 via email

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

3 participants