No it isn't:
> 10:48:55.380 document.location.href
> 10:48:55.384 "https://news.ycombinator.com/item?id=26166797"
> 10:48:57.723 document.characterSet
> 10:48:57.726 "UTF-8"
Plenty of non-ASCII symbols show up perfectly fine. For example, '£'.
xmlns:v="https://vecta.io/nano"
serves any purpose besides advertising.You can't translate the Wikipedia quote in the article into an SVG except by just rendering the bare text.
Checking programmatically that text is about "bird" or "Twitter" is very easy. Checking that an SVG is about "bird" or "Twitter" is very hard.
It's not even efficient. It conveys the same message as the word "Twitter" in a hundred times the size. And it wouldn't be less efficient if it were a binary format.
It's maybe more suitable for carving into granite than a binary format, but you'd be better off carving the logo itself.
That depends on what you want:
If you know what twitter is, then yes, just saying "twitter" is more efficient than a whole SVG file describing the twitter logo.
But if you don't know what twitter is, nor what its logo looks like, SVG is a very efficient way to describe the logo exactly. If you can have it rendered to your screen that's optimal, but if not, you can take it as instructions to redraw the logo yourself and still get an accurate impression of what the twitter logo looks like.
I that sense, "twitter" and the SVG of the twitter logo are both text, but they don't have the same meaning.
As for the granite, it is indeed one situation where just drawing the plain SVG logo is more effective, but SVG would still be viable. Over telephone, on the other hand, you just can't transmit an image. You can only attempt to describe it, and the more detailed you get with that, the closer you come to just using a code very similar to SVG.
Could you kindly verify that by repeating your post using something other than what amounts to a text file?
If not maybe that's an even truer seal of irony.
Could you kindly present me your comment without using all these inferior non-text technologies involved on my side to read it off my screen? That's the irony, if anything.
That's a bit short-minded, don't you think? Or is this some kind of troll meme at this point? Anyway, I don't expect you to have some off-spec working TLS/TCP/IP/ARP/ETH implementation purely based on text, yet alone are connected to the internet via some text-only telegraphy station utilizing those things. Pretty sure your output device (read as: screen) has some sort of analog/digital signaling as well that's not ASCII encoded. There are sure some pesky non-text technologies involved ...
Edit: upon some rereading, I get that there was maybe more sarcasm in gp comment than I perceived at the time.
And they still reach places having no other form of comunication.
If it was not a post card, you would need to open the envelope please.
If you would like to read that kind of text off your screen, you might just need to scan it yourself or find someone who can.
Obviously you need ways to display text in the physical world, be it a screen or a piece of handwritten paper. It's still text.
> Obviously you need ways to display text in the physical world, be it a screen or a piece of handwritten paper. It's still text.
And what about transfer? People keep claiming text is superior for transferring information, yet the majority my network stack or anything involved with the transport isn't text based.
The premise of the whole "text is the best technology" argument is based on cherry picking and strawman arguments anyway.
I agree with that so naturally cherry-pick the thing expected to be the most universal and the last one standing.
Aren't everyone else's network stack usually sending packets of text when it's a plain text file? Even if it is hypertext.
The article was written in 2014. Worth remembering when nitpicking the text of an article.
Text is that it's highly compressible while also being highly compressed (and lossy) info already. To make text we have to filter our own ideas, and then to interpret text we have to add a bunch of info back from context.
Pictures have the same tricks up their sleeve. Bitmaps are great but inefficient. If we put it through a lossy compression, it's a lot better. If we make it semi procedurally with a vector file, it's even better. How far can we take a compressed procedural file though? Well.. .kkreiger was about 97 KB, and stores a full 3d shooter. For a meg, you could store 100 such full games. https://en.wikipedia.org/wiki/.kkrieger
Text isn't best in every way. With clever design we can use all the same principles that make text efficient, and make other types of data more efficient. It is a very good default though.
If SVG counts as text, then text is just binary. The encoding is not important, the final result (an image you see on a screen, in the case of SVG) is.
Besides, try reading out the actual SVG source text to someone and see if they can tell you what the image you are describing is. I dunno about you, but I find thinking in terms of paths and strokes to be rather meaningless.
Or another example, do you consider Wavefront .obj files text? They're ascii files, but I don't consider a series of "v 0.123 0.234 0.345 1.0" as something I would ever read in text form and have even the slightest idea of what the final 3D model actually is. I have to view it visually. Its "technically" text, but its no more useful as text (for a human text reader) than if it were binary data. Encoding isn't what makes text what it is, so non-text things encoded as text aren't really text.
Of course, to extract meaning from this text (what is it?) requires drawing it. But you don't have to, you can just name it. You could just say "I'm sending you the stylised image of a blue bird, with the instructions on how to draw it using the SVG text standard". Or just, more clearly even, the following string of characters: "twitter_logo.svg"
No. A path tag with a 500-600 element `d` attribute is not human readable. It is not human understandable or parsable until it's converted into a visual format.
Ask a blind person whether they think SVG charts are accessible on their own without any additional markup or alternate explanations or controls. Ask them if they can read SVG line charts by stepping through the path property. Figuring out how to communicate complicated graphs/charts with lots of data without relying on any visual medium is a complicated problem that we are still trying to solve.
> You could just say "I'm sending you the stylised image of a blue bird, with the instructions on how to draw it using the SVG text standard". Or just, more clearly even, the following string of characters: "twitter_logo.svg"
By that logic, a PNG is also text, because I can do the same thing. All images can have alt tags. Even Javascript Canvas can have fallback text for when it doesn't render. My Twitter png can be transmitted as "twitter_logo.png".
What do people mean when they say text is preferable if not that the textual representation is more useful than the image representation? If you didn't feel like the SVG format was adding any useful information in its rendered form, you wouldn't waste the time sending information to render it. You would just send the alt text.
> I can read it to someone over the phone with a pen and graph paper, and he can draw it exactly like it should be represented, with zero loss of quality
Right, and when that person draws it, they will have converted it from a textual format into a visual one. I can send you the individual pixels of a small raster image over the wire in a textual format and you can sit down on a piece of grid paper and ink in squares until you come up with the final image. At which point you will no longer be looking at a piece of text.
To argue that the fact that we can encode a format over a UTF-8 stream or physically replicate your computer's drawing algorithm makes a thing text seems to me to be a misreading of the original article's point. The original article is not complimentary of Twitter's SVG, it explicitly brings it up as an example of a non-text medium.
If you expand the definition of text to include basically any storeable information that can be theoretically encoded into UTF-8, then sure, I would agree that text in that system is tremendously powerful. But that's not a useful category to talk about, it's so broad that it becomes meaningless.
That doesn't make it human-readable. I challenge you to tell me what (even the basic shape) this SVG is without loading it in a viewer (taken from a real SVG, not something handcrafted to prove you wrong, but the first thing I found online while searching for public domain SVG files):
https://gist.github.com/danielytics/90446a2314c1ad87017233eb...
Good luck figuring out what that is, even with graph paper. And that's a single layer, single (even if a bit complex) shape, single colour SVG. They only get more incomprehensible from here.
Is human comprehensibility a pre-requisive to be called text? What if there was a written language no one understood, would that be text? What if someone broke the code for it? Would it suddenly become text?
Not all SVG authoring tools make SVG's easy to read/modify. Tools in the 90's used to the same thing with HTML. Are you going to argue HTML isn't text?
Go to google.com and view source. That's text, right?
lol, brb, PFA, W.H.O., IMHO, IANAL, GPA, GTA.. word soup for a different audience..
Actually I thought about talking about SVG, which would be the natural result of taking a text representation of shapes ... and then use abbreviations until you are at some expert level language (SVG for example), which would then break the argument again. You might as well use some binary representation then, because most people don't speak fluent SVG.
Also, you'd be surprised by the amount of people that write SVG by hand, which I doubt you'll see with PNG anytime soon.
Outside of bugs, I was under the impression that SVG was actually pretty well specified and that (except perhaps for pathological examples created intentionally) the rendering of an SVG was quite consistent.
What am I not aware of?
"Twitter"
carries the same weight
,~
('v)__
(/ (``/
\__>' hjw
^^
Twitter
Bird kindly borrowed from: https://www.asciiart.eu/animals/birds-landIf you treat a uniwidth character grid of characters as pixels, you have not converted an image into text, you have encoded text into an image. It's no different than using extended characters and font colors in a fixed width terminal window to make terminal art.
The fact that you use UTF-8 to encode something does not mean it will magically work in a screen reader, or that it will retain any of the advantages of pure text. I can encode any image or video file in a UTF-8 format and send it to you. Down this path lies calling everything text.
But if your "text" stops being readable if I disable monospace, or it stops working if I change the font, or it stops working if I change line wrapping, or it stops being communicable as soon as I try to read it out loud -- then it's not pure text. Using a UTF-8 character as a pixel does not change the fact that you're drawing an image out of pixels.
> text is the most powerful, useful, effective communication technology ever, period.
Nothing of this is actually true, period.
> I do not post to this blog with the intention of entertaining Hacker News Debate Club and I frequently disable comments or friend-lock posts in order to avoid this sort of nonsense. I'm not interested in further discussion.
Ah yes, the true seal of quality. (sarcasm)