{"id":269,"date":"2022-01-26T09:13:32","date_gmt":"2022-01-26T09:13:32","guid":{"rendered":"https:\/\/software.sil.org\/flextrans\/?page_id=269"},"modified":"2023-05-12T15:14:02","modified_gmt":"2023-05-12T15:14:02","slug":"common-questions","status":"publish","type":"page","link":"https:\/\/software.sil.org\/flextrans\/help\/common-questions\/","title":{"rendered":"Common Questions"},"content":{"rendered":"<h3>Can <b>FLExTrans<\/b> help me translate between any two languages?<\/h3>\n<p><b>FLExTrans<\/b> works best between related languages. In theory, you can translate between any two languages, but big linguistic differences mean lots of work to get translation working.<\/p>\n<h3>Do I have to have FLEx lexicons in order to use <b>FLExTrans<\/b>?<\/h3>\n<p><b>FLExTrans<\/b> needs FLEx lexicons for the source and target languages. If you don&#8217;t have these, you can gradually build lexicons as you go.<\/p>\n<h3>How is <strong>FLExTrans<\/strong> different from statistical machine translation system like Google Translate?<\/h3>\n<p>Statistical systems like Google Translate rely on huge amounts of data for a given language pair. With this data models are created that make a statistical prediction of what a word or sentence translates to. <strong>FLExTrans<\/strong> does not rely on large amounts of data like this. Instead <strong>FLExTrans<\/strong> is a rule-based system. With lexicons in the source and target languages and a set of rules that specify how the source language gets transformed into the target language, <strong>FLExTrans<\/strong> can produce accurate translations. <strong>FLExTrans<\/strong> is tailor-made for low-resource languages where there is not a lot of language data available.<\/p>\n<h3>Can I work on multiple language pairs with <strong>FLExTrans<\/strong>?<\/h3>\n<p>Yes, you can make a copy of <em>TemplateProject<\/em> folder, rename it and start working on a new language pair in that folder. The work you do for the new language pair will not affect work in your original language pair. Of course, if a shared FLEx project is used, changes in that project will affect any language pair that uses it.<\/p>\n<h3>What&#8217;s the difference between a category and an attribute in the transfer rules file?<\/h3>\n<p>One significant difference is that a category always refers to the source language. You use a category to group source words together. The grouping can be very broad such as verbs or very specific such as pronouns with feminine suffixes. An attribute is related to the characteristic of a word. It can apply to both source and target words. An example attribute might be \u2018a_number\u2019 and it might have the values \u2018pl\u2019, \u2018sg\u2019 and \u2018du\u2019 for plural, singular and dual. You use a category in the \u2018pattern\u2019 part of a transfer rule to help determine whether a rule should be run on a given word. Whereas you use attributes within the \u2018action\u2019 portion of a rule. You can check if a word has a certain attribute or change a word\u2019s attribute.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Can FLExTrans help me translate between any two languages? FLExTrans works best between related languages. In theory, you can translate between any two languages, but big linguistic differences mean lots of work to get translation working. Do I have to have FLEx lexicons in order to use FLExTrans? FLExTrans needs FLEx lexicons for the source [&hellip;]<\/p>\n","protected":false},"author":68,"featured_media":0,"parent":160,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"hide_sidebar":false,"hide_h1":false,"footnotes":""},"class_list":["post-269","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/software.sil.org\/flextrans\/wp-json\/wp\/v2\/pages\/269","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/software.sil.org\/flextrans\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/software.sil.org\/flextrans\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/software.sil.org\/flextrans\/wp-json\/wp\/v2\/users\/68"}],"replies":[{"embeddable":true,"href":"https:\/\/software.sil.org\/flextrans\/wp-json\/wp\/v2\/comments?post=269"}],"version-history":[{"count":7,"href":"https:\/\/software.sil.org\/flextrans\/wp-json\/wp\/v2\/pages\/269\/revisions"}],"predecessor-version":[{"id":369,"href":"https:\/\/software.sil.org\/flextrans\/wp-json\/wp\/v2\/pages\/269\/revisions\/369"}],"up":[{"embeddable":true,"href":"https:\/\/software.sil.org\/flextrans\/wp-json\/wp\/v2\/pages\/160"}],"wp:attachment":[{"href":"https:\/\/software.sil.org\/flextrans\/wp-json\/wp\/v2\/media?parent=269"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}