Translation of the string "Default value is" (AREV Specific)
At 21 NOV 2003 03:26:10PM E Keeman wrote:
Hi all
I'm busy translation some arev 3.12 MESSAGES and SYSTEXT for our dutch customers.
The string "Default value is" appears in the bottom-borderline when a default value is configured.
The only place I can find this string is in SYSOBJ.
I don't find it elegant to translate it in the $object code.
Does anyone know how this string can be translated?
Regards
Ed Keeman
mailto: [email protected]
At 22 NOV 2003 07:44AM [url=http://www.sprezzatura.com" onMouseOver=window.status= Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
The string also exists in SYSTEXT WINDOW*PARMS however it is not used in real time. Rather a system subroutine called COMPILETEXT_SUB is designed to swap it out. However at first glance this doesn't seem to be working correctly and since we stopped publishing REVMEDIA we tend to only spend lots of time investigating AREV stuff we need sorry
. We'd just go with the editing of object code to change the literal - remembering to change the appropriate byte pointers along the way if the lengths differ.
World Leaders in all things RevSoft
At 23 NOV 2003 07:07AM E Keeman wrote:
Thanks Sprezzatura
But can you axplain a little better what you mean with
"change the appropriate byte pointers if the lengths differ"
where do i set such a pointer?
Because the problem I get with translating in the object code is with the string length. But if the string length can be made dynamic by adjusting a pointer my problem is solved.
Ed Keeman
At 23 NOV 2003 07:34AM The Sprezzatura Group wrote:
The byte preceding the string gives the length of the string. There are other pointers to do with location of literal table et al but that's a tad too complex to go into here.
The Sprezzatura Group
World Leaders in all things RevSoft
At 23 NOV 2003 10:48AM Richard Hunt wrote:
Ahhhh you are taking me back to Prime InfoPc days, before Revelation.
All throughout the object code are literal string pointers. They actually point to the offset starting point of the literal string, within the literal string list. Also, as previously mentioned, the first byte pointed to, in the literal string list, is the length of the litteral string.
There are 2 types of literal string pointers within the object code. First there is the one byte type. It is marked with a CHAR(128):CHAR(pointer). Then there is the two byte type. It is marked with a CHAR(129):CHAR(lo pointer):CHAR(hi pointer).
I would strongly suggest you do not even try to mess with this stuff for 2 reasons…
1) You will most likely mess up your literal string list.
2) I would consider getting written approval from the copyright holder, before modifying any copyrighted object code.
Well… now you know why there is a 254 byte limit on literal strings.
At 23 NOV 2003 11:10AM The Sprezzatura Group wrote:
Didn't Cosmos write InfoPC before releasing AREV?
The Sprezzatura Group
World Leaders in all things RevSoft
At 23 NOV 2003 11:26AM Richard Hunt wrote:
I do believe so. That is what I was led to believe from the Prime InfoPc people. And that is how I found out about Arev.
At 23 NOV 2003 06:41PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
we also suspect that AREV keeps the ONE byte length rule - so 255 applies and no need for lo/hi.
World Leaders in all things RevSoft