Talk:Binary-to-text encoding: Difference between revisions

Content deleted Content added
 
(13 intermediate revisions by 9 users not shown)
Line 1:
{{WikiProject Computer sciencebanner shell|class=C |importance=Low}}
{{WikiProject Computer science |importance=Low}}
 
}}
== A few extras to consider ==
{{Broken anchors|links=
 
* <nowiki>[[List of numeral systems#By type of notations|listed by notation type]]</nowiki>
* [http://www.fourmilab.ch/codegroup/ "Five-Letter Codegroup Filter"]: uses only upper case ASCII letters and spaces; includes a CRC. --[[User:DavidCary|DavidCary]] ([[User talk:DavidCary|talk]]) 08:28, 19 February 2021 (UTC)
}}
* [[Variable-length quantity|VLQ]]
* [[LEB128]]
* basE91
* [https://rfc.zeromq.org/spec:32/Z85/ Z85] diff charset from Ascii85
 
== ASCII85 implementation in JavaScript ==
 
I wanted to add link to my "just written" implementation, however got a warning about conflict of interests.
If anyone other will think that this information will be helpfull feel free to add [https://github.com/nE0sIghT/ascii85.js this link] to Article. [[User:NE0sIghT|NE0sIghT]] ([[User talk:NE0sIghT|talk]]) 21:24, 27 February 2018 (UTC)
 
==basE91==
Line 53 ⟶ 45:
 
:Indeed. Potentially interesting for student programmers, but in my opinion too trivial to classify as knowledge. --[[user:bdijkstra|bdijkstra]] ([[user talk:bdijkstra|talk]]) 18:16, 2 July 2020 (UTC)
::I'm for removing that column as well, unless you find all existing public implementations for all languages out there...--[[Special:Contributions/2A02:8070:6394:7A00:1920:6758:18DA:1DF9|2A02:8070:6394:7A00:1920:6758:18DA:1DF9]] ([[User talk:2A02:8070:6394:7A00:1920:6758:18DA:1DF9|talk]]) 18:41, 29 December 2021 (UTC)
 
== Identifying the encoding used ==
Line 76 ⟶ 69:
 
* I added a point of clarification. I think you are thinking about one specific subset of what binary-to-text encodings are used for. While it is true that ASCII is not commonly used to represent arbitrary Binary data, Binary-encoded ASCII is still the most common data format there is. To address your claim "cannot represent half of all possible octets" that's entirely false. Any binary sequence can be represented in ASCII. It does take 2 characters to represent one octet, it only takes 8 ASCII characters to hold 7 octets. So the efficiency is 7/8 = 87.5%. [[User:Alanbly|Adam McCormick]] ([[User talk:Alanbly|talk]]) 00:43, 18 November 2021 (UTC)
::ASCII is ASCII, a 7 bit encoding. '''All''' the schemes listed in the article are forms of encoding binary data as ascii. Whereas if you allow control characters you could bit-shift 7 octets of 8-bit binary data into 8 octets of 127-bit ascii data this would ony be 7/8% efficient for multiples of 567 bytes and is certainly not commonly used. -- [[User:Q Chris|Q Chris]] ([[User talk:Q Chris|talk]]) 11:09, 18 November 2021 (UTC)
 
== Missing encodings ==
 
Is this article missing any other notable encodings, whether ‘modern’ or historic?
 
=== Examples ===
For example, I’ve never heard of these being used in this context, but they seem like they plausibility could ''(or do)'' exist:
 
{{bulleted list
| [[Base10]] - e.g. inputting binary data into a 10-key numerical keypad ''(an anonymous user commented on the general topic of Base10 encodings here under the heading '''[[#Decimal (base10)|Decimal (base10)]]''')''
| [[Base12]] - e.g. inputting binary data into a 12-key telephone keypad ''(0-9, plus '*' and '#')'' or transmitting it ''(yes, less efficiently than [[Base16]])'' by sending [[Dual-tone multi-frequency signaling|DTMF]] tones through an audio channel ''(including from speaker to microphone)''
}}
 
What about [[Telex]]-like systems (and their modern descendants)?
 
=== Already mentioned by others ===
[[Base 26]] ''(hexavigesimal)'' was mentioned above* but never appears to be re-added. Does anyone use this for encoding binary, or is it mostly used for representing integers ''(as done by Amazon for ASINs)'' in a more concise form ''(the opposite aim compared to the encodings in this article; it has an integer-to-text efficiency of greater than 100% - [[Binary-coded decimal|BCD]], an integer-to-binary encoding, is a better analogue, as the encoded version of BCD is less efficient than the original)''?
 
''*The last edit by [[User:Eyreland|Eyreland]] prior to reversion and that above discussion, ([https://en.m.wikipedia.org/w/index.php?title=Binary-to-text_encoding&oldid=572560755 21:18, September 11, 2013]), never appears to have been restored. (Unfortunately, I don’t have time to research that further at the moment.)''
 
[[User:DavidCary|DavidCary]] mentioned several others here under the heading ''[[#A few extras to consider|A few extras to consider]]'' in early 2021.
 
[[User:起司狗|𝒞𝒽ℯℯ𝓈ℯ𝒹ℴℊ (起司狗)]] mentioned the [[PGP word list]], which seems like it could qualify for inclusion.
----
 
=== Some of these things are not like the others ===
Certain encodings and formats, while perhaps having some similar characteristics to those already included in the article, don’t belong here and should be listed/classified elsewhere.
 
This article’s title seems to '''really mean''' “binary [[Syllable (computing)|syllable]]-to-text encoding” or “byte-to-text encoding”, where the syllable/byte size is commonly 8 bits ''(but not always; [[Ascii85|Ascii85/Base85]] uses a 32-bit [[Big-endian|BE]] grouping of four 8-bit bytes, for example, which could be seen as encoding a syllable/byte size of 32 bits)''
 
{{bulleted list
| Most [[Category:Character encoding|character encodings]] [[Character encoding|character and terminal encodings]]
| Some [[Data compression|data compression]] standards
| [[Geocode]] systems
}}
 
A larger category of ‘data-to-text encodings’ might include some of those that don’t fit into the scope or this article.
 
[[User:Jim Grisham|Jim Grisham]] ([[User talk:Jim Grisham|talk]]) 00:08, 17 June 2022 (UTC)
 
== YEnc ==
 
https://en.m.wikipedia.org/wiki/YEnc should be added to the table [[Special:Contributions/69.17.160.164|69.17.160.164]] ([[User talk:69.17.160.164|talk]]) 15:40, 10 July 2024 (UTC)
 
== Number of printable ASCII-characters ==
 
In the '''Overview''' section, the number of ''printable ASCII characters'' is specified as 94. However in the linked article ([[ASCII#Printable character table|ASCII#Printable character table]]) the number of ''printable ASCII characters'' is specified as 95. The difference is likely due to omitting the ''space'' character, being the only printable character that has no visual representation. This discrepancy should be addressed to avoid confusion arisen by the difference of these two numbers. [[User:Arutawa|Arutawa]] ([[User talk:Arutawa|talk]]) 09:43, 9 April 2025 (UTC)
 
== Uh - No Issues Here ==
 
Yeah - when I saw the page there was a banner at the top. and it said something like "''this page has issues''"
 
'''NO IT DON'T'''
 
''I learned about data. More specifically I came to the page to find information about BIP54 encryption with Solana Blockchain. What I discovered on this page was mind expanding. I now understand communication with binary data - which our (human) entire computer systems use''
 
Not only can it be both (light is particle and wave) but also something else.‹› [[Special:Contributions/50.75.15.186|50.75.15.186]] ([[User talk:50.75.15.186|talk]]) 21:57, 11 May 2025 (UTC)