A new Curl logo
daniel.haxx.se
daniel.haxx.se
In my head, I say "curl" as in curly hair. It's really "see-url"!? I think it's too late for my brain to correct that.
"We pronounce curl and cURL with an initial k sound: [kurl]."
They do, however, note that the "fact it can also be pronounced 'see URL' also helped" [to choose the name].
See you are ell.
Same problem with SQL. Is it "ess que ell" or "sequel"?
It's unconventional pronunciations of less common initialisms that cause problems.
SQL -> "sequel", how could we know?
Stunned into silence.
Edit: Changed 'sue-do' to 'sue-doo' to make it less ambiguous.
Those are both pronounced the same way.
The prior is pronounced /ˈso͞odō/
The latter is pronounced /so͞odu/
Speaking about sudo, learned that before living in an English speaking country, so everybody pronounced rhyming with su-go (say) not su-do and I still pronounce it that way (which I guess it's wrong!)
ah, the joys of learning English as a written language first, even now after living in North America for nearly 20 years occasionally I find words I completely mispronounce due to having learned them from books
Too pool -or- Tup ulll -or- Tup lee
So many choice from just five letters....
"Tup Lee" just seems silly.
(It's historically rhymed with couple)
On the other hand, a lot of Latin-originating words have had their pronunciations changed in US English, the canonical example being data (from UK English "da-ta" to US English "day-ta", which has now begun to become standard everywhere due to the tech industry) so I guess other words could go the same way.
So it's true! It is pronounced with a short initial syllable. I've always pronounced it along the lines of toople.
> One of the hardest things about LaTeX is deciding how to pronounce it.This is also one of the few things I'm not going to tell you about LaTeX, since pronunciation is best determined by usage, not fiat. TeX is usually pronounced teck, making lah-teck, and lay-teck the logical choices; but language is not always logical, so lay-tecks is also possible.
See also http://tex.stackexchange.com/questions/17502/what-is-the-cor...
> Insiders pronounce the χ of TeX as a Greek chi, not as an ‘x’, so that TeX rhymes with the word blecchhh. It’s the ‘ch’ sound in Scottish words like loch or German words like ach; it’s a Spanish ‘j’ and a Russian ‘kh’. When you say it correctly to your computer, the terminal may become slightly moist.
Surely, we should be insiders.
Source: https://changelog.com/201/
'char' : as in charcoal
'car' : pronounced like a car, used as (car (cons 'a 'b))
'cdr' : supposed to be 'could-er', but I flip between cee-derr and could-er
'cadaddr' : prounounced 'why'
I kid a little, but it's funny to hear these things, especially when it's from somebody from a foreign country. It wasn't until grad school that I realized there's so many different ways to pronounce keywords.
But I also pronounce "enum" like "ee num", not "ee noom", so there is apparently no overarching theme.
However, the association for me is very much to PCB design since the lines with hollow circles look like tracks with vias or just pads for through-hole components. See, for instance, the background on KiCad's (an actual PCB design program) site: http://kicad-pcb.org/.
This "inspiration" was visible in the first suggestion too, the one with the c-as-symbol also makes the c look like circuit board tracks. Strange.
According to RFC3986, URIs (the proper name; URLs are a kind of URI) are correctly of the form:
<scheme>:<scheme-specific-part>
For some schemes, the <scheme-specific-part> may contain a <hierarchical-part>, the format for which is: //<authority>[/<path>] | <path>
So it's only hierarchical URIs with a defined authority that have the (admittedly iconic) "://" in them.I know most people identity URIs as having that sequence in them, but these are all valid URIs:
mailto:bob@example.com
sip:bob@example.com
tel:+18005550123
file:/path/to/file
I'm not saying I expect everyone to understand these subtleties, but people who claim to grok URLs ought to.No, it supports mainly schemes with a hierarchical-part - even though it works with 'file:'
For a logo there's absolutely no problem in using an element that's common and pretty identifiable
https://webcache.googleusercontent.com/search?q=cache:hGPFWP...
I have never seen file:/ used before, so I can't really comment, but it seems invalid to me (and browsers auto-redirect it to ///).
The file: signifies the protocol. The /// is actually //<machinename>/ with an empty machinename as a shorthand for 'localhost'.
Why is this interpreted as a relative path?
cd /etc
curl file://resolv.conf"I also suggested we’d try to work with :// (colon slash slash) somehow as a symbol, since after all the :// letter sequence is commonly used in all the URL formats that curl supports. And it is sort of a global symbol for URLs when you start to think about it. Made sense to me."
They seem to grok it perfectly well, but recognize the modern association people have with :// and urls.
The logo for the accepted version is the best of the 3, in my opinion. However, when looking at it combined with the logotext it looks kind of odd in that the slashes are leaning away from the word curl so prominently. (#2 doesn't have this problem). No matter, though, it is a big improvement.
http://archive.li/TRDMX/c9b30e15b66869f9d7c9f825e9771b3b9828...
the important part of the name is URL after all. Logos are always tricky though; everyone wants to have input, which means you often end up with things like the last logo with lots of ideas mushed together.
In type design, curves and points will usually extend out further then straight square edges to stop them looking like they have stopped just short.
If you blow up some text large and draw a line on the baseline between an 'x' and rounded character like an 'o', the o will go slightly beyond the line. If it didn't, it would look too small to the eye. This is what you would call 'optically correct'. (Its the same for typefaces with pointy 'w's and stuff)
The stem of the bottom of the 'r' in the logo is rounded, so that could make the straight edge of the 'l' look out of place to the human eye, even though that when you draw a line, they line up.
https://daniel.haxx.se/docs/curl-vs-wget.html
Which is a pretty good summary of the similarities and differences, and it makes me want to try curl a bit more than I have in the past, especially the support for scp and cifs.
I don't like the new or old logo.
We detached this comment from https://news.ycombinator.com/item?id=11785541 and marked it off-topic.