From #191 (comment)

Names with seemingly innocuous epithets that nevertheless end up in an unparsed tail:

Profusulinella оblопgа Potievskaya, 1964
Tetrataxis toгosus Postoyalko, 1975
Anomalina badkhyseпsis Kuryleva, 1973
Bigenerina iпfrapaleogenica Suleymanov, 1963
Carpelimus (Trogophloeus) rougemoпti Gildenkov, 2014

All of these contain cyrillic characters that not suppose to be in scientific names: п, г, so they are not parsed correctly

gnparser silently replaces "fake spaces" (mostly non-breaking space symbols coming from copy-pasted web pages, I guess: very difficult to track them). They are turned into normal spaces in the parsed results (normalized, canonicals, authorship and so on). No warnings. Great job.

Those п and г cyrillic characters do so much resemble n and r Latin characters. Very difficult also to detect them when looking at an excel file, for example. I guess those symbols were probably typed because the writer's keyboard had not the Latin ones he/she was trying to reproduce.
Would it be perhaps possible for gnparser to automatically detect and replace them for their Latin "resembled equivalents", and rise a quality warning "Non-standard characters in canonical"?

Yes, I know those cyrillic characters could be part of the authorship.
But the same is already happening to some other characters which are valid in authorships but not in Latin/latinized names, and gnparser is correctly detecting, replacing and warning.
Much like it already happens to ñ (parsing "Anthyllis peñalarensis Vázquez, Piñón & Montañés", returns species:"penalarensis" and canonical "Anthyllis penalarensis", but authorship "Vázquez, Piñón & Montañés", and this quality warning: "Non-standard characters in canonical").

A similar approach could be used for chûjôi epithet above: change úùûü into u, óòôöø into o, and so on with all a, e and i variants.

Cannot parse some unusual epithets #199

Description

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions