So Trump can support war criminals like Netanyahu, but when someone says Israel shouldn't colonize Palestine and practice appartheid, she becomes a mouthpiece of Hamas? Get your facts together.
This code seems to be aimed at pirates selling access to Jellyfin instances. It allows them to restream video feeds through Jellyfin with a control plane over a Discord bot.
Debian stable repositories currently serve version 4.13.13.
Multiple security releases have been issued by samba since then: from 4.13.14 to the recent 4.13.17 which fixes CVE-2021-44142 [1].
It seems the current maintainer does not have any more time to work on the package [2].
My previous position was sold to me as requiring lots of low-level skills and I was actually doing only few trivial tasks each week. I left this job after almost two years and have virtually done nothing ever since. Boreout created very hard to get around mechanisms in my brain.
They don’t say “Gnuplot” is wrong. They even include themselves (“many of us”) in those people that don’t want to start sentences and title words with lower case. My reading of that paragraph is that while “GNUplot” is definitely incorrect, “Gnuplot” may naturally occur due to capitalization, just like with any lower-case noun.
gnuplot is a command-driven plotting program. It can be used interactively to plot functions and data points in both two- and three-dimensional plots in many different styles and many different output formats. Gnuplot can also be used as a scripting language to automate generation of plots. It is designed primarily for the visual display of scientific data. gnuplot is copyrighted, but freely distributable; you don’t have to pay for it. You are welcome to download the source code.”
If it’s lowercase in title font, it should be lowercase everywhere.
> If it’s lowercase in title font, it should be lowercase everywhere.
If you read closely, you’ll notice that only “x” level headings use title case, “x.y” level headings use sentence case; there is no clear instance of “gnuplot”, capitalized or not, in title case anywhere in the document. The only arguable case is the page header “gnuplot FAQ”, but since it is sui generis there is no way other than inferring from capitalization in the rest of the document of telling whether its titlecase or just the preferred labelling of the product followed by “FAQ” (and the context suggests the latter).
You see people use "Gnuplot" quite a bit because many of us have an aversion to starting a sentence with a lower case letter, even in the case of proper nouns and titles. gnuplot is not […]
Most of us don’t care about forcing the first letter to be always lowercase, and in fact feel it’s a lost cause. But I agree that after such an explicit clarification I would expect to see “gnuplot” everywhere in the official documentation, except for this particular excerpt and when they refer to “GNUplot”. Otherwise it is clearly inconsistent with what they are explaining.
Yes, I also read the body text after the numbered heading in the prior excerpt, which makes two different choices in sentence-starting position in sentence case. But what I was responding to was the inference of a rule bases on usage in “title font” (which seems to be a reference to title case), not a complaint about the inconsistent use in sentence case. Hence, the except you provide here isn't really germane to anything I've said.
> If it’s lowercase in title font, it should be lowercase everywhere.
The section titles are in sentence case, not title case. You would not expect it to be capitalised unless it were the first word of the title. The inconsistency in that paragraph is in the first sentence.
Because it's the correct way to spell it. Names are spelled with an uppercase letter in the beginning and all the other letters are lowercase. "I saw John" vs. "I saw john" vs. "I saw JOHN". First one is correct. Even if John tells you "My name is spelled with a lower case j". Or if John writes: "this orange thing is a kaRROT", it's still a carrot.
You can write whatever you want. You can also write "Tis is me bunni and he likes KArRoTs" and have a lot of friends agree with you that's the correct spelling. And it is still generally considered wrong :)
There are many names that do not follow your rule, and generally speaking I'd find it very rude if I told you my name, and you'd go "let me fix that to the _correct_ spelling". For example a name as Angus MacGyver, or Armand de la Cour. Both don't follow your rule. I don't see why that wouldn't apply to brand names as well.
Wikipedia often rejects corporate case styling and uses the sane "first letter upper case, others lowercase" for some brands. For example Wikipedia writes Nvidia instead of NVIDIA, although the company always capitalizes its name without exception.
No, Wikipedia does not make the judgement call on whether to "reject" corporate case styling on its own, it follows what is "in widespread use":
> Follow standard English text formatting and capitalization practices, even if the trademark owner considers nonstandard formatting "official", as long as this is a style already in widespread use, rather than inventing a new one: (But see exception below under § Trademarks that begin with a lowercase letter.)
> use: Time, Kiss, Asus, Sony Mobile. (Capitalize IKEA, IBM, as acronyms/initialisms.)
One thing that entry does not cover is all lower-case names. Although a couple things I looked up (gnuplot, xkcd), Wikipedia does seen to respect all lower-case. I'm not sure how many companies actually have all lower-case names--even if their logo is all lower-case. And my observation is that even many projects that are nominally lower-case, aren't very consistent about it as in the current example.
> Follow standard English text formatting and capitalization practices, even if the trademark owner considers nonstandard formatting "official", as long as this is a style already in widespread use, rather than inventing a new one: (But see exception below under § Trademarks that begin with a lowercase letter.)
> use: Time, Kiss, Asus, Sony Mobile. (Capitalize IKEA, IBM, as acronyms/initialisms.)
Not sure. There's GNU after all. Wikipedia's "arbitrary" standard is actually pretty common in my experience. But I'm not sure I could come up with a coherent explanation as to why.
GNU is an acronym, that's fine. But if they insist on Nvidia, they should also insist on Xkcd (it's not an acronym, just an unpronounceable artificial word).
And radar is an acronym too and it's not commonly capitalized although SCSI is. And, often, Fortran, not FORTRAN. I'm not making a case for how things should be. I'm just observing how they commonly are in style guides, etc.
I think part of it is a general stylistic distaste for having "unnecessary" caps. See also general shift away from "Open Source," "Big Data," and the like.
Do people actually write eBay? It looks as dated as eMail.
iPhone is definitely an example of marketing winning over grammar, but it's not a given. Plenty of style guides indicate "our company name is to be written in all caps", when they want to stand out, which the rest of us happily ignore.
In my experience, publications and the like do tend to respect the capitalization and other choices of a company/project/etc. with perhaps some exceptions like the ! in Yahoo! and perhaps all caps as in NVIDIA. In the case of Wikipedia, I'd go so far as to say that they're simply wrong if they're ignoring the actual way a company name is officially styled.
Mind you, I'm not necessarily a big fan of case-sensitive everything but here we are.
I can mostly agree with people's names, especially stuff like cultural variations or things that are basically name prepositions like de/Mac/o etc. That said if you decided to change your name to "JOHN SMITH" don't be surprised if that decision was less respected and you were referred to as "John Smith" following capitalisation norms.
Companies don't get even that assumption for me, sure I'll use "iPhone" because they've won that one and it's the cultural expectation, but the only time I'm using "FREE NOW" is to criticise that decision
Maybe. Probably. But in practice no one really cares other than editors and pedants. I'd probably only bother if I was showcasing something to people from that particular entity.
People are perfectly free to spell their names however they want. Good luck to them in getting everyone else to spell them that way, though. And even more so, good luck not having other people think they're being pretentious wankers.
And even in cases where the lowercase starting letter is somewhat accepted, the start of the sentence rule is still left untouched by most writers. Iphones come to mind.
In my native language, the general advice from our language council is to NOT listen to corporation’s rules. You would write “an iphone”, and casing as usual. In fact you wouldn’t really use iphone at all, but smartphone. The idea is that the name casing rules are for showing respect, and an inanimate product does not deserve the same respect as a person.
OTOH you would say Apple though, but I guess that avoids some obvious ambiguity
I don't know what your native language is, could it be Swedish? In Sweden, media consistently write Iphone, because it's a name, and names start with upper case.
As you mentioned, what the marketing department says about the case of letters in the name does not affect this generic recommendation.
Of course, you'll find a lot of people writing it in accordance with the marketing style, bit typically you'll see media follow the Swedish spelling rules.
> In fact you wouldn’t really use iphone at all, but smartphone
The sentence "Smartphone is a phone made by Apple" (or maybe "A smartphone is a phone made by Apple") would have a very different and wrong meaning though, so that doesn't make much sense to me.
To be fair, they mostly advise against GNUplot, and mention Gnuplot because of the aversion to start sentences with lowercase (which is also where they use it with uppercase).
The article explicitly shows that the provided macros are very efficient with a modern compiler. You can check on godbolt.org that they emit the same code.
Though the article only mentions bswap64 and mentioning __builtin_bswap64 would be a nice addition.
