Working with twol - Revision history

Rcrowther at 12:26, 26 September 2016

2016-09-26T12:26:59Z

Firespeaker: /* Guidelines */

2015-11-06T18:10:56Z

Guidelines

Firespeaker at 21:13, 4 October 2015

2015-10-04T21:13:01Z

Unhammer: /* See also */

2014-12-30T08:10:57Z

Unhammer at 08:10, 30 December 2014

2014-12-30T08:10:45Z

Francis Tyers at 19:25, 1 February 2012

2012-02-01T19:25:15Z

Francis Tyers at 19:23, 1 February 2012

2012-02-01T19:23:16Z

Francis Tyers at 19:22, 1 February 2012

2012-02-01T19:22:59Z

Francis Tyers: Created page with ' ==Guidelines== * Every rule should have a comment giving the input from the morphotactics (e.g. `те>{A}т{ь}` and the expected output from the phonology `т…'`


2012-02-01T19:22:44Z
Created page with ' ==Guidelines==  * Every rule should have a comment giving the input from the morphotactics (e.g. <code>те>{A}т{ь}</code> and the expected output from the phonology <code>т…'
New page


==Guidelines==



* Every rule should have a comment giving the input from the morphotactics (e.g. <code>те>{A}т{ь}</code> and the expected output from the phonology <code>тет</code>) -- no exceptions.

@@ Line 48: / Line 48: @@
 [[Category:Documentation]]
+[[Category:Documentation in English]]
 [[Category:HFST]]

@@ Line 1: / Line 1: @@
 ==Guidelines==
-* Every rule should have a comment giving the input from the morphotactics (e.g. <code>те>{A}т{ь}</code> and the expected output from the phonology <code>тет</code>) -- no exceptions.
+* Every rule should have a comment giving the input from the morphotactics (e.g. <code>те>{A}т{ь}</code> and the expected output from the phonology <code>тет</code>) -- no exceptions.  The current format for this is as follows:
+: <code>!@ т е >:0 {A}:0 т {ь}:0</code>
 * Define your alphabet, no jokes. It should contain all your alphabetic symbols, and your [[archiphonemes]] with their default realisations.
+* Some limitations:
+** You can't insert from 0; i.e., you can't write a rule like <code>0:n</code> and expect to be able to insert n.  You must specify an archiphoneme (like <code>{n}</code>) where you need insertion to happen.
+** You shouldn't have two characters as the input or output of a rule.  So instead of having a rule like <code>cc:sh</code>, you will need two rules: <code>c:s</code> and <code>c:h</code>, with appropriate contexts.
 == Writing rules ==

@@ Line 4: / Line 4: @@
 * Define your alphabet, no jokes. It should contain all your alphabetic symbols, and your [[archiphonemes]] with their default realisations.
+== Writing rules ==
+=== Deciding on the input symbol ===
+Deciding on the input symbol is the first problem that needs to be solved for writing a twol rule.  This is the symbol that gets implemented in the morphology, and constitutes the first part of any rule.
+The idea of the input symbol, for anyone familiar with phonology, is roughly the same idea as the underlying form.  If you have a good understanding of what this is, then you can probably skip much of this document; for everyone else, keep reading.
+In simple cases, the input symbol is often simply the most common form of the character to occur.  For example, if ''x'' changes to ''y'' in some restricted condition, then ''x'' is the input symbol, since it occurs in the must unrestricted environment, and ''y'' is a conditioned output symbol.  See [[#Phonologically conditioned symbol change]] for how to write this kind of rule.
+In some cases, it's not clear what the input symbol should be, since its output forms occur in restricted environments.  Vowel harmony is a good example of this.  For these cases, you should probably choose an archiphoneme.  Apertium convention is to put archiphonemes in <code>{}</code>s, with archiphonemes that primarily change form in upper case (e.g., {{archi|A}}) and archiphonemes that delete in lower case (e.g., {{archi|y}}).  Note that the <code>{}</code>s have to be escaped with <code>%</code>.  See ... for more information on how to write this kind of rule.
+When you want to delete a character, the input character is simply the character that gets deleted.  See [[#Phonologically conditioned deletion]] for more information.
+When you want to insert a character, you again have to use an archiphoneme, since otherwise you have no input character.  To learn more about writing this sort of rule, see [[#Phonologically conditioned insertion]].
+=== Types of rules ===
+==== Phonologically conditioned deletion ====
+==== Morphologically conditioned deletion ====
+==== Phonologically conditioned symbol change ====
+There's actually several types of this:
+* one character to another
+* multiple characters to one character
+* one character to multiple characters
+* unknown input character to one of a number of characters
+==== Morphologically conditioned symbol change ====
+==== Phonologically conditioned insertion ====
+==== Morphologically conditioned insertion ====
 ==See also==

@@ Line 10: / Line 10: @@
 [[Category:Documentation]]
+[[Category:HFST]]
 [[Category:Writing dictionaries]]

← Older revision		Revision as of 08:10, 30 December 2014
Line 9:		Line 9:

	[[Category:Documentation]]		[[Category:Documentation]]


			[[Category:Writing dictionaries]]

Working with twol - Revision history

Rcrowther at 12:26, 26 September 2016

Firespeaker: /* Guidelines */

Firespeaker at 21:13, 4 October 2015

Unhammer: /* See also */

Unhammer at 08:10, 30 December 2014

Francis Tyers at 19:25, 1 February 2012

Francis Tyers at 19:23, 1 February 2012

Francis Tyers at 19:22, 1 February 2012

Francis Tyers: Created page with ' ==Guidelines== * Every rule should have a comment giving the input from the morphotactics (e.g. те>{A}т{ь} and the expected output from the phonology т…'

Francis Tyers: Created page with ' ==Guidelines== * Every rule should have a comment giving the input from the morphotactics (e.g. `те>{A}т{ь}` and the expected output from the phonology `т…'`