Talk:Private Use Areas

Page contents not supported in other languages.
Source: Wikipedia, the free encyclopedia.

Discussion from a Redirects for Discussion entry

From

WP:RfD
:


Characters

Since all instances of this character in the document appear for me (on a Mac) as the Apple logo, it makes sense to me to have rasterized images of each version of the character. Since the character can represent a corporate logo, this raises the question of if a representation of the corresponding Unicode character constitutes fair use. --IntrigueBlue 09:25, 9 May 2006 (UTC)[reply]

I'm seeing the same thing... How would you go about doing this? PaulC/T+ 02:04, 11 May 2006 (UTC)[reply]
Based on further research, it would appear that the Apple logo was originally included in fonts as a copyright method, because people would not be able to redistribute the font since it contains a trademarked logo. By extension I would assume including depiction of the logo here would not constitute fair use, which kinda throws a spanner in the works. As for the other symbols mentioned, since I can't see them I can't make pictures of them either. Could somebody who can see them do this, and add the pic to the article? --IntrigueBlue 05:14, 12 May 2006 (UTC)[reply]
I'm in Windows XP presently and just see ?, in linux I see €. Thryduulf 09:58, 12 May 2006 (UTC)[reply]

I see little hollow boxes for everything except Wingdings and Webdings, where I see glyphs different from those described... AnonMoos 23:29, 25 October 2006 (UTC)[reply]

For me everything is displaying as the insignia of the Klingon Empire. --PiMaster3 talk 21:49, 2 December 2006 (UTC)[reply]
What OS/browser are you using? Could you upload a high-resolution rasterized/SVG version of the insignia? I've been trying to find a browser that displays that way. —INTRIGUEBLUE (talk|contribs) 22:06, 2 December 2006 (UTC)[reply]
I'm using Firefox 2.0 on Windows XP. The only font that I think might be causing this would be code2000. --PiMaster3 talk 01:47, 4 December 2006 (UTC)[reply]
Okay, I'll check that out next time I boot to Windows. —INTRIGUEBLUE (talk|contribs) 02:36, 4 December 2006 (UTC)[reply]

I'm seeing it the way IntrigueBlue described it, as all apple logo's. something should be done, but i don't know how. Jordan042 21:31, 15 June 2007 (UTC)[reply]

https://en.wikipedia.org/wiki/User%3APsantora 2607:DA80:3:995:C908:70E7:AF64:524A (talk) 07:59, 2 June 2021 (UTC)[reply]

Uploads for different fonts

Currently, all I see on this page is this glyph: Apple over and over again. It would be great if someone could upload the other glyphs in a similar format and insert them into the article so that others can see the correct image. I'll add the Apple logo where appropriate. PaulC/T+ 21:55, 14 January 2007 (UTC)[reply]

See the discussion above your post. What it boils down to is that the Apple logo was added as a form of copy protection, and the image you linked is listed under fair use. Use in this article would appear not to fall under blanket fair use. —INTRIGUEBLUE (talk|contribs) 01:24, 15 January 2007 (UTC)[reply]
Fair enough. Still, it would be nice if the other glyphs could be imaged and added to the article..PaulC/T+ 09:35, 15 January 2007 (UTC)[reply]
I find it useless having the same symbol apear exactly the same again & again Tuck99 08:27, 7 March 2007 (UTC)[reply]
Yeah, this article should basically be deleted if it doesn't make sense depending on what computer one is on. Clearly, the windows logo is not an Apple symbol.72.78.57.6 22:47, 3 October 2007 (UTC)[reply]
It's a trademark. You can't extend copyright with a trademark. Fair use still applies. The trademark issue is separate. Pictures of trademarked items are also fine, the key question being if the use of the trademarked image could cause market confusion. That is, could an image of the Apple logo on Wikipedia cause some fool to believe that Wikipedia is an Apple product? Since the law is not based on the theoretical maximum fool, the answer is no. Usage here is fine, no problem. Replacing the Wikipedia puzzle-globe logo with an Apple logo would of course be another matter entirely. 24.110.145.106 (talk) 06:21, 29 January 2008 (UTC)[reply]

Wingdings and Webdings

Wingdings and Webdings are symbol fonts that are not mapped to Unicode system, so there is nothing at the codepoint. You can check it out with BabelMap for example. --Octra Bond (talk) 10:00, 6 September 2010 (UTC)[reply]

Requested move

The following discussion is an archived discussion of the proposal. Please do not modify it. Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section.

The result of the proposal was no consensus. --BDD (talk) 20:36, 25 March 2014 (UTC)[reply]

WP:PLURAL. --Relisted. Xoloz (talk) 01:14, 14 March 2014 (UTC) DePiep (talk) 07:51, 5 March 2014 (UTC)[reply
]

