printer logger ascii chars doesn't match

By thegeps

Champion (368)

thegeps's picture

04-02-2020, 12:07

when I write a basic program and want to export it in an asc file, I can use the logger print, selcting printer port: logger from catapult misc control options. All works fine with normal chars, but when I have a string where there are special chars inside, obtained by pressing alt+q,w,e,r,t,y,ecc during emulation, they are otputted wrong. I know that special chars are different from those used by Windows, but it was expected that if I do a copy&paste from printlogged file to input text mask on catapult, the string is outputted correcty to emulator. But chars are totally different this time too... I need it to act correctly cause I can compress graphic infos in basic listing for basic contest and reduce chars usage...

Login or register to post comments

By Manuel

Ascended (16125)

Manuel's picture

04-02-2020, 23:59

It depends a bit on which MSX model you're emulating. When pasting, an attempt to translate the characters to MSX characters is attempted, depending on the MSX model you're using.

The printer logger is not attempting to do such a (reverse) translation. It just outputs the bytes that are sent by the MSX, whatever they mean.

I have plans to make such a translation into the 'copy to clipboard' feature, though. But it's taking more work than I anticipated and I don't have enough time to work on it lately.

By thegeps

Champion (368)

thegeps's picture

05-02-2020, 00:52

Thank you as always Manuel. But I saw that mismatching can be avoided. Simply I can edit all the code with a notepad and after loaded it from dir as disk I can edit chars in the emulator and save it with ,A option in dir as disk. Chars will appear weird on pc, but when loaded from openMSX they will be as they were saved Wink so I can do this way until you make the translation

By Manuel

Ascended (16125)

Manuel's picture

05-02-2020, 07:44

This method is the best: no translation needed. As I said, there is no 100% to and from translation possible. And the translation from MSX to unicode is only planned in the copy-from-screen function.