Announcement

Collapse
No announcement yet.

Written Accent (Use of Unicode in HRD)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • K7ZCZ
    replied
    Originally posted by WB5JJJ View Post
    Also Lookup fails to import the full name of the ham if it is something like Henry von Smith. Just the von Smith or sometimes just Smith are copied over, but it will take a many word Special Event Station, so it's not counting spaces. I think this has to do with those SES typically being capitalized words when the "von" is not. Just my thoughts from a old programmer from 30+ years ago.
    I've opened Mantis issue 2633 to track this isuse.


    Leave a comment:


  • K7ZCZ
    replied
    Originally posted by joaquin View Post

    Sorry for not answering before. I get this display just pressing 'Lookup' on a Logbook entry. 'Lookup' searchs the data for the corresponding callsign on QRZ, I think.
    Thanks for providing a description of the repro case. I've opened Mantis issue 2632 to track this.

    Leave a comment:


  • joaquin
    replied
    Well, after 25 years of having Unicode around, one has lost the habit of finding such problems in code.

    Leave a comment:


  • WB5JJJ
    replied
    So many non English speaking countries use accents of one form or another over Latin letters. For some reason QRZ.com and others display these correctly, but when you do an lookup in the ALE, they are turned to non sense when transitioned to ALE. The same thing happens to city names. However a simple copy and past will restore everything. Also Lookup fails to import the full name of the ham if it is something like Henry von Smith. Just the von Smith or sometimes just Smith are copied over, but it will take a many word Special Event Station, so it's not counting spaces. I think this has to do with those SES typically being capitalized words when the "von" is not. Just my thoughts from a old programmer from 30+ years ago.

    Leave a comment:


  • joaquin
    replied
    Originally posted by K7ZCZ View Post
    This kind of problem is caused by improperly handled character encoding. I suppose there could be a bug in HRD, but since data can (and does) come from other program,s we'd need to rule those out. Are you able to reproduce this problem such that you enter correct data, and end up seeing poorly displayed data? If so, what specific steps do you follow to do so?
    Sorry for not answering before. I get this display just pressing 'Lookup' on a Logbook entry. 'Lookup' searchs the data for the corresponding callsign on QRZ, I think.

    Leave a comment:


  • K7ZCZ
    replied
    This kind of problem is caused by improperly handled character encoding. I suppose there could be a bug in HRD, but since data can (and does) come from other program,s we'd need to rule those out. Are you able to reproduce this problem such that you enter correct data, and end up seeing poorly displayed data? If so, what specific steps do you follow to do so?

    Leave a comment:


  • joaquin
    started a topic Written Accent (Use of Unicode in HRD)

    Written Accent (Use of Unicode in HRD)

Working...
X