Displaying 2 results from an estimated 2 matches for "value_encoding".
2011 Sep 17
3
[PATCH 1/1] hivexml: Base64-encode non-printable data
...riter, key, type, NULL);
- XML_CHECK (xmlTextWriterStartAttribute, (writer, BAD_CAST "value"));
- XML_CHECK (xmlTextWriterWriteString, (writer, BAD_CAST str));
- XML_CHECK (xmlTextWriterEndAttribute, (writer));
+ ret = safe_print_string_attribute (h, writer_v, "value", "value_encoding", str);
end_value (writer);
- return 0;
+ return ret;
}
static int
@@ -299,17 +351,18 @@ value_multiple_strings (hive_h *h, void *writer_v, hive_node_h node,
const char *key, char **argv)
{
xmlTextWriterPtr writer = (xmlTextWriterPtr) writer_v;
+ int ret...
2011 Sep 17
1
[PATCH 0/1] Base64-encode non-printable data
...escriptors for a values and
one for nodes. Keys and values might need to encode their names.
Values might also need to encode their data. We already know I'm
pushing for value data to go into attributes in another patch series.
Could we change the "encoding" value attribute to "value_encoding"?
* I'd like to change values' "key" attribute to "name" attributes.
Rich, what are your feelings, or what are the policies to which you're
adhering, on changing the name of an element that hivexml has already
been producing? You've been quite accepting of...