$snippet->code = chunk_split(base64_encode($translation));
So chunk_split seems to be the main difference here. In NemeinLocalization we just: $string=base64_encode($translation);
I don't have the time to look more deeply into this right now, however it appears that MidCOM uses something like NemeinLocalization but it's not (meant to be) compatible ? The storage format is different: "l10n" doesn't have executable code in the snippets, just base64 encoded data (While nemeinloc has code that sets $string [which contains base64 encoded data] and $myguid, which the functions use, the advantage is getting all needed data with single mgd_include_snippet in stead of doing mgd_snippedir_by_path and get_snippet_by_name and then decoding $snippet->code)
The base64 storage (and snippet name) is not a problem to special characters, so the limitation must be elsewhere (propably the editor itself)
/Rambo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
