Many thanks for all the input. Ron: I've corrected the copy-paste error. Comet: I have incorporated many of your suggestions and I agree with your philosophy.
The revised and permanent home for the table is now: http://wickensonline.co.uk/static/files/tandy/Unicode/TandyModelTCodetoUnicodeConversionTable.html I got light-hearted ribbing from a Unix-oriented work colleague for having spaces in the URI so I've removed them. As I use Windows Server 2012 R2 at home together with a good smattering of Ubuntu, Debian and OpenVMS I changed to Camel Case to placate him :D I have embedded the GNU Unifont truetype font in the HTML file - this is a really nice for font this application as it is based on bitmap glyphs and has good coverage. I'm still learning how best to provide the appropriate fonts so that the table will render with as many possible glyphs on as many possible devices. The only issue I have with rendered glyphs is that the control characters are not yet being displayed, I'll work on that later. The remaining question marks regarding suitable unicode glyphs for me are (Model T character positions quoted): 0x90 and 0x91 - these are currently mapped to the Bell and Peace symbol. I believe that characters 0x90 & 0x91 are meant to represent two positions of a Space Invader. I'd be happier if these mapped to something with the equivalent semantic meaning. 0x81 and 0x82 - to me these look like a payphone and an off-hook payphone. I think the current Unicode glyph assigned to 0x82 ✆ is a better fit for 0x81 and an 'off-hook' symbol should be assigned to 0x82, but I haven't found one of those. 0x83 - I understand the argument that this may be representing a 'wireless' phone connection - either satellite link or mobile phone. I'm on the fence with this one. Mobile phone might be a more useful glyph to use, but satellite dish is cooler :) Regards, Mark. On 15 November 2015 at 08:48, _ Comet <[email protected]> wrote: > http://bitchin100.com/wiki/index.php?title=Unicode_Mappings suggests > alternate translations for some of the Unicode code points. > (Chris Osburn) > M100,81,U+26FD,FUEL PUMP ⛽ > ☏ ☏ WHITE TELEPHONE > M100,83,U+1F4E1,SATELLITE ANTENNA 📡 ☈ > ☈ THUNDERSTORM > M100,84,U+1F697,AUTOMOBILE 🚗 > ♿ ♿ WHEELCHAIR SYMBOL > M100,87,U+1F6BD,TOILET > 🚽 ⚚ ⚚ STAFF OF HERMES > M100,93,U+1F6B9,MENS SYMBOL 🚹 ☺ > ☺ WHITE SMILING FACE > M100,94,U+1F6C2,PASSPORT CONTROL 🛂 ☹ > ☹ WHITE FROWING FACE > > I believe it is more important to match the semantic meaning, rather than > the particular glyph appearance, as Unicode explicitly defines MEANINGS, > and does leave it to font designers much freedom in designing the > particular glyph appearances, so downloading the proper graphics should be > secondary to assigning the proper meaningful Unicode point. > : > 81 looks like it's intended to indicate a phone booth, so ✆ > telephone location sign -- dingbat > 82 I would map to ℡telephone sign > 83 It doesn't look like it means "Thunderstorm" to me, although I can > kinda see a satellite antenna. I think the meaning is 📱'MOBILE PHONE' > (U+1F4F1) > 84 means formula one style racing car to me, so 🏎 U+1F3CE > 87 looks like it means 🖀 'TELEPHONE ON TOP OF MODEM' (U+1F580). > > 93 and 94 are not looking like they mean any kind of white face at all; to > me, they convey the following meanings: > 93 is gender-neutral pedestrian 🚶 U+1F6B6 > 94 is gender-neutral dancer 💃 U+1F483 > > 224 E0 does not duplicate "space" to me. Its presence by the graphic > drawing characters means 'EM QUAD' (U+2001) space to me. > > 190 BE looks, even for the Model 100, like it means ¨ DIAERESIS > > -------- > Comet > > ------------------------------ > *From:* Ron Wiesen <[email protected]> > *To:* 'Model 100 Discussion' <[email protected]> > *Sent:* Friday, November 13, 2015 5:02 AM > *Subject:* Re: [M100] Fwd: Re: Conversion of Tandy Model T characters > after PC filetransfer... > > > > Here is the fruits of my labour > The table you’ve made is a handy reference that some folks will > appreciate. The table has an error that I believe is the result of an > intended “Copy_Paste_then_Edit” operation where the Edit didn’t happen: see > the CHR$(254) description which should read “BLACK LOWER RIGHT TRIANGLE” > rather than “BLACK UPPER RIGHT TRIANGLE”. > > > > > http://www.wickensonline.co.uk/static/files/tandy/Tandy%20Model%20T%20Code%20to%20Unicode%20Generated%20V1.7.html > > > >
