Sys Ed / Form Event Ed don't like this character (OpenInsight 32-bit Specific) [Revelation On-Line Wiki]

Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 22 NOV 2002 05:50:56AM Ross Brooker wrote:

OpenInsight 32-bit Specific

A minor bug…

Any instances of the ¬ character cause the form event editor to truncate the display of event code at that point.

In the system editor it causes all following end of line positions to go askew by one character.

I wouldn't have found this, except my quick'n'dirty export proc had the following code:
if oldMode then
	nameDelim	= "^"
	recDelim	= "¬"
end else
which I'm now removing. Looks like the OI programmers thought it made a good substitute system delimiter, just like I did!

At 22 NOV 2002 06:33AM Oystein Reigem wrote:

Ross,

I have no problem at all with this character.

This character is not on my Norwegian keyboard. I key it in on the numeric keyboard with Alt+0172.

Are we talking about the same character?

I did my testing in OI 4.0.3, in 4.1.2 latest beta, and in 4.1.2 latest beta with the /UTF8 switch.

- Oystein -

At 22 NOV 2002 08:51AM [url=http://www.sprezzatura.com" onMouseOver=window.status= Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:

The DOS ¬ and the Windows ¬ are separate characters. The DOS ¬ causes the symptoms described.

The Sprezzatura Group

World Leaders in all things RevSoft

At 22 NOV 2002 11:27AM Pat McNerthney wrote:

How about in 4.1.2?

Pat

At 22 NOV 2002 12:03PM Oystein Reigem wrote:

I don't know if you ever noticed, but I spell my name with a DOS "y".

- Oystein -

At 27 NOV 2002 09:17AM Ross Brooker wrote:

I just found another proc that's not happy in OI32 (4.1.0)…

Someone had managed to enter the text Transaction Nº into a proc…

Guess which character caused the System Editor to throw a wobbly*

In fact, in OI16 the character even has underline.

Ross

====

(* Where 'wobbly' is defined as a collection of blobs, dots and ampersands, and the truncation of the proc)

At 27 NOV 2002 01:45PM Oystein Reigem wrote:

Ross,

Perhaps Pat suspects a bug in 4.1.0 since he asks you to try 4.1.2.

I have no problem at all with your two characters in 4.1.2 (and 4.0.3). Have you tried 4.1.2? Go ahead! Don't be shy!

There's also the possibility you're mistaken about the two characters' identity. In a Windows program, like OpenInsight, running on a PC in the Western world, the two characters "¬" and "º" are char(172) and char(186), far away from any dangerous delimiters. Where do your stored procedures come from? The DOS world or the Windows world? What conversions have they gone through, if any?

- Oystein -

At 28 NOV 2002 03:39AM Oystein Reigem wrote:

Ross,

I know what the problem is - Unicode, or UTF8. Sorry I didn't spot it earlier. (For some reason I was thinking Unicode in OI came later than 4.1.) OI 4.1 does by default assume your rows - be they stored procedures or not - are UTF8 encoded Unicode text and not old-fashioned Windows ANSI text. High-bit characters like "¬" and "º" are interpreted as the first byte of two byte UTF8 characters. Visual result: Wobbly termination at the first high-bit character. OI 4.1.2 assumes by default your rows are ANSI. If your rows looked all right in OI16 they will do so in OI 4.1.2.

- Oystein -

View this thread on the forum...