For those interested in a more technical explanation:
Whilst many systems can accept the larger character sets involving special characters beyond the ASCII character set that most people are familiar with (basically the numbers, letters and symbols you can see on your keyboard), it is easy for encoding issues to occur that mean those special characters don't get represented correctly in the database. It depends on a number of different factors, including how the user's system is set up. The developer has the choice of either accepting the user input or trying to sanitise it (check to see if it's a valid character or in a known character set).
So whilst it is technically possible to put those special characters in, it is discouraged, as they may not get stored the way it was intended - especially for cultivar names as Zuzu said, since the site's search engine does not group similar-looking characters (so if you had a cultivar with an accent on a letter, it would not show up in search results unless that specific accented character was included). Hence the ASCII version of the cultivar name is used and if it has special characters, the correct name goes in the "Also sold as" field, enabling it to be found under both names.
As for the duplicate name on the Opuntia entry.... not sure.
@dave?