This reminds me of a bug I have seen, encountered while developing the TemplateHelper Action. The issue seems to be related to any Action that generates a file – unless you tell it explicitly, it will skip the encoding step. Here’s the extra effort I had to take in TH:
function makePartial(myName,textStream){
textStream.fwConvertLineEndings = true;
textStream = fwEncode(textStream);
outFile = new FWFile;
outFile.fwSetEncoding('UTF-8');
if (outFile.fwOpenWrite('_' + myName + '.' + fwParameters['extension'],true,"TEXT","R*ch")){
fwParameters['partial'].fwClear();
outFile.fwWrite(textStream);
outFile.fwClose();
fwParameters["partial"].fwSpecify(outFile);
var partial = fwParameters["partial"].toString();
fwParameters['partial'].fwClear();
return partial.substring(1,partial.indexOf('.'));
}
fwParameters['partial'].fwClear();
return null;
}
You may want to look inside the Simple Include Pro Action and see if similar steps have been taken on the file streams that it imports.
Walter
On Nov 30, 2014, at 7:20 AM, Leif Halvard Silli (russisk.no) email@hidden wrote:
On 30 Nov 2014, at 12:52, Ernie Simpson wrote:
Hope the above was clarifying.
Well, I do appreciate the effort you’ve made to educate me. 
Well, it was helpful for myself - and hopefully to Softpress and Tim - that I had to lay out the problem more accurately.
Clearly this is beyond my area of experience. It sounds like a language
thing, like there are characters you are using not supported by UTF-8(?)
UTF-8 supports all Unicode characters. Thus your assumption is wrong (since our computers basically only permit us to enter Unicode characters). This is a bug in Freeway - nothing more or less. The issue is that while Freeway ‘itself’ has implemented Unicode/UTF-8, its import function suffers from a Mac OS Roman hangover (http://en.wikipedia.org/wiki/Mac_OS_Roman). (I use checked, and Freeway’s import function only supports Mac OS Roman - thus, it does not support Windows 1252 (Windows Latin1) files.)
It is not a surprising bug, however, in the sense that in the transition to UTF-8 (which is something every developer worth his/her salt strives for these days - though many seems to think the job is done …), there are always certain corners that developers forget. These corners seem especially easy to forget for developers that, on a day to day basis, only need to handle (to put it simply) texts in English. (Part of the reason being that the ASCII character set/encoding is a 100% valid subset of UTF-8.)
It is really a pretty simple thing … but getting developers to get it … is not always so simple.
Leif Halvard Silli
actionsdev mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
actionsdev mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options