NetTalk Central

Author Topic: Some ascii character problem in browse and menu  (Read 4820 times)

sukhendu

  • Jr. Member
  • **
  • Posts: 92
    • View Profile
    • Email
Some ascii character problem in browse and menu
« on: August 03, 2014, 09:02:39 AM »
Some ascii characters, say 248 (alt+248 on num keyboard) the produces degree or 230 that produces Greek character mu, do not show correctly on a browse.  These characters are in a cstring field of a TPS file.  Using c9 and NetTalk-6.57.

The 'Next" button does nothing.  Also the form does not load the record that has this character and the browse does not respond.  However, if that column is not in the browse than all work as normal.

Would upgrading to NT8 fix this?

Any help is appreciated.
Sukhendu Barua
« Last Edit: August 03, 2014, 10:53:41 AM by sukhendu »

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11244
    • View Profile
Re: Some ascii character problem in browse and menu
« Reply #1 on: August 03, 2014, 10:13:38 PM »
>> Would upgrading to NT8 fix this?

yes.
Or more specifically, if it was still a problem in NT8 then I could at least investigate it.

cheers
Bruce

sukhendu

  • Jr. Member
  • **
  • Posts: 92
    • View Profile
    • Email
Re: Some ascii character problem in browse and menu
« Reply #2 on: August 18, 2014, 05:18:21 PM »
Hi Bruce - NT8 did not fix this.  I'm still seeing this on my browse.

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11244
    • View Profile
Re: Some ascii character problem in browse and menu
« Reply #3 on: August 18, 2014, 11:17:23 PM »
can you tweak one of the small shipping examples (say example 1) to show the effect please - specifically include the problem characters in your example data.

cheers
Bruce

sukhendu

  • Jr. Member
  • **
  • Posts: 92
    • View Profile
    • Email
Re: Some ascii character problem in browse and menu
« Reply #4 on: August 19, 2014, 10:13:12 AM »
Bruce, following your suggestion I did the following:

1) modified the app1 by adding a table (MUnit), compiled and ran.  The browse looked fine with the extended characters. (see left side picture clip1)

2) exported the MUnit browse and form procedures from app1 into my app (call it AA), compiled and ran.  The browse looks funny (see right side picture clip2).

3) then edited the extended characters while running AA app (alt+248 on the numeric pad).  Now the browse looks normal.  However the report shows an extra A with a hat on top (see the attached tps picture).

I'm at a loss here.  Thanks for looking into this strange issue I'm facing.

Sukhendu


[attachment deleted by admin]

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11244
    • View Profile
Re: Some ascii character problem in browse and menu
« Reply #5 on: August 19, 2014, 09:36:12 PM »
I'm guessing the charset and SaveAs settigs (on the WebServer procedure, Advanced tab), are different in your app as to the example. Set the example to match your app, start with fresh data, and test again.

Cheers
Bruce

sukhendu

  • Jr. Member
  • **
  • Posts: 92
    • View Profile
    • Email
Re: Some ascii character problem in browse and menu
« Reply #6 on: August 20, 2014, 06:36:58 AM »
That did it - thank you Bruce:).  Character set was by default 'utf-8'.  And it is 'ISO-8859-1' in the example app.  Where do I go to set the default character set for future apps?

I appreciate your help.
Sukhendu

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11244
    • View Profile
Re: Some ascii character problem in browse and menu
« Reply #7 on: August 20, 2014, 09:42:13 PM »
Hi Sukhendu,

using utf-8 as the default input is highly recommended. It can / should work in this mode. If it does not then send me an example (set in itf-8 mode and showing the problem area.)

Cheers
Bruce

sukhendu

  • Jr. Member
  • **
  • Posts: 92
    • View Profile
    • Email
Re: Some ascii character problem in browse and menu
« Reply #8 on: August 21, 2014, 09:59:16 AM »
Bruce,

You can reproduce this in the BasicBrowseandForm(1) (NetTalk8 c9 example). Try the following:
1) change character set to 'utf-8'  (It is 'ISO-8859-1' in my example set)
2) compile and run
3) edit one user name by adding extended character (alt+248) degree sign.  This will look fine.
4) TpsScan the MAILBOXE.TPS.  You will notice A-hat on that user name.
5) While in TpsScan, edit another user name by adding the same extended character.
6) Now run the web app and check those two user names.

If you cannot reproduce the error, I can send you my example.  I'm using c9-10376 and NT8.24.

Thanks,
Sukhendu

sukhendu

  • Jr. Member
  • **
  • Posts: 92
    • View Profile
    • Email
Re: Some ascii character problem in browse and menu
« Reply #9 on: August 24, 2014, 02:53:44 PM »
Bruce,

I emailed you an example app.  Hope you can reproduce my issues.

Thanks,
Sukhendu

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11244
    • View Profile
Re: Some ascii character problem in browse and menu
« Reply #10 on: September 02, 2014, 07:35:04 AM »
Hi Sukhendu,

you had "store data as" set to utf-8.
If you do this then you won't be able to view, or edit, the data in Topscan (or indeed any Clarion for windows program.)
By editing in Topscan you broke the data.

If you want to make the data visible in Topscan then you'll need to "save data as" Ascii *. (which may or may not be right for any other special characters you need to display).

You'll want build 8.26 or later to use SaveAs Ascii for an extended character like that. For 8.25 or earlier choose "Save as Spanish". And change it to ASCII when you get 8.26.

cheers
Bruce




sukhendu

  • Jr. Member
  • **
  • Posts: 92
    • View Profile
    • Email
Re: Some ascii character problem in browse and menu
« Reply #11 on: September 02, 2014, 08:57:46 AM »
Hi Bruce,

"Save as Spanish" did the trick.  Thank you.  As you suggested, will change to ASCII when 8.26 is installed.

Regards,
Sukhendu