Talk:Apertium and Constraint Grammar - Revision history

Unhammer: whatever this was it's outdated now

2014-09-18T11:00:54Z

whatever this was it's outdated now

Unhammer: /* Ability to specify where a MAPPING tag should be added in the tag_list */ no longer applicable

2013-10-03T08:46:44Z

Ability to specify where a MAPPING tag should be added in the tag_list: no longer applicable

Unhammer: /* Ability to specify where a MAPPING tag should be added in the tag_list */

2010-02-23T13:13:16Z

Ability to specify where a MAPPING tag should be added in the tag_list

Unhammer: /* Wishlist */

2010-02-23T13:10:16Z

Wishlist

Unhammer: /* Wishlist */ new section

2010-02-23T13:06:34Z

Wishlist: new section

Francis Tyers at 11:55, 26 August 2009

2009-08-26T11:55:04Z

Trondtr: /* Compiling vislcg3 on Mac */

2009-08-26T06:22:31Z

Compiling vislcg3 on Mac

Francis Tyers at 22:55, 21 March 2009

2009-03-21T22:55:23Z

Francis Tyers: /* Compiling vislcg3 on Mac */

2009-03-21T22:42:58Z

Compiling vislcg3 on Mac

Unhammer: /* Compiling vislcg3 on Mac */ new section

2009-03-21T22:17:36Z

Compiling vislcg3 on Mac: new section

@@ Line 116: / Line 116: @@
 ==Current bugs==