It's more simple. Three PUA's is a list of PUA's, not a system of PUAs. -DePiep (talk) 16:46, 18 March 2014 (UTC)[reply]
  • Oppose. "Private Use Area" in the singular is used to refer to the BMP PUA - the term was coined prior to the creation of the supplementary planes - and it contrasts with the "Private Use Planes". The term "Private Use Areas", in the plural, is the exclusive term that refers to all three, collectively. Also, in answer to NSU, there in fact will not be any more private use areas in the future, as per Unicode stability policy. In other words, moving this page would be factually incorrect. VanIsaacWScont 15:47, 17 March 2014 (UTC)[reply]
No. PUA also refers to another PUA, not just the one BMP block. Simply, there are three blocks Private Use Areas (they are a Private Use Area, by definition), one of them is actually named 'Private Use Area'. Unicode Chapter 16.5 Three distinct blocks of private-use characters are provided in the Unicode Standard: the primary Private Use Area (PUA) in the BMP and two supplementary Private Use Areas in the supplemental planes. The language and the definition does not force us to use plural as a concept. The three are not a system of PUAs, they are just a list. None of the exceptions mentioned in
WP:PLURAL apply. Note that this is a policy, not opinion. -DePiep (talk) 09:35, 18 March 2014 (UTC)[reply
]
The above discussion is preserved as an archive of the proposal. Please do not modify it. Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.

Requested move 23 March 2015

The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review. No further edits should be made to this section.

The result of the move request was: NO CONSENSUS. Hadal (talk) 06:09, 25 April 2015 (UTC)[reply]



WP:TITLE. DePiep (talk) 00:24, 23 March 2015 (UTC)[reply
]


The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page or in a move review. No further edits should be made to this section.

Other uses in text parsing algorithms

See this discussion: when parsing text (eg. XML) is interesting to reduce complexity replacing tokens or tags by 1-character token, so, generates a simple text with usual characters and non-ambiguous tokens-as-characters. This simple string can be parser by usual regular-expressions instead complex

parser
.

Summarizing: the "other use" is "as reliable Unicode 1-character-token in parsing context".

Example: XML representation of multilingual text as

  <section class="main"><p>Hello, any character as 𩸽.</p><p>Bye!</p></section>

Now, we can reduce tagged representation to "text and token" representation, remembering the sequence of tags (eg. in an array). Let's see replacing XML-tags by "_T1_", "_T2_", etc. tokens, the text will be
_T1__T2_Hello, any character as 𩸽._T3__T4_Bye!_T5__T6
... But to process the tokenized text by a regular expression the less complex is to reduce tokens to 1-character... To avoid conflict with "real text" exoctic characters (like "𩸽"), we adopt PUA as the best choice, that never conflics.

Supposing the adoption of PUA codes 61528 (decimal) and 61527, that are the UTF-8 characters "" and "". Now we can represent the XML text with the tokenized text and arrays (suppose JSON representation), and process its content by a simple regular expression.

{
  "content":"Hello, any character as 𩸽.Bye!",
  "open_tags":["section","p","p"],
  "attributes":[{"class":"main"},null,null],
  "close_tags":["p","p","section"],
}

Krauss (talk) 20:44, 1 February 2018 (UTC)[reply]

"U+f8ff" listed at Redirects for discussion

An editor has asked for a discussion to address the redirect U+f8ff. Please participate in the redirect discussion if you wish to do so. 1234qwer1234qwer4 (talk) 13:40, 5 April 2020 (UTC)[reply]

"􍁷" listed at Redirects for discussion

An editor has asked for a discussion to address the redirect 􍁷. Please participate in the redirect discussion if you wish to do so. 1234qwer1234qwer4 (talk) 16:29, 5 April 2020 (UTC)[reply]

"􏰉" listed at Redirects for discussion

An editor has asked for a discussion to address the redirect 􏰉. Please participate in the redirect discussion if you wish to do so. 1234qwer1234qwer4 (talk) 16:29, 5 April 2020 (UTC)[reply]

"" listed at Redirects for discussion

An editor has asked for a discussion to address the redirect

. Please participate in the redirect discussion if you wish to do so. –LaundryPizza03 (d) 07:25, 13 April 2020 (UTC)[reply
]

Former status of surrogate zone

As of Unicode 1.0.1, in the now-antiquated system of dividing the Basic Multilingual Plane into "zones", U+D800..U+DFFF were part of the O-zone, not the R-zone (which included the private use range U+E000..U+F8FF): [1]. This was prior to U+D800..U+DFFF becoming the surrogate S-zone. So U+D800..U+DFFF seems to have been reserved space, not private use space. --HarJIT (talk) 19:51, 11 October 2021 (UTC)[reply]

I think I see where the confusion may have arisen, since the Unicode 1.0.0 PUA ended later, at U+FDFF (but also started later, at U+E800): [2] --HarJIT (talk) 19:53, 11 October 2021 (UTC)[reply]