Re: Representing EBCDIC code 37 in xslt

Setting FTP  transmission mode to ASCII introduces another set of
question marks. Its effect depends on what FTP, for either side, assumes
as the default encoding for ASCII files. If the output of an XSLT transformation
does not agree with what FTP expects, you are in for trouble.
-W

On 30/12/2013, a kusa <akusa8@xxxxxxxxx> wrote:
> Yes, the transformation does run on the unix box after which I FTP to
> mainframe.
>
> I have FTP set to ASCII. I am using <xsl:output-character> to replace
> the latin-1 characters with the equivalent EBCDIC code 037 values.
>
> The output from my transformation is in UTF-8. I have tried setting it
> to ISO-8859-1. That didn't help either.
>
>
> On Mon, Dec 30, 2013 at 1:37 PM, Michael Kay <mike@xxxxxxxxxxxx> wrote:
>>
>> On 30 Dec 2013, at 18:52, a kusa <akusa8@xxxxxxxxx> wrote:
>>
>>> Hi Michael:
>>>
>>> Thanks for your quick response. I did mention that I tried utf-8 and
>>> iso-8859-1 encoding. I cannot set the whole encoding to EBCDIC since
>>> that will change all the other text to gibberish.
>>>
>>
>>
>> Further to my previous response: you appear to be running the
>> transformation on a Unix box and then doing an FTP of the result to a
>> mainframe.
>>
>> Is the FTP in text mode or binary mode, that is, are you expecting the FTP
>> to do UTF8-to-EBCDIC conversion?
>>
>> If you expect the FTP to do code conversion, then (a) you must configure
>> it correctly to do so, and (b) the output from your transformation must be
>> in UTF8.
>>
>> If you don't expect the FTP to do code conversion, then (a) you need to
>> configure it so it does not do so, and (b) you need to generate the whole
>> output in EBCDIC encoding on the UNIX box, using an appropriate value for
>> <xsl:output encoding="..."/>
>>
>> Michael Kay
>> Saxonica