Extend ignoretags with documented cuisine values

[gaben]

There are currently 190 documented ​Key:cuisine values on the wiki. Only 70 of them are in the presets. Do you think it is worth adding them to the ignoretags to feed the spell checker? Obviously, adding them all to the restaurant preset would be overwhelming, not to mention the translations.

Using r19265.

[taylor.smock]

If they are valid values, I'd rather add them to the cuisine tag. It might be overwhelming to users though. The list is sorted alphabetically, so I don't know if it would be that bad, assuming the user knows what they are looking for.

For reference, the current chunk for cuisine is

    <chunk id="cuisine">
    <multiselect key="cuisine" text="Cuisine" values="african;american;arab;argentinian;asian;bagel;balkan;barbecue;bavarian;beef_bowl;brazilian;burger;cake;caribbean;chicken;chinese;coffee_shop;crepe;curry;danish;donut;ethiopian;filipino;fish;fish_and_chips;french;friture;frozen_yogurt;german;georgian;greek;heuriger;hot_dog;ice_cream;indian;indonesian;international;italian;japanese;kebab;korean;lebanese;malaysian;mediterranean;mexican;moroccan;noodle;pancake;pasta;persian;peruvian;pizza;polish;portuguese;ramen;regional;russian;sandwich;sausage;seafood;soba;spanish;steak_house;sushi;tex-mex;tapas;thai;turkish;vietnamese;wings" values_searchable="true" />
    </chunk>

As an alternative, what we could do is have an if statement for multiselect objects, whereby if there are more than a configured number of values, a search box appears.

[skyper]

+1, for adding more values to the preset and to think about options for tags with lots of values.

Though, some values are messy. Looking at the values with at least 500 uses, e.g. I find the deprecated fast_food and the Austrian word Buschenschank which should use a value in English as these places are also found in countries which do not have German as an official language.