OK so I've updated the conversion table to take Comet's comments into
account - they all make perfect sense to me.

I also decided to extract the data in the HTML file into an XML file so
that I could run custom XSL/XSLT templates against it to generate the
conversion table from the XML. I'll switch to the generated conversion
table at some point.

The reason for this was that I started hand-balling a keyboard map file and
found that it was taking me a significant amount of time, but more
importantly it felt wrong having the data then in two places. So after some
head scratching I got the map keyboard auto-generating from the same XML
data file.

At the moment it's a map of the Model 100 keyboard characters, I need to
think a little about how best to generate the T102/T200. It's a technical
problem that I know I can solve but I've run out of steam for today.

It would be great to get some feedback!

The updated conversion table is here:
http://wickensonline.co.uk/static/files/tandy/Unicode/TandyModelTCodetoUnicodeConversionTable.html

The new keyboard map is here:
http://wickensonline.co.uk/static/files/tandy/Unicode/TandyModelTKeyboardMap.html

Regards, Mark.



On 15 November 2015 at 18:30, Comet <[email protected]> wrote:

> Hi Mark,
>
> I am glad you found my comments helpful.
>
> I agree with you that the appearance of the Model 100 glyphs for 90 and 91
> indicate that the Unicode code points to which they correspond should have
> related symantec meanings.
> I believe Model 100 glyph looks unambiguously like the bell symbol.  This
> suggests that 91 is the “RINGING BELL”.
> 90 ⍾ &#x237E; BELL SYMBOL;
> 91 🕭 &#x1F56D; RINGING BELL
>
> I am glad you agree with me on the phone booth glyph being mapped to the
> “telephone location sign” code point.
> 81 ✆        &#9990;    \2706    Telephone location sign;
>
> For me, the semantic meaning of 82 is “telephone extension” (note the
> appearance of “x” after telephone), or basically the importance is on the
> phone number, rather than the phone device.
> If you agree this is a reasonable meaning, then you can see why I suggest
> 82 ℡    &#8481;    telephone sign
>
> For 0x83, I recommend 📱'MOBILE PHONE' (U+1F4F1), because this code point
> does not mean only cell phones, but includes satellite phones also.
> The font designer can be creative and choose to represent “mobile phone”
> with a glyph indicating a satellite phone, and this would be just as valid
> as one representing a cellular phone.
> Since Immarsat has been around since 1979, and the first widely-deployed
> North American cellular network was introduced in 1983 (after the Model
> 100), I think it makes sense that 0x83 is a generic “mobile phone.”
>
>
> *From:* Mark Wickens <[email protected]>
> *Sent:* Sunday, November 15, 2015 3:30 a.m.
> *Cc:* Model 100 Discussion <[email protected]>
> *Subject:* Re: [M100] Fwd: Re: Conversion of Tandy Model T characters
> after PCfiletransfer...
>
> Managed to get the control characters to display (the Unicode control
> character glyphs start at 0x2400)
>
> On 15 November 2015 at 10:51, Mark Wickens <[email protected]>
> wrote:
>
>> 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 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 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
>>> ⛽   ☏ &#x260F; WHITE TELEPHONE
>>> M100,83,U+1F4E1,SATELLITE ANTENNA                               📡   ☈
>>> &#x2608; THUNDERSTORM
>>> M100,84,U+1F697,AUTOMOBILE
>>> 🚗  ♿ &#x267F; WHEELCHAIR SYMBOL
>>> M100,87,U+1F6BD,TOILET
>>> 🚽   ⚚ &#x269A; STAFF OF HERMES
>>> M100,93,U+1F6B9,MENS SYMBOL                                          🚹
>>> ☺ &#x263A; WHITE SMILING FACE
>>> M100,94,U+1F6C2,PASSPORT CONTROL                              🛂  ☹
>>> &#x2639; 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 &#9990;
>>> telephone location sign -- dingbat
>>> 82 I would map to &#8481;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 &#x00A8 DIAERESIS
>>>
>>> --------
>>> Comet
>>>
>>
>

Reply via email to