the ^EUq string building escape now respects the encoding (can insert bytes or codepoints) (refs #5)

* This is trickier than it sounds because there isn't one single place to consult.
  It depends on the context.
  If the string argument relates to buffer contents - as in <I>, <S>, <FR> etc. -
  the buffer's encoding is consulted.
  If it goes into a register (EU), the register's encoding is consulted.
  Everything else (O, EN, EC, ES...) expects only Unicode codepoints.
* This is communicated through a new field teco_machine_stringbuilding_t::codepage
  which must be set in the states' initial callback.
* Seems overkill just for ^EUq, but it can be used for context-sensitive
  processing of all the other string building constructs as well.
* ^V and ^W cannot be supported for Unicode characters for the time being without an Unicode-aware parser

1 files changed, 3 insertions, 3 deletions

diff --git a/src/qreg.c b/src/qreg.c
index c3ab1a5..2c2b6ad 100644
--- a/src/qreg.c
+++ b/src/qreg.c
@@ -204,14 +204,14 @@ teco_qreg_plain_get_integer(teco_qreg_t *qreg, teco_int_t *ret, GError **error)
 	return TRUE;
 }
 
-static gint
+static guint
 teco_qreg_plain_get_codepage(teco_qreg_t *qreg)
 {
 	if (teco_qreg_current)
 		teco_doc_update(&teco_qreg_current->string, teco_qreg_view);
 
 	teco_doc_edit(&qreg->string);
-	gint ret = teco_view_ssm(teco_qreg_view, SCI_GETCODEPAGE, 0, 0);
+	guint ret = teco_view_get_codepage(teco_qreg_view);
 
 	if (teco_qreg_current)
 		teco_doc_edit(&teco_qreg_current->string);
@@ -408,7 +408,7 @@ teco_qreg_external_edit(teco_qreg_t *qreg, GError **error)
 	return TRUE;
 }
 
-static gint
+static guint
 teco_qreg_external_get_codepage(teco_qreg_t *qreg)
 {
 	/*