Transfuse - Revision history

Unhammer: /* Debugging transfuse issues */

2022-06-16T11:04:28Z

Debugging transfuse issues

Unhammer at 11:21, 3 June 2022

2022-06-03T11:21:22Z

Unhammer at 09:42, 3 June 2022

2022-06-03T09:42:46Z

Unhammer: Created page with "'''Transfuse''' is used under the hood for Format handling on the edges of the pipeline. See * User:Khannatanmai/Wordbound_blanks * https://github.com/TinoDidrikse..."

2022-06-03T09:34:49Z

Created page with "'''Transfuse''' is used under the hood for Format handling on the edges of the pipeline. See * User:Khannatanmai/Wordbound_blanks * https://github.com/TinoDidrikse..."

New page

'''Transfuse''' is used under the hood for [[Format handling]] on the edges of the pipeline.

See

* [[User:Khannatanmai/Wordbound_blanks]]

* https://github.com/TinoDidriksen/Transfuse

← Older revision		Revision as of 11:04, 16 June 2022
Line 27:		Line 27:
	</pre>		</pre>

	then you can <code>cp modes/foo-bar.mode modes/tf.mode</code> and insert `teez /tmp/tf1.log \| ` at the start and `\| teez /tmp/tfN.log` etc. in the middle between pipeline steps in modes/tf.mode and do things like <code>APERTIUM_TRANSFUSE=yes apertium -f docx -u -d . tf /tmp/in.docx >/tmp/out.docx</code> and then inspect /tmp/tf?.log		then you can <code>cp modes/foo-bar.mode modes/tf.mode</code> and insert <code>teez /tmp/tf1.log \| </code> at the start and <code>\| teez /tmp/tfN.log</code> etc. in the middle between pipeline steps in modes/tf.mode and do things like <code>APERTIUM_TRANSFUSE=yes apertium -f docx -u -d . tf /tmp/in.docx >/tmp/out.docx</code> and then inspect /tmp/tf?.log

@@ Line 6: / Line 6: @@
 * https://github.com/TinoDidriksen/Transfuse
+== Notes on wordblank format ==
+    The pipe may not yield nested structures, nor will Transfuse give it nested structures
+so <code><nowiki>[[t:text:SyTAKg]]nett[[/]][[t:text:SyTAKg]]lesar[[/]]</nowiki></code> is OK, while <code><nowiki>[[t:text:SyTAKg]]ne[[t:text:SyTAKg]]tt[[/]]lesar[[/]]</nowiki></code> is not.
 == Debugging transfuse issues ==

@@ Line 6: / Line 6: @@
 * https://github.com/TinoDidriksen/Transfuse
+== Debugging transfuse issues ==
+Transfuse runs the full pipeline with NUL flushing, so if you want to catch the intermediate output between stages of a mode, you need a little helper. Put this in $PATH with filename <code>teez</code>:
+<pre>
+#!/bin/sh
+[ "$1" = -z ] && shift
+[ -z "$1" ] && { echo "Expecting file as arg" >&2; exit 1; }
+awk -v out="$1" 'BEGIN{RS="\0"}{printf "%s", $0 >> out; printf "%s", $0}'
+</pre>
+then you can <code>cp modes/foo-bar.mode modes/tf.mode</code> and insert `teez /tmp/tf1.log | ` at the start and `| teez /tmp/tfN.log` etc. in the middle between pipeline steps in modes/tf.mode and do things like <code>APERTIUM_TRANSFUSE=yes apertium -f docx -u -d . tf  /tmp/in.docx >/tmp/out.docx</code> and then inspect /tmp/tf?.log