It doesn't matter what the actual status of the word in common usage is, they just have to show they are attempting to protect the trademark so that they can litigate to protect it in specific instances.
Adobe thoroughly enjoys the fact that 'photoshop' is synonymous with image editing. They just have to pretend otherwise. See also band-aid, aspirin, Hoover, Kleenex. (iOS capitalized the last two but not the first two)
I think it's an excellent excuse to try to get people to stop making implicit product recommendations and reinforcing a de facto standard (monpoly?) when they are really just trying to say "photo editing".
Adobe's Creative Suite is a little pet peeve of mine. Many people I know have it illegally (I'm a student, so that says something about the financial capabilities of my peers), and even if they can afford it they say they don't use it professionally or not enough to warrant buying it. Many are even software developers themselves. Some subjects in the study I do even require using Adobe Photoshop specifically, but kindly ask people to buy it rather than supplying a license "because it's too expensive to provide for everyone". (So they think the students can afford it then? I'm quite certain they're just covertly asking us to violate copyright laws here.) If it's all so terribly expensive and apparently we can't negotiate with this overlord, why don't we try to get rid of this industry standard?
So your brand got the rare honour of being used in many languages of the world as a verb, burning the brand to peoples heads and then, instead of being damn proud, you publish such a marketing nonsense and slam it in peoples faces? Are you kidding me?? Really, your marketing department thinks this is wrong? Challenge accepted. Let me GIMP your brand out of my mental image.
This is not a marketing page. It's a legal page from their lawyers stating how the brand name should be used, such that they don't loose control over their trademark. You better believe they're damn proud of the fact that their name is being used as a verb. They just have to show that they're defending the brand so that they don't loose their trademark. Google and Kleenex are in the same boat.
Here's an interesting case from the open-source world.
Apache holds the "Apache Maven" trademark. Apache Maven is a build management/automation tool which uses a lot of "plugins".
The peculiar part is that Apache won't let you name your plugin "maven-<foobar>-plugin" whereas "<foobar>-maven-plugin" is allowed. The wording is:
"Calling it maven-<yourplugin>-plugin (note "Maven" is at the beginning of the plugin name) is strongly discouraged since it's a reserved naming pattern for official Apache Maven plugins maintained by the Apache Maven team with groupId org.apache.maven.plugins. Using this naming pattern is an infringement of the Apache Maven Trademark."
To be clear, we're talking about technical naming here, similar to how you'd name a package or an executable file. These names are actually composite, the full plugin name consists of a "groupId" like "com.acme.foo" and "artifactId" like "<foobar>-maven-plugin". For non-"org.apache.maven.plugins" plugins groupdId is mandatory, so "com.acme.foo:maven-foobar-plugin" makes it pretty clear that it's not an Apache development.
I'm a plugin developer who had the bad luck naming my plugin "maven-<foobar>-plugin" before this convention was established. There's an established user base, a lot of documentation, StackOverflow tags etc. There exists also an alternative plugin named "<foobar>-maven-plugin".
But still once in a while I get contacted by someone (from Apache or totally unrelated) who educates me on how the name of my plugin infringes on the Apache Maven Trademark.
I strongly disagree with this and my position was ever since that if Apache wants to enforce this trademark, they are totally welcome to send me a "Cease and Desist" letter. I'll print it out, hang it on the wall and then shut down the project.
I'm mostly disturbed by the sentence "Since Photoshop is a trademark, you should always use it as an adjective only to describe the Adobe products associated with the Photoshop brand.", as Photoshop is clearly a noun.
Columbia Journalism Review used to have full-page advertisements from Xerox that read, "You can't Xerox a Xerox on a Xerox. But you can make a copy on a Xerox-brand copier."
It was effective, in that I remember the ad many years later. But it didn't do much to change the way people use language.
I don't understand how this is a bad thing, I mean to Google is a verb, to Photoshop ® is to edit photos, it means that their product is the absolute best in its category so much so that it became a verb. Most startup folks would kill it to have their product be a synonym with a verb.
But interestingly, everyone I know in Germany says "Lego bricks/stones" (translated to German, of course) but not "Legos" - but maybe it helps we can/must contract many words to one :P
The "Lego Community" misses the point, arguing over the pluralization instead of realizing the company doesn't want you using the word to describe the blocks at all.
Xerox went to great lengths to prevent their trademark becoming generic in just this way. In the west, they succeeded, and so fell into obscurity—but at least with their trademark mostly intact. In India, where we in Australia would use the verb “photocopy”, they use the verb “xerox”. And a fair few of the machines actually are by Xerox (though far from all of them).
[+] [-] robotresearcher|9 years ago|reply
Adobe thoroughly enjoys the fact that 'photoshop' is synonymous with image editing. They just have to pretend otherwise. See also band-aid, aspirin, Hoover, Kleenex. (iOS capitalized the last two but not the first two)
[+] [-] tsomctl|9 years ago|reply
[+] [-] adambrenecki|9 years ago|reply
Adobe's trademark lawyers would very much like it to not be a verb, but it is. They've lost that battle long ago.
[+] [-] lucb1e|9 years ago|reply
Adobe's Creative Suite is a little pet peeve of mine. Many people I know have it illegally (I'm a student, so that says something about the financial capabilities of my peers), and even if they can afford it they say they don't use it professionally or not enough to warrant buying it. Many are even software developers themselves. Some subjects in the study I do even require using Adobe Photoshop specifically, but kindly ask people to buy it rather than supplying a license "because it's too expensive to provide for everyone". (So they think the students can afford it then? I'm quite certain they're just covertly asking us to violate copyright laws here.) If it's all so terribly expensive and apparently we can't negotiate with this overlord, why don't we try to get rid of this industry standard?
[+] [-] huckyaus|9 years ago|reply
[+] [-] joedevon|9 years ago|reply
[+] [-] geff82|9 years ago|reply
[+] [-] hrayr|9 years ago|reply
[+] [-] chemmail|9 years ago|reply
[+] [-] tdy721|9 years ago|reply
[+] [-] c8g|9 years ago|reply
[+] [-] forgingahead|9 years ago|reply
"No smiling, the cake hasn't been cut yet."
[+] [-] Huhty|9 years ago|reply
[+] [-] lucb1e|9 years ago|reply
[+] [-] orless|9 years ago|reply
Apache holds the "Apache Maven" trademark. Apache Maven is a build management/automation tool which uses a lot of "plugins".
The peculiar part is that Apache won't let you name your plugin "maven-<foobar>-plugin" whereas "<foobar>-maven-plugin" is allowed. The wording is:
"Calling it maven-<yourplugin>-plugin (note "Maven" is at the beginning of the plugin name) is strongly discouraged since it's a reserved naming pattern for official Apache Maven plugins maintained by the Apache Maven team with groupId org.apache.maven.plugins. Using this naming pattern is an infringement of the Apache Maven Trademark."
https://maven.apache.org/guides/plugin/guide-java-plugin-dev...
To be clear, we're talking about technical naming here, similar to how you'd name a package or an executable file. These names are actually composite, the full plugin name consists of a "groupId" like "com.acme.foo" and "artifactId" like "<foobar>-maven-plugin". For non-"org.apache.maven.plugins" plugins groupdId is mandatory, so "com.acme.foo:maven-foobar-plugin" makes it pretty clear that it's not an Apache development.
I'm a plugin developer who had the bad luck naming my plugin "maven-<foobar>-plugin" before this convention was established. There's an established user base, a lot of documentation, StackOverflow tags etc. There exists also an alternative plugin named "<foobar>-maven-plugin".
But still once in a while I get contacted by someone (from Apache or totally unrelated) who educates me on how the name of my plugin infringes on the Apache Maven Trademark.
I strongly disagree with this and my position was ever since that if Apache wants to enforce this trademark, they are totally welcome to send me a "Cease and Desist" letter. I'll print it out, hang it on the wall and then shut down the project.
[+] [-] johnhenry|9 years ago|reply
[+] [-] adambrenecki|9 years ago|reply
> Trademarks are proper adjectives and should be followed by the generic terms they describe.
> Correct: The image was manipulated using Adobe® Photoshop® software.
> Incorrect: The image was manipulated using Photoshop.
Adobe's own marketing pages consistently use the ostensibly "incorrect" usage though: http://www.adobe.com/au/products/photoshop.html
[+] [-] crasm|9 years ago|reply
[+] [-] jve|9 years ago|reply
Where I live many people call Kelloggs any cereal boxes. I though they should have been proud that their every such product is called by their name.
Pampers also comes to my mind - almost no one calls them diapers - just pampers be it from any manufacturer.
[+] [-] tobyhinloopen|9 years ago|reply
[+] [-] reuven|9 years ago|reply
It was effective, in that I remember the ad many years later. But it didn't do much to change the way people use language.
[+] [-] thewhitetulip|9 years ago|reply
[+] [-] ominous|9 years ago|reply
https://youtube.com/watch?v=J7E-aoXLZGY
[+] [-] lostgame|9 years ago|reply
[+] [-] Tomte|9 years ago|reply
It is a shibboleth, and the "Lego community" is incredibly serious about it, to the point of incivility, but who cares?
[+] [-] wink|9 years ago|reply
But interestingly, everyone I know in Germany says "Lego bricks/stones" (translated to German, of course) but not "Legos" - but maybe it helps we can/must contract many words to one :P
[+] [-] qbrass|9 years ago|reply
[+] [-] syphilis2|9 years ago|reply
[+] [-] kriro|9 years ago|reply
[+] [-] tim333|9 years ago|reply
Wikipedia: ... the word "photoshop" has become a verb as in "to Photoshop an image," ...
[+] [-] bdwalter|9 years ago|reply
[+] [-] chrismorgan|9 years ago|reply