Search results

• Ideas for Google Summer of Code/Discontiguous multiwords
  ...types of discontiguous multiword expressions in Germanic, Celtic, Romance, Turkic, Uralic languages
  4 KB (632 words) - 12:33, 4 March 2016
• Text to speech for Turkic
  [[Category:Turkic]]
  2 KB (380 words) - 20:49, 16 October 2017
• Apertium-tat
  ...development. It is intended to be compatible with transducers for other [[Turkic languages]] so they can be translated among. It's used in the following la
  5 KB (598 words) - 03:25, 22 January 2020
• Turkic languages/spelling
  ! "Normal" English spellings !! Native spellings !! "Turkic" spellings
  706 bytes (79 words) - 09:13, 22 May 2014
• Northern Sámi and Norwegian/smemorf
  Trimming happens using the same HFST method as in the Turkic pairs etc. [[Automatically_trimming_a_monodix#Compounds_vs_trimming_in_HFST
  3 KB (484 words) - 09:46, 15 April 2015
• Apertium-test/teststats/
  * '''families''': <section begin=families />[[Turkic languages]]<section end=families />
  2 KB (242 words) - 19:49, 3 January 2018
• Apertium-tuk
  ...[[Turkmen]]. It is intended to be compatible with transducers for other [[Turkic languages]] so that they can be translated between.
  353 bytes (43 words) - 19:51, 7 October 2013
• Apertium-uzb/stats
  * '''families''': <section begin=families />[[Turkic languages]]<section end=families />
  3 KB (324 words) - 21:41, 15 December 2019
• Turkish
  |family=[[Turkic]]
  606 bytes (78 words) - 11:38, 20 August 2011
• Uighur and Turkish/GSoC2018 report
  ...n application of Apertium to develop an MT between Uyghur and Turkish, two Turkic languages. The project consisted mainly of building a bilingual bidix, writ
  5 KB (607 words) - 13:25, 12 August 2018
• Kazakh and Tatar/Work plan
  [[Category:Turkic languages]]
  6 KB (728 words) - 19:47, 8 May 2014
• Ideas for Google Summer of Code/Extend Mitzuli to support all language pairs
  ...upport [[CG]], which a number of language pairs rely on (for example Sámi, Turkic, Breton, Welsh etc.) The objective of this task is to make Mitzuli support
  815 bytes (127 words) - 12:41, 18 February 2015
• Starting a new language with HFST
  ...re going to model today &mdash; well, start to model &mdash; is Turkmen, a Turkic language spoken in Turkmenistan. The language pair we will supposedly be wo
  16 KB (2,711 words) - 09:31, 29 October 2015
• Narimann/GSOC 2019 proposal: Kazakh-Turkish and Turkish-Kazakh
  ...ill make these pairs more valuable and will lead to further development of Turkic languages in machine translation. In addition, it will help people to commu
  8 KB (1,094 words) - 13:10, 14 April 2019
• Kazakh and Tatar/Diary
  ...ve conjunctions wouldn't make any sense for Kazah-Tatar pair (or any other Turkic pair).
  8 KB (1,205 words) - 21:50, 19 July 2012
• Buryat
  ...velopment. It is intended to be largely compatible with transducers for [[Turkic languages]] and [[Khalkha language|Khalkha]]. It is written using HFST and
  591 bytes (73 words) - 05:38, 22 August 2017
• Turkmen
  * [[Turkic languages]]
  310 bytes (31 words) - 21:16, 5 August 2015
• Chuvash
  [[Category:Turkic languages]]
  2 KB (262 words) - 08:33, 24 January 2021
• Afshar
  * [& Csató, Éva A.] (eds.) The Turkic languages. London: Routledge
  889 bytes (121 words) - 23:02, 14 March 2013
• Morphological segmentation
  In the <code>apertium-kaz/.deps</code> (or any [[Apertium Turkic]] language) directory to get the segmented output:
  581 bytes (87 words) - 20:29, 18 June 2014

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)