Where is Klingon?

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Searching the font list for Klingon (piqad).
2. Examine the list.
3. Can't see Klingon (piqad) to download.

What is the expected output? What do you see instead?
I expect to see Klingon (piqad). I see no Klingon (piqad).

What version of the product are you using? On what operating system?
None yet. All OS's. I'm a developer. 

Please provide any additional information below.
We are using a language translation API (Bing) for our interface and it 
supports two forms of Klingon including "piqad" but all I see is tofu. Thought 
you guys might be on top of it. :-) 

Original issue reported on code.google.com by rlindab...@gmail.com on 21 Aug 2014 at 1:23

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

My guess is that until the Klingon script is encoded in Unicode, the chances of 
there being a Noto font that supports it is somewhere between zero and none. 
Keep in mind that the Klingon script was proposed and rejected, but that was 
several years ago during the early years of Unicode, and I would argue that 
many of the characters being accepted today, such as emoji, would have been 
rejected on similar grounds way back then.

In other words, please consider re-proposing the Klingon script. The worst that 
can happen is that it is rejected (again). Then again, there might be 
sufficient stigma associated with its earlier rejection to make the acceptance 
hurdle overly high.

Original comment by ken.lu...@gmail.com on 25 Aug 2014 at 4:55

[GoogleCodeExporter]

Klingon (as commonly written in the Latin script) is supported by Noto Sans and 
Noto Serif. Assigning the issue to myself to make sure the Noto web pages 
report Klingon 

Klingon as written in pIqaD are not encoded in Unicode yet, so we don't have 
any plans to support it in Noto yet.

(CC-ing our local Klingon expert.)

Original comment by roozbeh@google.com on 28 Aug 2014 at 5:03

• Changed state: Accepted
• Added labels: Component-Website

[GoogleCodeExporter]

Klingon pIqaD is currently mapped to the Private Use Area of Unicode (see: 
http://en.wikipedia.org/wiki/ConScript_Unicode_Registry).

It would be a bad idea to support this encoding in Noto for several reasons:
- it might conflict with other uses of the PUA;
- should Klingon later be accepted into Unicode proper, issues would arise with 
legacy support of the PUA encoding;
- this would actually lessen the chances that Klingon would later be accepted 
into Unicode, since most of what users want to do with it would already be 
possible with the PUA encoding.

p.s. This is sort of tangential to the main issue, but what the Bing Klingon 
translator produces is not actually correct Klingon in most cases (the 
exceptions being relatively simple sentences and some phrases which have 
appeared in Star Trek shows or publications). If all you want is something that 
looks alien and vaguely resembles Klingon to people who don't know the 
language, then it's sufficient. Otherwise, you might want to get someone who 
actually knows the language to do the translation for you.

Original comment by davi...@google.com on 29 Aug 2014 at 9:11

[GoogleCodeExporter]

Issue 189 has been merged into this issue.

Original comment by roozbeh@google.com on 31 Oct 2014 at 5:37

[GoogleCodeExporter]

Original comment by roozbeh@google.com on 16 Jan 2015 at 6:09

[GoogleCodeExporter]

As has been pointed out above - once Klingon has been encoded into Unicode we 
will consider it.

I direct you to: http://www.unicode.org/contacts.html

Original comment by stua...@google.com on 28 Feb 2015 at 12:19

• Changed state: WontFix