It is indeed not so nice if we can't use special characters, I find it a bit restrictive. The fonts I use are standard on the Mac, I never heard of problems with them. I am not technically aware of those things so it is difficult for me to explain. I guess it is a utf thing more than a font one but I can be totally wrong, if such statements can be useful ;-) Charly
>> - Interesting indeed, if I export the pgn, "Franﾇa, Elcio" >> becomes "Franáa, Elcio" so I don't think this is correct either >> - If I copy "Franﾇa, Elcio" from the Save: Replace game window >> and paste it in the Header Search window, it won't find any game >> of him!? >> > > In both cases, you should realize that "what you see" is not "what > you have." > > What you have is a series of bytes. I mean, in general the string > "abc" is represented by the three bytes 0x61 0x62 and 0x63. > > A font is a look-up table, and only after I spool these bytes > through some font file, I will see something: "abc" (or whatever > different representation, depending on the font description itself). > In any case, the three bytes are there and are always the same. > > If you open the pgn file in a hex editor (or use od -x on a unix > prompt), you should be able to figure out the bytes themselves. They > are key. > > And they are wrong or at least confusing to your font engine. That's > for sure. "Franca" should read 0x46 0x72 0x61 0x6E 0x63 0x61. > Between 0x6E and 0x61 your data is different. There is "something" > in between, not 0x63. > > What you see is what the font makes of it. My suspicion is that your > fonts are not consistent in what they display (the editor in which > you viewed the pgn data uses again a different font description, > probably). > >> - I also found another "funny" name: "Franﾍois Andrﾎ Philidor", >> I know this player. The pgn will export as "François André >> Philidor" which is correct. >> - Using either Lucida Grande or Helvetica fonts doesn't change >> anything >> - if I correct "Francois" to "François" in the Save: Replace game >> window, it will appear correctly in the Game list. >> - Maybe something is wrong with the base but why should I see >> Katakana for special characters in the game list? >> > > As I explained above. This is a font thing. > > Having said all this: I do not know this Franca guy, but the 'c' in > his name _could_ actually be some funny brazilian variation on the c- > theme. Apparently you have a name file with loads of special > characters that do not render well with your fonts. > > So this does not mean that your name file is 'wrong' as such. It > might be that it was created like this on purpose, however > uncomfortable. Normally special characters are avoided. > > How to correct this problem (if you think it is a problem, I think > it is, since it also stops the automatic spellchecker from working)? > Maybe there are tools out there to intelligently translate special > characters back to their standard ascii 7-bit siblings. In that case > you may want to export your complete Dbase to pgn, run the > translater, and import the result into a fresh new base. > > If there are not too many 'strange' names in your base, you could do > it manually using scid's name editor (File/Maintenance/Name spelling/ > Name editor). This at least avoids that you need to correct games > one-by-one. > > J. > >> On 18 mars 09, at 13:54, Joost 't Hart wrote: >> >> >>> Hm, I was pretty careless, I see. >>> >>> 1) It is the 'c' (0x63) that is _replaced_ by the 'nou', and >>> 2) it is in the game list (and not related to spell checking..) >>> >>> Sorry for this. >>> >>> Still, the pgn export should be able to help you identify whether >>> it is a data or a font or a scid problem. >>> >>> G'luck once more, >>> Joost. >>> >>> >>> >>>>> <zip> >>>>> >>>>> >>>>>>> 2) In the game list, names with special characters appear >>>>>>> with Chinese >>>>>>> (or is it Japanese) characters. >>>>>>> >>>>>>> >>>>>> I use Helvetica and as far as I could test, special >>>>>> characters appear as they should, could you be more specific >>>>>> about which special characters and which font are you using? >>>>>> >>>>>> >>>>> I use Lucida Grande for all fonts except for fixed fonts where >>>>> I use Monaco. >>>>> Franﾇa, Elcio is a name example. In case that the text doesn't >>>>> travel well, the character between "Fran" and "a" is funny. >>>>> >>>>> >>>> The character that I see in your mail (let's try to be very >>>> precise) is the Katakana (Japanese, indeed) character NU >>>> (pronounce "nou" in french). >>>> >>>> ============== >>>> >>>> ヌ >>>> >>>> U+30CC KATAKANA LETTER NU >>>> >>>> General Character Properties >>>> >>>> In Unicode since: 1.1 >>>> Unicode category: Letter, Other >>>> >>>> Various Useful Representations >>>> >>>> UTF-8: 0xE3 0x83 0x8C >>>> UTF-16: 0x30CC >>>> >>>> C octal escaped UTF-8: \343\203\214 >>>> XML decimal entity: ヌ >>>> >>>> ============== >>>> >>>> You see this is a multi-byte character. Between the 'n' and the >>>> 'c', three bytes are inserted, together representing the NU. >>>> >>>> The player you talk about seems to be the one identified as >>>> follows in my ssp file: >>>> >>>> Brito, Elcio Eustaquio de Franca #- BRA [2064] 1952 >>>> = Franca, Elcio Eustaquio de B >>>> >>>> >>>> So actually we should not expect any character between the 'n' >>>> and the 'c'. Where does it come from? >>>> >>>> Let's try to find it. Where do you see this character? >>>> >>>> If it is in the old name, check your database. Search for games >>>> played by 'elcio'. If in the board window the name looks also >>>> broken, export that game to pgn and check the pgn file with a >>>> text (or even hex) editor. What do you see? >>>> >>>> If it is in the new name, check your ssp file in a text editor. >>>> What do you see? >>>> >>>> If neither of this reveals something, then it is not a data >>>> problem, and scid probably goes wrong. Otherwise either your >>>> database (I hope not!) or your ssp file has become corrupted. >>>> >>>> G'luck, >>>> Joost. >>>> >>>> >>>> >>> <zip> >>> >> >> >> >> ------------------------------------------------------------------------------ >> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) >> are >> powering Web 2.0 with engaging, cross-platform capabilities. >> Quickly and >> easily build your RIAs with Flex Builder, the Eclipse(TM)based >> development >> software that enables intelligent coding and step-through debugging. >> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com >> _______________________________________________ >> Scid-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/scid-users >> > ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Scid-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scid-users
