View previous topic :: View next topic |
Author |
Message |
Roger Horton
Joined: 02 Oct 2012 Posts: 1545 Location: Cambridge, UK
|
Posted: Sun Mar 17, 2013 12:50 pm Post subject: Feedback request: Orobanche picridis (35627) |
|
|
This post was made automatically in response to a request for comment on the documentation form. There is more general info about such requests here.
Documented by xmhcman on 17th March 2013. Log-in to edit this sheet.
User comments about this sheet - xmhcman wrote
- Database refuses to believe that Flavigny sur Ozerain, Côte-d'Or, Bourgogne, is in France even when France is selected from 'other countries'!
|
|
Back to top |
|
|
Tom Humphrey Site Admin
Joined: 04 Jul 2005 Posts: 1298 Location: Wallingford, UK
|
Posted: Sun Mar 17, 2013 1:16 pm Post subject: |
|
|
I'm puzzled, what was it reporting, because the French locality appears to have been added to the record correctly. |
|
Back to top |
|
|
Roger Horton
Joined: 02 Oct 2012 Posts: 1545 Location: Cambridge, UK
|
Posted: Sun Mar 17, 2013 2:09 pm Post subject: |
|
|
Certainly a search for specimens from 'George Desplantes' and country 'France' returns (only) this specimen, but with nothing in the locality field. |
|
Back to top |
|
|
Tom Humphrey Site Admin
Joined: 04 Jul 2005 Posts: 1298 Location: Wallingford, UK
|
Posted: Sun Mar 17, 2013 4:35 pm Post subject: |
|
|
The missing place names were due to character-set conversion problems (specifically the 'ô' in Côte-d'Or).
I've still not properly resolved the issue, but at least the names display now.
Thank you for highlighting the problem. |
|
Back to top |
|
|
Roger Horton
Joined: 02 Oct 2012 Posts: 1545 Location: Cambridge, UK
|
Posted: Mon Mar 18, 2013 8:57 am Post subject: |
|
|
I should just type in foreign place-names and not cut-and-paste from Google! |
|
Back to top |
|
|
Tom Humphrey Site Admin
Joined: 04 Jul 2005 Posts: 1298 Location: Wallingford, UK
|
Posted: Mon Mar 18, 2013 9:42 am Post subject: |
|
|
Not your fault
It's the region name that's causing problems not the local place name (which can contain whatever symbols you want).
The database unintentionally has a mixture of columns using different character encodings. The solution will be to reload the offending tables, something I'm not looking forward.
Character sets are too often problematic in ill-conceived databases. At a museum were I worked a few years ago I created chaos by adding lots of Slavic place names to their database (complete with all sorts of exotic glyphs) which displayed correctly. It was only after entering several hundred names that I realized that they broke the indexes - not only could the names not be found but nothing else sorted after my entries could be retrieved either. |
|
Back to top |
|
|
|