Are single-letter programming language names trademarkable? It's no secret that the name of some programming languages are single-letter (sometimes with some non-letter characters) such as C, C++, C#, D, etc. A previous question asked about the situation of copyright of programming language name(s), and the answer lists Apple's Swift OOP language as an example of trademarked programming language names. What this post asks is that: are single-letter programming language names trademarkable, both as plain text and as visual design, considering the name in on itself has little to no novelty.
Probably yes. But it is only a trademark violation when used in connection with a sale of good and services in a manner that is suggests affiliation with the programming language. Thus, you can have a bar named &quot;C++&quot; but not you own programming language or updates to an existing programming language.
Rather than saying "for Project®" which might fairly be interpreted to indicate an affiliation with Microsoft, you ought to say something like "intended to be compatible with Project® (not affiliated with or endorsed by Microsoft)." can you imagine a worse scenario than Microsoft sending a Cease and Desist notice? In that case, I can imagine re-branding to "MYBRAND for E-Mail" as the logo/name and a textual reference to "The [MyBrand for E-Mail] Add-In for Microsoft® Outlook®.". What is the worst case scenario? You could be sued by Microsoft for trademark infringement under the Lanham Act and if you lost, forced to change your product name and to destroy all existing inventory, forced to disgorge all profits you have ever made from selling your product ever, forced to pay their attorneys' fees and costs (which won't be cheap) in addition to your own legal team, have your products seized and destroyed when imported by customs agents follow an ex parte court hearing (i.e. one you had no notice of) secretly brought by Microsoft, and forced to pay punitive damages equal to double the profits you made in addition to the profits themselves. You might not even be able to discharge the judgment against you by going bankrupt and the punitive damages would probably not be tax deductible. Microsoft has every right to do this even if you fully comply with their cease and desist letter. A criminal trademark prosecution would be unlikely in this fact pattern.
Registered Trade Marks aren't the only form of trade mark protection. You also have the law of unregistered trade marks. Basically (and this is an over-simplification), it works like this: a business starts using a trade mark for a specified product: beard comb. Let's say that they don't even register a trade mark. they start selling load and loads (thinks 100s of thousands of $ or £ worth) they become well-known in that market segment. They accrue "goodwill" in the (unregistered) trade mark. That trade mark is protectable in law. That's a summary of the law of passing off aka the law of unregistered trade marks. So, if the new manufacturer is still manufacturing them in the country that you want to sell them in, you'll probably have a problem. This assumes that that country has an equivalent of the law of passing off. The tip then has to be - check to see if the manufacturer is still selling them. If you think it's a good business opportunity and worth a small amount of risk capital - a few hundred $ or £, file the trade mark application is see if anyone does anything about it. You can always withdraw it and avoid a dispute. You might also do a search for registered design rights. They protect the shape of the products (not what it's called - which is what a trade mark does).
It is unclear whether WINE is infringing copyright or if it can rely on a fair use defense. The CAFC held that: that the declaring code and the structure, sequence, and organization of the API packages are entitled to copyright protection In that light, if WINE had original content in the structure, sequence, and organization of its API, the CAFC would likely also find that it is entitled to copyright protection. However, because this issue is outside the scope of the CAFC's exclusive jurisdiction (this is a copyright issue, not a patent issue), the holdings are not binding in any other circuit. Each circuit is free to review anew the copyrightability of APIs when such a case comes up. My guess is that this is the reason the Supreme Court declined to hear an appeal on CAFC's Oracle v. Google opinion. To address your fair use question would be simply speculation, because fair use is always assessed case-by-case, and even in WINE's closest analogy (Oracle v. Google), the CAFC remanded the fair use question back to the trial court, and that question hasn't been decided yet: we remand for further consideration of Google’s fair use defense in light of this decision
There is no internationally-enforceable mechanism regarding how other people call something, or what alphabet can be uses to write a word. I can legally call that country between Bangladesh and Thailand "Burma" or "Myanmar", I can call Україна Ukraine, The Ukraine, or Ukrainia (the latter seems to be old-fashioned, but it's still legal). As a diplomatic matter, the US government seems to have settled on certain designations so that it uses the version "Myanmar" for official purposes although it includes "(Burma)" in popular communications (State Department travel advisories). If it wanted to, the US could call The Republic of North Macedonia by the name "Macedonia", though there would be political protests. The EU, NATO, UN etc. can likewise set its own rules regarding names of countries. There are many additional complications in the case of countries that are not universally / widely recognized, such as Trasnistria and the Republic of Somaliland. If the president of the Republic of Somaliland sought to address the UN, his problem would not be what people would call his country, it is that the Republic of Somaliland is not "recognized" by the UN (it has no official status), or anyone else. The question of "sameness" of language is a prominent feature of nationalist movements. Claims are made that Flemish and Dutch are "the same" or "different", likewise Bosnian, Serbian, Croatian, Montenegrin; Dari, Farsi and Tajik. Thus there is no real chance of litigating the matter of whether Moldovan and Romanian are the "same language" and which name should be used. But if the EU parliament wants to, it could rule that the language of Moldova is to be called "Romanian", or "Moldovan".
Copyright is irrelevant, because names are not protected by copyright. Trademark is relevant: a name can be protected by a trademark. &quot;Yoda&quot; is a registered trademark owned by Lucasfilms, a subsidiary of Disney. There is a list of goods and services where the property right is asserted, so for example you could get sued for peddling art books under this name. It just depends on what your business does. For instance, a plumbing business isn't competing with Lucasfilms w.r.t. that class of goods and services.
Company B has created a derived work from company A's copyright-protected work, so yes, B has infringed on A's copyright. It might be difficult for A to prove it, however, so B might get away with it, but it's still infringement. On the other hand, if B creates software that behaves like A's through reverse engineering, that is, by examining the program's function without examining its code, then they will not have infringed the copyright in the code.
In Google LLC v. Oracle America, Inc., 593 U.S. ___ (2021), the US Supreme Court addressed the reproduction of a subset of the Java API. The majority assumed for the sake of argument that the Java API was protected by copyright, but went on to hold that the reproduction was a fair use. We shall assume, but purely for argument’s sake, that the entire Sun Java API falls within the definition of that which can be copyrighted. We shall ask instead whether Google’s use of part of that API was a “fair use.” Unlike the Federal Circuit, we conclude that it was. So, it is an open question whether an API is protected by copyright, but the precedent from the Federal Circuit will be persuasive authority. The Federal Circuit held that the API is protected by copyright and the Supreme Court did not upset that conclusion. Second, the factors that led the court to conclude the reproduction of part of the Java API was fair use could turn out another way in another fact scenario. Some of the reasoning seems to generalize, but some seems specific to the Java development ecosystem. Briefly, the court recognized: API authorship is a creative process, but is &quot;functional in nature&quot; The reproduction was intended to assist interoperability; it was commercial; there was no evidence of bad faith The amount of code taken was a small amount of the entire Java work, an amount consistent with its goals The market harms to Oracle were dubious My prediction is that there will continue to be significant case-by-case uncertainty as to the applicability of the fair-use defence in this context.