As you mention the steps to transition from 5.0 to 5.5 are covered in the What's New in Witango Server 5.5 file. As this is such a simple change to perform manually and did not affect the overall file format we did not believe that it warranted a specific conversion tool.
There are also benefit in doing the conversion with a text editor:
1 If you wish to see the code that is to being changed before it is replaced you can.
2 The process can also be easily undone by reversing the steps.
3 You can also convert entire sites/directories without any reprogramming in a few minutes on any platform.
For those that do not read documentation the steps are ...
In your Witango files do a global whole word find and replace of:
1 METAHTML and replace with META. 2 MULTILINEHTML and replace with W5_MULTILINEHTML. 3 MULTILINE and replace with W5_MULTILINE. 4 W5_MULTILINEHTML and replace with MULTILINE. 5 W5_MULTILINE and replace with MULTILINEHTML.
Witango Support
On 20/09/2004, at 10:35 PM, Stefan Gonick wrote:
The new encoding options do make more sense. However, since the
change will affect all of my programs (and I'm sure most other people's
as well), it would be great if you included a conversion tool to make the
switch easier. I know that there are search and replace instructions,
but when there upgrades that are not backward compatible, I think that
the vendor should help make the transition easier.
My 2 cents.
Stefan
At 01:12 AM 9/20/2004, you wrote:> If I read the include into a variable before the loop, I can't embed > variables that change in each loop.
This is a summary of the encoding methods in 5.5. I think they make sense
now.
The NONE value for the ENCODING attribute allows you to indicate that the
value returned by the meta tag contains formatting codes that are to be
passed back to the user's Web browser without any translations.
The HTML value for the ENCODING attribute allows you to indicate that the
value returned by the meta tag contains HTML formatting codes that are to be
translated as they are passed back to the user's Web browser. I.e. > < & '
and " are translated to the html encoding equivalent.
The META attribute value of the ENCODING attribute performs the same function as NONE but also looks for Witango meta tags in the value and evaluates any it finds.
The METAHTML attribute value lets you combine the functions of META and
HTML.
The MULTILINE attribute value causes Witango to replace return, line feed,
and return/line feed combinations in the value with <BR> tags. It will not
do HTML encoding.
The MULTILINEHTML attribute value lets you combine the functions of HTML and
MULTILINE.
In Witango Server 5.5 <@VAR scope$varname encoding="meta"> will resolve the
meta tags in the variable without html encoding before pushing it onto the
results buffer.
In Witango Server 5.0 <@VAR scope$varname encoding="metahtml"> will resolve
the meta tags in the variable without html before pushing it onto the
results buffer.
This is the reason we cleaned up the encoding names in Witango Server 5.5.
No one seemed to know what they really did.
______________________________________________________________________ __
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
=====================================================
Database WebWorks: Dynamic web sites through database integration
http://www.DatabaseWebWorks.com
_______________________________________________________________________ _
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
