https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34590 --- Comment #2 from Esther Melander <esther.melander@bywatersolutions.com> --- A library gave me this example. MARC21/USMARC places a personal name in 100$a (100 1 _ $aGonzález, Juan) UNIMARC places a personal name in 200$a (surname) and 200$b (forename) (200 _ 1 $aGonzález$bJuan) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34590 --- Comment #4 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- The foreign languages/unique characters etc. should be covered by the encoding setting - it's not related to the MARC format. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34590 --- Comment #6 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Esther Melander from comment #5)

Syntax is an option when configuring z39.50 search targets. If this option truly can't be used, then it should be removed in the z39.50 configuration options.

I stumbled on the same thing, but you are correct. In some cases it might work, because the formats are very similar to MARC21, but UNIMARC is too different. You could import it, but it would not make sense at all as all the fields are different.

Also, in this case, syntax appears to deal with how data is mapped and not special characters, as described in comment 2.

Correct, I was referring to your initial description that talked about special chaaracters. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.