I think this won’t work well since the SGF format is based on ASCII, so we’ll probably have to stick with the emoticons we know, or do it like this: <sweat>
please no emoticon pictures.
The big advantage automatical phrases bear is the transcendence of language barriers. However, I just treat everything I don’t understand at the beginning or end of a game as a polite greeting.
A sophisticated move comment and communication tool is too much in my opinion.
I think stephenM’s idea is better than the ‘translated greetings’ … but…
no emoticons in automated messages, because its.
not needed
not neccesary that you always want to show same kind of feeling every time you use a specific statement.
but i figure that these kind of messages could be good for teaching games and/or reviews, so allowing them to be automatically translated to whomevers native tounge on the fly is a great idea
Actually, fields of type text and simpletext can use any character encoding you specify. Comments are of type text, so in theory you could use something like utf-8 and have all those emoji things (http://www.alanwood.net/unicode/emoticons.html)
From the spec:
SGF uses the US ASCII char-set for all its property identifiers and
property values, except SimpleText & Text. For SimpleText & Text the
charset is defined using the CA property.
Apologies for resurrecting an old thread, but it’s to save starting a new one.
I’ve made a Chrome/Firefox extension which adds the functionality described above. It’s already available in the Chrome webstore, and it’s been submitted to Mozilla Add-ons for review, so should be available for Firefox soon.
Any suggestions for improvement or bug reports are appreciated, and you can view the source on Github.
Edit: After a brief 6 week wait in the review queue, the Firefox version has been approved
It would be nice to have an optional custom mini-text to show instead of the plain numbers (and personally, I’d remove the “quick chat” title aswell, but that’s just me being annoying ).