loghaD:
I went to that link, but I see a lot of squares, where some characters ought to be. Is there a fix for this ? qunnoH jan puqloD On Wed, Nov 9, 2016 at 10:37 PM, Felix Malmenbeck <felixm@kth.se> wrote:
Lovely!
I'd recommend adding some more examples of use by the Klingon-speaking community and random folks, rather than focusing CBS/Paramount sources. After all, we've been using this writing system since before it was cool, and it makes the argument that there's a community behind it, rather than just a company.
To name some examples:
Every day, chaDQI posts original pIqaD calligraphy on Instagram, normally tagged #klingonshodo: https://www.instagram.com/explore/tags/klingonshodo/
Every day, qurgh's Klingon Word of the Day on Facebook supplies pIqaD transliterations for all words.
The Misfit Shine has product details written in pIqaD: https://techcrunch.com/2014/04/20/the-secret-is-klingon/
The app sBASSdrum had a press release written in pIqaD: http://www.seqmedia.com/projects/sbassdrum/sBASSdrum_Klingon_PressRelease_20...
People have been playing Scrabble using pIqaD for more than a decade: 2004 source: http://www.lillsjon.net/~v108e/swecon.html More recent source: http://www.klingonwiki.net/En/Scrabble
...and now there's also Bananagrams: https://twitter.com/Bananagrams_uk/status/525971513229725696
...and at least two versions of 2048: iOS: https://scontent-arn2-1.xx.fbcdn.net/v/t1.0-9/10363505_10152422262290120_215... HTML5: https://scontent-arn2-1.xx.fbcdn.net/v/t1.0-9/10363505_10152422262290120_215...
I've collected quite a few examples - large and small - using the Twitter account @pIqaD: https://twitter.com/pIqaD
//loghaD
________________________________________ From: tlhIngan-Hol <tlhingan-hol-bounces@lists.kli.org> on behalf of Mark Shoulson <mark@kli.org> Sent: Tuesday, November 8, 2016 02:16 To: tlhIngan-Hol@kli.org Subject: [tlhIngan Hol] pIqaD in Unicode--again
Thought I would let people here know, since I have sort of acted on my own on this. I've submitted another paper to the Unicode Consortium asking to encode pIqaD finally: http://www.unicode.org/L2/L2016/16329-piqad-returns.pdf They always said it wasn't encoded because people weren't using it: I disprove that claim in the document. The discussion on the mailing list there is starting to heat up again; this time they're saying that there are problems with Paramount's copyright and all, but that's also not relevant, and even if it is, they should decide whether or not to encode and *then* we'll worry about difficulties carrying that out.
Anyway, just informing folks. I've been talking to various UTC members, and the official UTC meeting is this week or next week or something, so it will be brought up then and they'll probably have at least some sort of response after that. I'm not going to let them off the hook without at least some *sensible* answer and a path forward (and an explanation as to why the Tolkien alphabets, which apparently may also have copyright issues, are on the Roadmap, even if they aren't encoded, while pIqaD is not only not on the roadmap, but given as an example on the "Not on the Roadmap" page as something not worthy of being there.) Just FYI.
~mark
_______________________________________________ tlhIngan-Hol mailing list tlhIngan-Hol@lists.kli.org http://lists.kli.org/listinfo.cgi/tlhingan-hol-kli.org _______________________________________________ tlhIngan-Hol mailing list tlhIngan-Hol@lists.kli.org http://lists.kli.org/listinfo.cgi/tlhingan-hol-kli.org