-== Compiling vislcg3 on Mac ==
-I kept getting this error
-<pre>
-ld: symbol(s) not found
-collect2: ld returned 1
-</pre>
-on my Mac. According to [http://www.justatheory.com/computers/databases/postgresql/howto_avoid_tigers_readline.html this], it's related to GNU readline not being discovered. I tried installing GNU readline from both MacPorts and source, no help, tried using CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib, even moving Apple's readline files out of the way, finally gave up and tried the ./compile-mac.sh script, but this didn't give me the cg-comp and cg-proc files; but then on my next try, after make distclean, it compiled (no CPPFLAGS/LDFLAGS). I still don't know why, but hey, it works. {{unsigned|Unhammer}}
-:Strange. I don't have a mac to test this on, but on the other macs I've tried it compiled without problems. (Apart from having to install ICU) - [[User:Francis Tyers|Francis&nbsp;Tyers]] 22:42, 21 March 2009 (UTC)
-::After vislcg3 was tuned to Mac (in 2006-2007?) I '''never''' have any problems in compiling it on the Mac (and never saw that error msg). The only tweak is, as Francis says, that ICU must be installed. If the problem is still there, please write more, or contact Tino Dideriksen. [[User:Trondtr|Trondtr]] 06:22, 26 August 2009 (UTC).
 == Wishlist ==

@@ Line 130: / Line 130: @@
 == Wishlist ==
-=== Ability to specify where a MAPPING tag should be added in the tag_list ===
+=== <strike>Ability to specify where a MAPPING tag should be added in the tag_list</strike> ===
 Tags in vislcg3 are "unordered", but the input order is preserved, and MAPPING tags are added to the end. However, since Apertium matches longest left-to-right strings, we may have to disambiguate between
 <code>ganga# i<vblex></code> and <code>ganga<vblex>+i<pr></code>. The first one is easy, "ganga# i" is seen as the baseform and there is just one tag, vblex, we might get something like <code>ganga# i<vblex><@FVMAIN></code>. The second one is worse. The + means that the multiword should be split into two before transfer, <code>^ganga<vblex>$ ^i<pr>$</code>; but if the mapping tags go to the end, or even after the first word, we'll get <code>^ganga<vblex><@FVMAIN><@PART>+i<pr>$</code> or <code>^ganga<vblex>+i<pr><@FVMAIN><@PART>$</code>, but we want <code>^ganga<vblex><@FVMAIN>+i<pr><@PART>$</code>.
@@ Line 141: / Line 141: @@
 </pre>
+: This is better done using [[Subreadings]].
-'''Implementation''':
-In the file src/Grammar.cpp, tags are added to the end of list tags_list as they are read (this is the order we follow in outputting the tags). Perhaps MAPPING tags could be spliced into a certain position in this list, after the N'th +, if the target ends with :N?
-(It might make things slightly faster to keep a note of the tags_list-position of any tags starting with a + on reading the input, although since tags may be removed by SUBSTITUTE, this could create problems...)

@@ Line 134: / Line 134: @@
 <code>ganga# i<vblex></code> and <code>ganga<vblex>+i<pr></code>. The first one is easy, "ganga# i" is seen as the baseform and there is just one tag, vblex, we might get something like <code>ganga# i<vblex><@FVMAIN></code>. The second one is worse. The + means that the multiword should be split into two before transfer, <code>^ganga<vblex>$ ^i<pr>$</code>; but if the mapping tags go to the end, or even after the first word, we'll get <code>^ganga<vblex><@FVMAIN><@PART>+i<pr>$</code> or <code>^ganga<vblex>+i<pr><@FVMAIN><@PART>$</code>, but we want <code>^ganga<vblex><@FVMAIN>+i<pr><@PART>$</code>.
-CG Syntax change:
+'''CG Syntax change''':
 We could say something like
 <pre>
@@ Line 141: / Line 141: @@
 </pre>
-Implementation:
+'''Implementation''':
-In the file src/Grammar.cpp, tags are added to the end of list tags_list as they are read (this is the order we follow in outputting the tags). Perhaps MAPPING tags could be spliced into a certain position in this list?
+In the file src/Grammar.cpp, tags are added to the end of list tags_list as they are read (this is the order we follow in outputting the tags). Perhaps MAPPING tags could be spliced into a certain position in this list, after the N'th +, if the target ends with :N?
+(It might make things slightly faster to keep a note of the tags_list-position of any tags starting with a + on reading the input, although since tags may be removed by SUBSTITUTE, this could create problems...)

@@ Line 130: / Line 130: @@
 == Wishlist ==
+=== Ability to specify where a MAPPING tag should be added in the tag_list ===
-Ability to specify where a MAPPING tag should be added in the tag_list
 Tags in vislcg3 are "unordered", but the input order is preserved, and MAPPING tags are added to the end. However, since Apertium matches longest left-to-right strings, we may have to disambiguate between
 <code>ganga# i<vblex></code> and <code>ganga<vblex>+i<pr></code>. The first one is easy, "ganga# i" is seen as the baseform and there is just one tag, vblex, we might get something like <code>ganga# i<vblex><@FVMAIN></code>. The second one is worse. The + means that the multiword should be split into two before transfer, <code>^ganga<vblex>$ ^i<pr>$</code>; but if the mapping tags go to the end, or even after the first word, we'll get <code>^ganga<vblex><@FVMAIN><@PART>+i<pr>$</code> or <code>^ganga<vblex>+i<pr><@FVMAIN><@PART>$</code>, but we want <code>^ganga<vblex><@FVMAIN>+i<pr><@PART>$</code>.
+CG Syntax change:
+We could say something like
+<pre>
+MAP (@FVMAIN) TARGET VPart:0 (1* FOO);
+MAP (@PART) TARGET VPart:1 (-1* BAR);
+</pre>
+Implementation:
+In the file src/Grammar.cpp, tags are added to the end of list tags_list as they are read (this is the order we follow in outputting the tags). Perhaps MAPPING tags could be spliced into a certain position in this list?

@@ Line 128: / Line 128: @@
 :Strange. I don't have a mac to test this on, but on the other macs I've tried it compiled without problems. (Apart from having to install ICU) - [[User:Francis Tyers|Francis&nbsp;Tyers]] 22:42, 21 March 2009 (UTC)
 ::After vislcg3 was tuned to Mac (in 2006-2007?) I '''never''' have any problems in compiling it on the Mac (and never saw that error msg). The only tweak is, as Francis says, that ICU must be installed. If the problem is still there, please write more, or contact Tino Dideriksen. [[User:Trondtr|Trondtr]] 06:22, 26 August 2009 (UTC).
+== Wishlist ==
+Ability to specify where a MAPPING tag should be added in the tag_list
+Tags in vislcg3 are "unordered", but the input order is preserved, and MAPPING tags are added to the end. However, since Apertium matches longest left-to-right strings, we may have to disambiguate between
+<code>ganga# i<vblex></code> and <code>ganga<vblex>+i<pr></code>. The first one is easy, "ganga# i" is seen as the baseform and there is just one tag, vblex, we might get something like <code>ganga# i<vblex><@FVMAIN></code>. The second one is worse. The + means that the multiword should be split into two before transfer, <code>^ganga<vblex>$ ^i<pr>$</code>; but if the mapping tags go to the end, or even after the first word, we'll get <code>^ganga<vblex><@FVMAIN><@PART>+i<pr>$</code> or <code>^ganga<vblex>+i<pr><@FVMAIN><@PART>$</code>, but we want <code>^ganga<vblex><@FVMAIN>+i<pr><@PART>$</code>.

← Older revision		Revision as of 06:22, 26 August 2009
Line 127:		Line 127:

	:Strange. I don't have a mac to test this on, but on the other macs I've tried it compiled without problems. (Apart from having to install ICU) - [[User:Francis Tyers\|Francis Tyers]] 22:42, 21 March 2009 (UTC)		:Strange. I don't have a mac to test this on, but on the other macs I've tried it compiled without problems. (Apart from having to install ICU) - [[User:Francis Tyers\|Francis Tyers]] 22:42, 21 March 2009 (UTC)
			::After vislcg3 was tuned to Mac (in 2006-2007?) I '''never''' have any problems in compiling it on the Mac (and never saw that error msg). The only tweak is, as Francis says, that ICU must be installed. If the problem is still there, please write more, or contact Tino Dideriksen. [[User:Trondtr\|Trondtr]] 06:22, 26 August 2009 (UTC).

← Older revision		Revision as of 22:55, 21 March 2009
Line 126:		Line 126:
	on my Mac. According to [http://www.justatheory.com/computers/databases/postgresql/howto_avoid_tigers_readline.html this], it's related to GNU readline not being discovered. I tried installing GNU readline from both MacPorts and source, no help, tried using CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib, even moving Apple's readline files out of the way, finally gave up and tried the ./compile-mac.sh script, but this didn't give me the cg-comp and cg-proc files; but then on my next try, after make distclean, it compiled (no CPPFLAGS/LDFLAGS). I still don't know why, but hey, it works.		on my Mac. According to [http://www.justatheory.com/computers/databases/postgresql/howto_avoid_tigers_readline.html this], it's related to GNU readline not being discovered. I tried installing GNU readline from both MacPorts and source, no help, tried using CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib, even moving Apple's readline files out of the way, finally gave up and tried the ./compile-mac.sh script, but this didn't give me the cg-comp and cg-proc files; but then on my next try, after make distclean, it compiled (no CPPFLAGS/LDFLAGS). I still don't know why, but hey, it works.

	:Strange. I don't have a mac to test this on, but on the other macs I've tried it compiled without problems. (Apart from having to install ICU) - [[User:Francis Tyers\|Francis&~~amp;~~nbsp;Tyers]] 22:42, 21 March 2009 (UTC)		:Strange. I don't have a mac to test this on, but on the other macs I've tried it compiled without problems. (Apart from having to install ICU) - [[User:Francis Tyers\|Francis Tyers]] 22:42, 21 March 2009 (UTC)

@@ Line 125: / Line 125: @@
 </pre>
 on my Mac. According to [http://www.justatheory.com/computers/databases/postgresql/howto_avoid_tigers_readline.html this], it's related to GNU readline not being discovered. I tried installing GNU readline from both MacPorts and source, no help, tried using CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib, even moving Apple's readline files out of the way, finally gave up and tried the ./compile-mac.sh script, but this didn't give me the cg-comp and cg-proc files; but then on my next try, after make distclean, it compiled (no CPPFLAGS/LDFLAGS). I still don't know why, but hey, it works.
+:Strange. I don't have a mac to test this on, but on the other macs I've tried it compiled without problems. (Apart from having to install ICU) - [[User:Francis Tyers|Francis&amp;nbsp;Tyers]] 22:42, 21 March 2009 (UTC)