Lasso, MySQL and Encoding

classic Classic list List threaded Threaded
21 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Lasso, MySQL and Encoding

Rob Brooks
Hello folks, still struggling a bit with Lasso, MySQL and encoding:

 

In my siteadmin I have 'Default Page Encoding' set to UTF-8

 

In site admin for my host I have 'Use MySQL 4.1/5.x Character Sets' set to
Yes

 

When I run the following inline:

 

                var:'sql' = 'show variables like \'charac%\';';

                inline:-database='******',

                -sql=$sql,

                -username='*****',

                -password='******';

                                iterate:records_array ,(var:'item');

                                                output:$item->first + ': ' +
$item->second + '<br>';

                                /iterate;

 

                /inline;

 

I get the following output:

 

character_set_client: latin1

character_set_connection: latin1

character_set_database: utf8

character_set_filesystem: binary

character_set_results: latin1

character_set_server: utf8

character_set_system: utf8

character_sets_dir: /usr/share/mysql/charsets/

 

The same query run from the command line mysql client (centos) shows:

 

+--------------------------+----------------------------+

| Variable_name            | Value                      |

+--------------------------+----------------------------+

| character_set_client     | utf8                       |

| character_set_connection | utf8                       |

| character_set_database   | utf8                       |

| character_set_filesystem | binary                     |

| character_set_results    | utf8                       |

| character_set_server     | utf8                       |

| character_set_system     | utf8                       |

| character_sets_dir       | /usr/share/mysql/charsets/ |

+--------------------------+----------------------------+

 

 

 

Why is the client, connection and results latin1 here when connecting from
lasso?

 

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

RE: Lasso, MySQL and Encoding

Rob Brooks
This excerpt:

If the "Use MySQL 4.1/5.x Character Sets" option is set to Yes in the Setup
> Data Sources > Hosts section of Lasso Site Administration for a MySQL host
then Lasso will transmit all data to MySQL in UTF-8 and allow MySQL to
automatically encode that data according to the table definition.


from : http://www.lassosoft.com/Character-Encoding-and-Unicode-Workflow

leads me to believe that if I have this setting set to 'Yes' then all
connections to MySQL for this host should be in utf8 and my
character_set_client, character_set_connection, and character_set_results
variables should show as utf8?


Thanks
Rob



-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Rob Brooks
Sent: Friday, November 23, 2012 12:45 PM
To: [hidden email]
Subject: Lasso, MySQL and Encoding

Hello folks, still struggling a bit with Lasso, MySQL and encoding:

 

In my siteadmin I have 'Default Page Encoding' set to UTF-8

 

In site admin for my host I have 'Use MySQL 4.1/5.x Character Sets' set to
Yes

 

When I run the following inline:

 

                var:'sql' = 'show variables like \'charac%\';';

                inline:-database='******',

                -sql=$sql,

                -username='*****',

                -password='******';

                                iterate:records_array ,(var:'item');

                                                output:$item->first + ': ' +
$item->second + '<br>';

                                /iterate;

 

                /inline;

 

I get the following output:

 

character_set_client: latin1

character_set_connection: latin1

character_set_database: utf8

character_set_filesystem: binary

character_set_results: latin1

character_set_server: utf8

character_set_system: utf8

character_sets_dir: /usr/share/mysql/charsets/

 

The same query run from the command line mysql client (centos) shows:

 

+--------------------------+----------------------------+

| Variable_name            | Value                      |

+--------------------------+----------------------------+

| character_set_client     | utf8                       |

| character_set_connection | utf8                       |

| character_set_database   | utf8                       |

| character_set_filesystem | binary                     |

| character_set_results    | utf8                       |

| character_set_server     | utf8                       |

| character_set_system     | utf8                       |

| character_sets_dir       | /usr/share/mysql/charsets/ |

+--------------------------+----------------------------+

 

 

 

Why is the client, connection and results latin1 here when connecting from
lasso?

 

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

RE: Lasso, MySQL and Encoding

stevepiercy
Your connection may be UTF-8, but the encoding setting of the
objects might not.  Check under Setup > Datasources > Tables
whether each item overrides the connection setting.  You can do
a "Table Batch Change" within the scope of a selected Host or
Database instead of onesies.

For a quick overview of all table encoding settings:

Utility > SQL Browser > Browser:

select * from security_database_tables where encoding != 'utf-8';

There may be other encoding issues, but let's try this one first.

--steve


On 11/23/12 at 2:52 PM, [hidden email] (Rob Brooks) pronounced:

>This excerpt:
>
>If the "Use MySQL 4.1/5.x Character Sets" option is set to Yes in the Setup
>>Data Sources > Hosts section of Lasso Site Administration for a MySQL host
>then Lasso will transmit all data to MySQL in UTF-8 and allow MySQL to
>automatically encode that data according to the table definition.
>
>
>from : http://www.lassosoft.com/Character-Encoding-and-Unicode-Workflow
>
>leads me to believe that if I have this setting set to 'Yes' then all
>connections to MySQL for this host should be in utf8 and my
>character_set_client, character_set_connection, and character_set_results
>variables should show as utf8?
>
>
>Thanks
>Rob
>
>
>
>-----Original Message-----
>From: [hidden email]
>[mailto:[hidden email]] On Behalf Of Rob Brooks
>Sent: Friday, November 23, 2012 12:45 PM
>To: [hidden email]
>Subject: Lasso, MySQL and Encoding
>
>Hello folks, still struggling a bit with Lasso, MySQL and encoding:
>
>
>
>In my siteadmin I have 'Default Page Encoding' set to UTF-8
>
>
>
>In site admin for my host I have 'Use MySQL 4.1/5.x Character Sets' set to
>Yes
>
>
>When I run the following inline:
>
>
>
>var:'sql' = 'show variables like \'charac%\';';
>
>inline:-database='******',
>
>-sql=$sql,
>
>-username='*****',
>
>-password='******';
>
>iterate:records_array ,(var:'item');
>
>output:$item->first + ': ' +
>$item->second + '<br>';
>
>/iterate;
>
>
>
>/inline;
>
>
>
>I get the following output:
>
>
>
>character_set_client: latin1
>
>character_set_connection: latin1
>
>character_set_database: utf8
>
>character_set_filesystem: binary
>
>character_set_results: latin1
>
>character_set_server: utf8
>
>character_set_system: utf8
>
>character_sets_dir: /usr/share/mysql/charsets/
>
>
>
>The same query run from the command line mysql client (centos) shows:
>
>
>
>+--------------------------+----------------------------+
>
>| Variable_name            | Value                      |
>
>+--------------------------+----------------------------+
>
>| character_set_client     | utf8                       |
>| character_set_connection | utf8                       |
>| character_set_database   | utf8                       |
>| character_set_filesystem | binary                     |
>| character_set_results    | utf8                       |
>| character_set_server     | utf8                       |
>| character_set_system     | utf8                       |
>| character_sets_dir       | /usr/share/mysql/charsets/ |
>+--------------------------+----------------------------+
>
>
>
>
>
>
>
>Why is the client, connection and results latin1 here when connecting from
>lasso?
>
>
>
>#############################################################
>This message is sent to you because you are subscribed to
>the mailing list Lasso
>[hidden email]
>To unsubscribe, E-mail to: <[hidden email]>
>Send administrative queries to  <[hidden email]>
>
>#############################################################
>This message is sent to you because you are subscribed to
>the mailing list Lasso
>[hidden email]
>To unsubscribe, E-mail to: <[hidden email]>
>Send administrative queries to  <[hidden email]>

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
Steve Piercy               Web Site Builder              
Soquel, CA
<[hidden email]>                  <http://www.StevePiercy.com/>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Lasso, MySQL and Encoding

Lasso Talk
In reply to this post by Rob Brooks
We use Lasso more year for Central Europe character encoding with MySQL.

Her are any rules for correct character encoding:
MySQL:
Set Database to UTF-8 encoding and set same for each Table in this
database. Which chrar set use in Table setting for UTF-8 isn´t important.

After:
LASSO:
In SiteAdmin in DataSource select MySQL connector and select Database.
On right side you can set Table Batch Change for Database. Select UTF-8
and press Perform button. All Tables are set to selected encoding.
If you are add new table to existing database you must manual change
Table encoding. Click to table name in Table list and on right side set
encoding for selected Table and press Update button. Here you can view
correct Table encoding which is set in Lasso.

HTML Page:
use BOM for each web page (HTML page). In Dreamweaver create new page
and in menu select MODIFY/PAGE PROPERTIES. In this panel select TITLE
ENCODING. Set page enaoding to UTF-8 and select check button INCLUDE
UNICODE SIGNATURE (BOM). After press APPLY button and OK button. This
option you can set in DW Preferences as default NEW page properties.

With this option we use any languages in one MySQL Database and Table
(for menu languages translations).

Lubos

> Rob Brooks <mailto:[hidden email]>
> 23. novembra 2012 19:45
> Hello folks, still struggling a bit with Lasso, MySQL and encoding:
>
>
>
> In my siteadmin I have 'Default Page Encoding' set to UTF-8
>
>
>
> In site admin for my host I have 'Use MySQL 4.1/5.x Character Sets' set to
> Yes
>
>
>
> When I run the following inline:
>
>
>
> var:'sql' = 'show variables like \'charac%\';';
>
> inline:-database='******',
>
> -sql=$sql,
>
> -username='*****',
>
> -password='******';
>
> iterate:records_array ,(var:'item');
>
> output:$item->first + ': ' +
> $item->second + '<br>';
>
> /iterate;
>
>
>
> /inline;
>
>
>
> I get the following output:
>
>
>
> character_set_client: latin1
>
> character_set_connection: latin1
>
> character_set_database: utf8
>
> character_set_filesystem: binary
>
> character_set_results: latin1
>
> character_set_server: utf8
>
> character_set_system: utf8
>
> character_sets_dir: /usr/share/mysql/charsets/
>
>
>
> The same query run from the command line mysql client (centos) shows:
>
>
>
> +--------------------------+----------------------------+
>
> | Variable_name | Value |
>
> +--------------------------+----------------------------+
>
> | character_set_client | utf8 |
>
> | character_set_connection | utf8 |
>
> | character_set_database | utf8 |
>
> | character_set_filesystem | binary |
>
> | character_set_results | utf8 |
>
> | character_set_server | utf8 |
>
> | character_set_system | utf8 |
>
> | character_sets_dir | /usr/share/mysql/charsets/ |
>
> +--------------------------+----------------------------+
>
>
>
>
>
>
>
> Why is the client, connection and results latin1 here when connecting from
> lasso?
>
>
>
> #############################################################
> This message is sent to you because you are subscribed to
> the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to <[hidden email]>
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

RE: Lasso, MySQL and Encoding

Rob Brooks
In reply to this post by stevepiercy
I did do the Table Batch Change to UTF-8 at the Host level.

 

However, when I do: select * from security_database_tables where encoding !=
'utf-8';

 

I get:

 


id

id_database

name

alias

enabled

encoding

modified


1

1

All Tables

NULL

N

iso8859-1

NULL


11

2

security_datasources

NULL

Y

iso8859-1

NULL


12

2

security_datasource_hosts

NULL

Y

iso8859-1

NULL


13

2

security_datasource_databases

NULL

Y

iso8859-1

NULL


15

2

security_database_tables

NULL

Y

iso8859-1

NULL


17

2

security_table_fields

NULL

Y

iso8859-1

NULL

 

 

Plus a small number of tables from my database in question where the
encoding is set to iso8859-1. (not all the tables by any stretch) This is
interesting because I did the batch change at the Host level.  Also the
tables that I'm testing on are not showing up in the list.  My test includes
updating a field in a table with a string of UTF-8 chars including Chinese
letters.  If in the same inline I prefix the UPDATE stmnt with 'set names
utf-8', the characters appear correctly in myslq.  If I don't prefix with
the set names stmnt, they appear garbled or as if non latin1 chars have been
encoded with latin1

 

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Steve Piercy - Web
Site Builder
Sent: Friday, November 23, 2012 3:17 PM
To: [hidden email]
Subject: RE: Lasso, MySQL and Encoding

 

Your connection may be UTF-8, but the encoding setting of the objects might
not.  Check under Setup > Datasources > Tables whether each item overrides
the connection setting.  You can do a "Table Batch Change" within the scope
of a selected Host or Database instead of onesies.

 

For a quick overview of all table encoding settings:

 

Utility > SQL Browser > Browser:

 

select * from security_database_tables where encoding != 'utf-8';

 

There may be other encoding issues, but let's try this one first.

 

--steve

 

 

On 11/23/12 at 2:52 PM,  <mailto:[hidden email]>
[hidden email] (Rob Brooks) pronounced:

 

>This excerpt:

>

>If the "Use MySQL 4.1/5.x Character Sets" option is set to Yes in the

>Setup

>>Data Sources > Hosts section of Lasso Site Administration for a MySQL

>>host

>then Lasso will transmit all data to MySQL in UTF-8 and allow MySQL to

>automatically encode that data according to the table definition.

>

>

>from :  <http://www.lassosoft.com/Character-Encoding-and-Unicode-Workflow>
http://www.lassosoft.com/Character-Encoding-and-Unicode-Workflow

>

>leads me to believe that if I have this setting set to 'Yes' then all

>connections to MySQL for this host should be in utf8 and my

>character_set_client, character_set_connection, and

>character_set_results variables should show as utf8?

>

>

>Thanks

>Rob

>

>

>

>-----Original Message-----

>From:  <mailto:[hidden email]>
[hidden email]

>[ <mailto:[hidden email]>
mailto:[hidden email]] On Behalf Of Rob Brooks

>Sent: Friday, November 23, 2012 12:45 PM

>To:  <mailto:[hidden email]> [hidden email]

>Subject: Lasso, MySQL and Encoding

>

>Hello folks, still struggling a bit with Lasso, MySQL and encoding:

>

>

>

>In my siteadmin I have 'Default Page Encoding' set to UTF-8

>

>

>

>In site admin for my host I have 'Use MySQL 4.1/5.x Character Sets' set

>to Yes

>

>

>When I run the following inline:

>

>

>

>var:'sql' = 'show variables like \'charac%\';';

>

>inline:-database='******',

>

>-sql=$sql,

>

>-username='*****',

>

>-password='******';

>

>iterate:records_array ,(var:'item');

>

>output:$item->first + ': ' +

>$item->second + '<br>';

>

>/iterate;

>

>

>

>/inline;

>

>

>

>I get the following output:

>

>

>

>character_set_client: latin1

>

>character_set_connection: latin1

>

>character_set_database: utf8

>

>character_set_filesystem: binary

>

>character_set_results: latin1

>

>character_set_server: utf8

>

>character_set_system: utf8

>

>character_sets_dir: /usr/share/mysql/charsets/

>

>

>

>The same query run from the command line mysql client (centos) shows:

>

>

>

>+--------------------------+----------------------------+

>

>| Variable_name            | Value                      |

>

>+--------------------------+----------------------------+

>

>| character_set_client     | utf8                       |

>| character_set_connection | utf8                       |

>| character_set_database   | utf8                       |

>| character_set_filesystem | binary                     |

>| character_set_results    | utf8                       |

>| character_set_server     | utf8                       |

>| character_set_system     | utf8                       |

>| character_sets_dir       | /usr/share/mysql/charsets/ |

>+--------------------------+----------------------------+

>

>

>

>

>

>

>

>Why is the client, connection and results latin1 here when connecting

>from lasso?

>

>

>

>#############################################################

>This message is sent to you because you are subscribed to the mailing

>list Lasso  <mailto:[hidden email]> [hidden email] To
unsubscribe, E-mail to:

>< <mailto:[hidden email]>
[hidden email]>

>Send administrative queries to  <
<mailto:[hidden email]>
[hidden email]>

>

>#############################################################

>This message is sent to you because you are subscribed to the mailing

>list Lasso  <mailto:[hidden email]> [hidden email] To
unsubscribe, E-mail to:

>< <mailto:[hidden email]>
[hidden email]>

>Send administrative queries to  <
<mailto:[hidden email]>
[hidden email]>

 

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

-- --

Steve Piercy               Web Site Builder              

Soquel, CA

< <mailto:[hidden email]> [hidden email]>                  <
<http://www.StevePiercy.com/> http://www.StevePiercy.com/>

 

#############################################################

This message is sent to you because you are subscribed to

  the mailing list Lasso

 <mailto:[hidden email]> [hidden email]

To unsubscribe, E-mail to: < <mailto:[hidden email]>
[hidden email]>

Send administrative queries to  < <mailto:[hidden email]>
[hidden email]>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

RE: Lasso, MySQL and Encoding

stevepiercy
Actually, I just remembered seeing this once before and
recently.  You can use the -host connection method in your
inlines, and use this parameter:

     -tableencoding = 'utf-8'

So this will fix it:

     inline(-host=array(
             -datasource='mysqlds',
             -name='localhost',
             -username='***',
             -password='***',
             -tableencoding='utf-8'),
         -database   = 'db',
         ...
         );

For the looooooong discussion of this exact issue and resolution
tefer to:
http://lasso.2283332.n4.nabble.com/Round-tripping-Chinese-characters-through-MySQL-and-Lasso-tt3259283.html#none

--steve


On 11/23/12 at 4:13 PM, [hidden email] (Rob Brooks) pronounced:

>I did do the Table Batch Change to UTF-8 at the Host level.
>
>
>
>However, when I do: select * from security_database_tables where encoding !=
>'utf-8';
>
>
>
>I get:
>
>
>
>
>id
>id_database
>name
>alias
>enabled
>encoding
>modified
>
>1
>
>1
>
>All Tables
>
>NULL
>
>N
>
>iso8859-1
>
>NULL
>
>
>11
>
>2
>
>security_datasources
>
>NULL
>
>Y
>
>iso8859-1
>
>NULL
>
>
>12
>
>2
>
>security_datasource_hosts
>
>NULL
>
>Y
>
>iso8859-1
>
>NULL
>
>
>13
>
>2
>
>security_datasource_databases
>
>NULL
>
>Y
>
>iso8859-1
>
>NULL
>
>
>15
>
>2
>
>security_database_tables
>
>NULL
>
>Y
>
>iso8859-1
>
>NULL
>
>
>17
>
>2
>
>security_table_fields
>
>NULL
>
>Y
>
>iso8859-1
>
>NULL
>
>
>
>
>
>Plus a small number of tables from my database in question where the
>encoding is set to iso8859-1. (not all the tables by any stretch) This is
>interesting because I did the batch change at the Host level.  Also the
>tables that I'm testing on are not showing up in the list.  My test includes
>updating a field in a table with a string of UTF-8 chars including Chinese
>letters.  If in the same inline I prefix the UPDATE stmnt with 'set names
>utf-8', the characters appear correctly in myslq.  If I don't prefix with
>the set names stmnt, they appear garbled or as if non latin1 chars have been
>encoded with latin1
>
>
>
>-----Original Message-----
>From: [hidden email]
>[mailto:[hidden email]] On Behalf Of Steve Piercy - Web
>Site Builder
>Sent: Friday, November 23, 2012 3:17 PM
>To: [hidden email]
>Subject: RE: Lasso, MySQL and Encoding
>
>
>
>Your connection may be UTF-8, but the encoding setting of the objects might
>not.  Check under Setup > Datasources > Tables whether each item overrides
>the connection setting.  You can do a "Table Batch Change" within the scope
>of a selected Host or Database instead of onesies.
>
>
>
>For a quick overview of all table encoding settings:
>
>
>
>Utility > SQL Browser > Browser:
>
>
>
>select * from security_database_tables where encoding != 'utf-8';
>
>
>
>There may be other encoding issues, but let's try this one first.
>
>
>
>--steve
>
>
>
>
>
>On 11/23/12 at 2:52 PM,  <mailto:[hidden email]>
>[hidden email] (Rob Brooks) pronounced:
>
>
>
>>This excerpt:
>
>>
>
>>If the "Use MySQL 4.1/5.x Character Sets" option is set to Yes in the
>
>>Setup
>
>>>Data Sources > Hosts section of Lasso Site Administration for a MySQL
>
>>>host
>
>>then Lasso will transmit all data to MySQL in UTF-8 and allow MySQL to
>
>>automatically encode that data according to the table definition.
>
>>
>
>>
>
>>from :  <http://www.lassosoft.com/Character-Encoding-and-Unicode-Workflow>
>http://www.lassosoft.com/Character-Encoding-and-Unicode-Workflow
>
>>
>
>>leads me to believe that if I have this setting set to 'Yes' then all
>
>>connections to MySQL for this host should be in utf8 and my
>
>>character_set_client, character_set_connection, and
>
>>character_set_results variables should show as utf8?
>
>>
>
>>
>
>>Thanks
>
>>Rob
>
>>
>
>>
>
>>
>
>>-----Original Message-----
>
>>From:  <mailto:[hidden email]>
>[hidden email]
>>[ <mailto:[hidden email]>
>mailto:[hidden email]] On Behalf Of Rob Brooks
>
>>Sent: Friday, November 23, 2012 12:45 PM
>
>>To:  <mailto:[hidden email]> [hidden email]
>
>>Subject: Lasso, MySQL and Encoding
>
>>
>
>>Hello folks, still struggling a bit with Lasso, MySQL and encoding:
>
>>
>
>>
>
>>
>
>>In my siteadmin I have 'Default Page Encoding' set to UTF-8
>
>>
>
>>
>
>>
>
>>In site admin for my host I have 'Use MySQL 4.1/5.x Character Sets' set
>
>>to Yes
>
>>
>
>>
>
>>When I run the following inline:
>
>>
>
>>
>
>>
>
>>var:'sql' = 'show variables like \'charac%\';';
>
>>
>
>>inline:-database='******',
>
>>
>
>>-sql=$sql,
>
>>
>
>>-username='*****',
>
>>
>
>>-password='******';
>
>>
>
>>iterate:records_array ,(var:'item');
>
>>
>
>>output:$item->first + ': ' +
>
>>$item->second + '<br>';
>
>>
>
>>/iterate;
>
>>
>
>>
>
>>
>
>>/inline;
>
>>
>
>>
>
>>
>
>>I get the following output:
>
>>
>
>>
>
>>
>
>>character_set_client: latin1
>
>>
>
>>character_set_connection: latin1
>
>>
>
>>character_set_database: utf8
>
>>
>
>>character_set_filesystem: binary
>
>>
>
>>character_set_results: latin1
>
>>
>
>>character_set_server: utf8
>
>>
>
>>character_set_system: utf8
>
>>
>
>>character_sets_dir: /usr/share/mysql/charsets/
>
>>
>
>>
>
>>
>
>>The same query run from the command line mysql client (centos) shows:
>
>>
>
>>
>
>>
>
>>+--------------------------+----------------------------+
>
>>
>
>>| Variable_name            | Value                      |
>
>>
>
>>+--------------------------+----------------------------+
>
>>
>
>>| character_set_client     | utf8                       |
>
>>| character_set_connection | utf8                       |
>
>>| character_set_database   | utf8                       |
>
>>| character_set_filesystem | binary                     |
>
>>| character_set_results    | utf8                       |
>
>>| character_set_server     | utf8                       |
>
>>| character_set_system     | utf8                       |
>
>>| character_sets_dir       | /usr/share/mysql/charsets/ |
>
>>+--------------------------+----------------------------+
>
>>
>
>>
>
>>
>
>>
>
>>
>
>>
>
>>
>
>>Why is the client, connection and results latin1 here when connecting
>
>>from lasso?
>
>>
>
>>
>
>>
>
>>#############################################################
>
>>This message is sent to you because you are subscribed to the mailing
>
>>list Lasso  <mailto:[hidden email]> [hidden email] To
>unsubscribe, E-mail to:
>>< <mailto:[hidden email]>
>[hidden email]>
>
>>Send administrative queries to  <
><mailto:[hidden email]>
>[hidden email]>
>
>>
>
>>#############################################################
>
>>This message is sent to you because you are subscribed to the mailing
>
>>list Lasso  <mailto:[hidden email]> [hidden email] To
>unsubscribe, E-mail to:
>>< <mailto:[hidden email]>
>[hidden email]>
>
>>Send administrative queries to  <
><mailto:[hidden email]>
>[hidden email]>
>
>
>
>-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>
>-- --
>
>Steve Piercy               Web Site Builder
>Soquel, CA
>
>< <mailto:[hidden email]> [hidden email]>                  <
><http://www.StevePiercy.com/> http://www.StevePiercy.com/>
>
>
>
>#############################################################
>
>This message is sent to you because you are subscribed to
>
>the mailing list Lasso
>
><mailto:[hidden email]> [hidden email]
>
>To unsubscribe, E-mail to: < <mailto:[hidden email]>
>[hidden email]>
>
>Send administrative queries to  < <mailto:[hidden email]>
>[hidden email]>
>
>#############################################################
>This message is sent to you because you are subscribed to
>the mailing list Lasso
>[hidden email]
>To unsubscribe, E-mail to: <[hidden email]>
>Send administrative queries to  <[hidden email]>

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
Steve Piercy               Web Site Builder              
Soquel, CA
<[hidden email]>                  <http://www.StevePiercy.com/>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

RE: Lasso, MySQL and Encoding

Rob Brooks
In reply to this post by Lasso Talk
Thank to Steve and Lubos,

In conclusion,

We're running Lasso 8.6 on CentOS 5.8 with Apache 2.2.3 and MySQL 5.0.95

We needed full UTF8 support for Latin American, European and Asian
languages.

In addition to having all settings in MySQL set to UTF8 we also needed the
following on Lasso:

1.  'Use MySQL 4.1/5.x Character Sets' set to 'Yes' in Data
Sources->Hosts->Host Detail in Lasso site admin.
2.  Default Page Encoding set to 'UTF-8(Unicode)' in Lasso Settings in Lasso
site admin.
2.  Use the -host array for all MySQL inlines with -tableencoding='utf-8'
option.
3.  All files that have MySQL inlines must be saved encoded as UTF8 *with
BOM*.

If any one of these criteria weren't met then there were problems.

Probably rehashing old information but thanks for the help getting it setup
and working.

Questions:

1.  I'm guessing there isn't a server wide setting that would solve having
to use the -tablencoding='utf-8' option in the host array in every inline in
Lasso 8.6 (must now change many, many inlines to internationalize)?  Surely
someone would have mentioned this  :-)

2.  Is there such a setting in Lasso 9 or a change in methods for handling
UTF8 encoding with MySQL?


Thanks
Rob



-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of LassoTalk
Sent: Friday, November 23, 2012 3:26 PM
To: [hidden email]
Subject: Re: Lasso, MySQL and Encoding

We use Lasso more year for Central Europe character encoding with MySQL.

Her are any rules for correct character encoding:
MySQL:
Set Database to UTF-8 encoding and set same for each Table in this database.
Which chrar set use in Table setting for UTF-8 isn´t important.

After:
LASSO:
In SiteAdmin in DataSource select MySQL connector and select Database.
On right side you can set Table Batch Change for Database. Select UTF-8 and
press Perform button. All Tables are set to selected encoding.
If you are add new table to existing database you must manual change Table
encoding. Click to table name in Table list and on right side set encoding
for selected Table and press Update button. Here you can view correct Table
encoding which is set in Lasso.

HTML Page:
use BOM for each web page (HTML page). In Dreamweaver create new page and in
menu select MODIFY/PAGE PROPERTIES. In this panel select TITLE ENCODING. Set
page enaoding to UTF-8 and select check button INCLUDE UNICODE SIGNATURE
(BOM). After press APPLY button and OK button. This option you can set in DW
Preferences as default NEW page properties.

With this option we use any languages in one MySQL Database and Table (for
menu languages translations).

Lubos

> Rob Brooks <mailto:[hidden email]> 23. novembra 2012 19:45
> Hello folks, still struggling a bit with Lasso, MySQL and encoding:
>
>
>
> In my siteadmin I have 'Default Page Encoding' set to UTF-8
>
>
>
> In site admin for my host I have 'Use MySQL 4.1/5.x Character Sets'
> set to Yes
>
>
>
> When I run the following inline:
>
>
>
> var:'sql' = 'show variables like \'charac%\';';
>
> inline:-database='******',
>
> -sql=$sql,
>
> -username='*****',
>
> -password='******';
>
> iterate:records_array ,(var:'item');
>
> output:$item->first + ': ' +
> $item->second + '<br>';
>
> /iterate;
>
>
>
> /inline;
>
>
>
> I get the following output:
>
>
>
> character_set_client: latin1
>
> character_set_connection: latin1
>
> character_set_database: utf8
>
> character_set_filesystem: binary
>
> character_set_results: latin1
>
> character_set_server: utf8
>
> character_set_system: utf8
>
> character_sets_dir: /usr/share/mysql/charsets/
>
>
>
> The same query run from the command line mysql client (centos) shows:
>
>
>
> +--------------------------+----------------------------+
>
> | Variable_name | Value |
>
> +--------------------------+----------------------------+
>
> | character_set_client | utf8 |
>
> | character_set_connection | utf8 |
>
> | character_set_database | utf8 |
>
> | character_set_filesystem | binary |
>
> | character_set_results | utf8 |
>
> | character_set_server | utf8 |
>
> | character_set_system | utf8 |
>
> | character_sets_dir | /usr/share/mysql/charsets/ |
>
> +--------------------------+----------------------------+
>
>
>
>
>
>
>
> Why is the client, connection and results latin1 here when connecting
> from lasso?
>
>
>
> #############################################################
> This message is sent to you because you are subscribed to the mailing
> list Lasso [hidden email] To unsubscribe, E-mail to:
> <[hidden email]>
> Send administrative queries to <[hidden email]>
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>


#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Lasso, MySQL and Encoding

Jolle Carlestam-3
27 nov 2012 kl. 08:04 skrev Rob Brooks <[hidden email]>:

> 2.  Is there such a setting in Lasso 9 or a change in methods for handling
> UTF8 encoding with MySQL?

My experience is that Lasso 9 just handles it. Provided your tables are setup as UTF-8 Lasso 9 simply works.

HDB
Jolle
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

How would you have KNOP pass 2 variables to a php include?

Paul Moebius-3
How would you have KNOP pass 2 variables to a php include?
I want to pass to variables $MP and $PID
to the connector.php


<script type="text/javascript" charset="utf-8">
                        $().ready(function() {
                                var elf = $('#elfinder').elfinder({


                                        url : '/_plugins/elfinder/php/connector.php'  


                                }).elfinder('instance');
                        });
</script>
 

Sincerely,
 
Paul Moebius | Vice President | Digital One Color ~ Graphics Reimagined


#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: How would you have KNOP pass 2 variables to a php include?

Jolle Carlestam-3
I don't understand the question.

Knop does not handle variables per se. That is a Lasso thing. And Lasso, or Knop, can not directly manipulate PHP variables. It can however provide vars as content for get or post params that could be brought along with an AJAX call.

Here's one way of doing that. I'm assuming Lasso 8.
<?LassoScript

var('my_mp' = 'My MP content');
var('my_pid' = 'My PID content');

/* ... more code ... */

?>
<script type="text/javascript" charset="utf-8">
        $().ready(function() {
                var elf = $('#elfinder').elfinder({
                        url : '/_plugins/elfinder/php/connector.php?mp=[encode_url($my_mp) + '&pid=' + encode_url($my_pid)]'
                }).elfinder('instance');
        });
</script>

NB! The above assumes you don't need square brackets in your javascript code. ANd you need for the PHP file to convert the get params to proper vars.

HDB
Jolle

27 nov 2012 kl. 08:40 skrev Paul Moebius <[hidden email]>:

> How would you have KNOP pass 2 variables to a php include?
> I want to pass to variables $MP and $PID
> to the connector.php
>
>
> <script type="text/javascript" charset="utf-8">
> $().ready(function() {
> var elf = $('#elfinder').elfinder({
>
>
> url : '/_plugins/elfinder/php/connector.php'  
>
>
> }).elfinder('instance');
> });
> </script>
>
>
> Sincerely,
>
> Paul Moebius | Vice President | Digital One Color ~ Graphics Reimagined
>
>
> #############################################################
> This message is sent to you because you are subscribed to
>  the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>
>
>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: How would you have KNOP pass 2 variables to a php include?

Paul Moebius-3
Exactly… using KNOP Framework I am retrieving some variables from fields my database ( $p )

This should work

var: 'my_pid' = ($p -> (field: -fieldname='_id_display'));
var: 'my_mp' = ($p -> (field: -fieldname='MagicPassword'))


<script type="text/javascript" charset="utf-8">
        $().ready(function() {
                var elf = $('#elfinder').elfinder({
                        url : '/_plugins/elfinder/php/connector.php?mp=[encode_url($my_mp) + '&pid=' + encode_url($my_pid)]'
                }).elfinder('instance');
        });
</script>


 
Sincerely,
 
 
Paul Moebius | Vice President | Digital One Color ~ Graphics Reimagined





On Nov 26, 2012, at 2:54 PM, Jolle Carlestam <[hidden email]> wrote:

> I don't understand the question.
>
> Knop does not handle variables per se. That is a Lasso thing. And Lasso, or Knop, can not directly manipulate PHP variables. It can however provide vars as content for get or post params that could be brought along with an AJAX call.
>
> Here's one way of doing that. I'm assuming Lasso 8.
> <?LassoScript
>
> var('my_mp' = 'My MP content');
> var('my_pid' = 'My PID content');
>
> /* ... more code ... */
>
> ?>
> <script type="text/javascript" charset="utf-8">
> $().ready(function() {
> var elf = $('#elfinder').elfinder({
> url : '/_plugins/elfinder/php/connector.php?mp=[encode_url($my_mp) + '&pid=' + encode_url($my_pid)]'
> }).elfinder('instance');
> });
> </script>
>
> NB! The above assumes you don't need square brackets in your javascript code. ANd you need for the PHP file to convert the get params to proper vars.
>
> HDB
> Jolle
>
> 27 nov 2012 kl. 08:40 skrev Paul Moebius <[hidden email]>:
>
>> How would you have KNOP pass 2 variables to a php include?
>> I want to pass to variables $MP and $PID
>> to the connector.php
>>
>>
>> <script type="text/javascript" charset="utf-8">
>> $().ready(function() {
>> var elf = $('#elfinder').elfinder({
>>
>>
>> url : '/_plugins/elfinder/php/connector.php'  
>>
>>
>> }).elfinder('instance');
>> });
>> </script>
>>
>>
>> Sincerely,
>>
>> Paul Moebius | Vice President | Digital One Color ~ Graphics Reimagined
>>
>>
>> #############################################################
>> This message is sent to you because you are subscribed to
>> the mailing list Lasso
>> [hidden email]
>> To unsubscribe, E-mail to: <[hidden email]>
>> Send administrative queries to  <[hidden email]>
>>
>>
>
> #############################################################
> This message is sent to you because you are subscribed to
>  the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: How would you have KNOP pass 2 variables to a php include?

Jolle Carlestam-3
27 nov 2012 kl. 09:04 skrev Paul Moebius <[hidden email]>:

> This should work
>
> var: 'my_pid' = ($p -> (field: -fieldname='_id_display'));
> var: 'my_mp' = ($p -> (field: -fieldname='MagicPassword'))


As will this. Trust me. You will want to make the jump to a parens syntax at some point. Might just as well start now.

var('my_pid' = $p -> field('_id_display'));
var('my_mp' = $p -> field('MagicPassword'));

Same result, better syntax. And, yes, this is Lasso 8 syntax.

HDB
Jolle
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: How would you have KNOP pass 2 variables to a php include?

Tim Taplin
In reply to this post by Jolle Carlestam-3
I would agree with Jolle's suggestion.

However, while I'm not familiar with the specific function you are using, normally, this type of js function would also have support for a parameter that takes the input parameters, and you would need to use similar methods to those Jolle has proposed to insert your variables into that item.

If you have control over the design of this elfinder js function, we may be able to organize it to make inserting lasso values more simple.

Tim Taplin

On Nov 26, 2012, at 3:54 PM, Jolle Carlestam <[hidden email]> wrote:

> I don't understand the question.
>
> Knop does not handle variables per se. That is a Lasso thing. And Lasso, or Knop, can not directly manipulate PHP variables. It can however provide vars as content for get or post params that could be brought along with an AJAX call.
>
> Here's one way of doing that. I'm assuming Lasso 8.
> <?LassoScript
>
> var('my_mp' = 'My MP content');
> var('my_pid' = 'My PID content');
>
> /* ... more code ... */
>
> ?>
> <script type="text/javascript" charset="utf-8">
> $().ready(function() {
> var elf = $('#elfinder').elfinder({
> url : '/_plugins/elfinder/php/connector.php?mp=[encode_url($my_mp) + '&pid=' + encode_url($my_pid)]'
> }).elfinder('instance');
> });
> </script>
>
> NB! The above assumes you don't need square brackets in your javascript code. ANd you need for the PHP file to convert the get params to proper vars.
>
> HDB
> Jolle
>
> 27 nov 2012 kl. 08:40 skrev Paul Moebius <[hidden email]>:
>
>> How would you have KNOP pass 2 variables to a php include?
>> I want to pass to variables $MP and $PID
>> to the connector.php
>>
>>
>> <script type="text/javascript" charset="utf-8">
>> $().ready(function() {
>> var elf = $('#elfinder').elfinder({
>>
>>
>> url : '/_plugins/elfinder/php/connector.php'  
>>
>>
>> }).elfinder('instance');
>> });
>> </script>
>>
>>
>> Sincerely,
>>
>> Paul Moebius | Vice President | Digital One Color ~ Graphics Reimagined
>>
>>
>> #############################################################
>> This message is sent to you because you are subscribed to
>> the mailing list Lasso
>> [hidden email]
>> To unsubscribe, E-mail to: <[hidden email]>
>> Send administrative queries to  <[hidden email]>
>>
>>
>
> #############################################################
> This message is sent to you because you are subscribed to
>  the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: How would you have KNOP pass 2 variables to a php include?

Paul Moebius-3
In reply to this post by Jolle Carlestam-3
What about retrieving them in the connector.php

Wouldn't one need to capture these via at GET function?


<?php
var: 'pid' = GET  $pid;
var: 'mp' = GET   $mp;

'user' => $pid,
'pass' => $mp,
               

 

Sincerely,
 
 
Paul Moebius | Vice President | Digital One Color ~ Graphics Reimagined



On Nov 26, 2012, at 3:10 PM, Jolle Carlestam <[hidden email]> wrote:

> 27 nov 2012 kl. 09:04 skrev Paul Moebius <[hidden email]>:
>
>> This should work
>>
>> var: 'my_pid' = ($p -> (field: -fieldname='_id_display'));
>> var: 'my_mp' = ($p -> (field: -fieldname='MagicPassword'))
>
>
> As will this. Trust me. You will want to make the jump to a parens syntax at some point. Might just as well start now.
>
> var('my_pid' = $p -> field('_id_display'));
> var('my_mp' = $p -> field('MagicPassword'));
>
> Same result, better syntax. And, yes, this is Lasso 8 syntax.
>
> HDB
> Jolle
> #############################################################
> This message is sent to you because you are subscribed to
>  the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: How would you have KNOP pass 2 variables to a php include?

Jolle Carlestam-3
27 nov 2012 kl. 09:22 skrev Paul Moebius <[hidden email]>:

> What about retrieving them in the connector.php
>
> Wouldn't one need to capture these via at GET function?

Yes, one would.

HDB
Jolle
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: How would you have KNOP pass 2 variables to a php include?

Paul Moebius-3
Worked like a charm...

<script type="text/javascript" charset="utf-8">
                        $().ready(function() {
                                var elf = $('#elfinder').elfinder({

                                        url : '/_plugins/elfinder/php/connector.php?mp=[encode_url($my_mp)+'&pid=' + encode_url($my_pid)]'
                               
                                }).elfinder('instance');
                        });
</script>


// passed to the connector.php ------->


<?php
                'user' => $_GET["pid"],
                'pass' => $_GET["mp"],
?>




On Nov 26, 2012, at 5:01 PM, Jolle Carlestam <[hidden email]> wrote:

> 27 nov 2012 kl. 09:22 skrev Paul Moebius <[hidden email]>:
>
>> What about retrieving them in the connector.php
>>
>> Wouldn't one need to capture these via at GET function?
>
> Yes, one would.
>
> HDB
> Jolle
> #############################################################
> This message is sent to you because you are subscribed to
>  the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: How would you have KNOP pass 2 variables to a php include?

Jolle Carlestam-3
27 nov 2012 kl. 14:50 skrev Paul Moebius <[hidden email]>:

> Worked like a charm...

Glad I could help.

HDB
Jolle
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

RE: Lasso, MySQL and Encoding

stevepiercy
In reply to this post by Rob Brooks
On 11/26/12 at 4:04 PM, [hidden email] (Rob Brooks) pronounced:

>Questions:
>
>1.  I'm guessing there isn't a server wide setting that would solve having
>to use the -tablencoding='utf-8' option in the host array in every inline in
>Lasso 8.6 (must now change many, many inlines to internationalize)?  Surely
>someone would have mentioned this  :-)

Correct.  There is no Easy button in 8.x.  :)

In Lasso 8.5.x, I switched to using -host connections because I
got tired of mucking around in Lasso Security and because of
encoding issues.  It's been mentioned a few times.

>2.  Is there such a setting in Lasso 9 or a change in methods for handling
>UTF8 encoding with MySQL?

I just ran some testing to try to break this in Lasso 9 ("I void
warranties").  I used a regular Lasso inline using the -database
connection method instead of -host:

     inline(
         -database   = #d,
         -table      = #t,
         -username   = #u,
         -password   = #p,
         -search,
         -maxrecords='all');

and it returned beautiful Chinese characters.  Next I tried
saving the file with UTF-8 no BOM and about a half-dozen other
encodings.  Same beautiful Chinese characters.  *shrug*

In both 8 and 9, I always do:

* Save all Lasso script files as UTF-8 with BOM
* Use -host connection method in inlines

The Lasso Admin settings from Lasso 8 do not apply in Lasso 9.  
It's vastly simpler.

--steve

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
Steve Piercy               Web Site Builder              
Soquel, CA
<[hidden email]>                  <http://www.StevePiercy.com/>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Lasso, MySQL and Encoding

Jolle Carlestam-3
27 nov 2012 kl. 19:28 skrev "Steve Piercy - Web Site Builder" <[hidden email]>:

>
> In both 8 and 9, I always do:
>
> * Save all Lasso script files as UTF-8 with BOM

In Lasso 9 there is no longer any need to use BOM. In fact it can be a hindrance once you start playing with LassoApps.



HDB
Jolle

Sent from a thin, flat, touchy device from an undetermined place in space.

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Lasso, MySQL and Encoding

Brad Lindsay-2
On Nov 27, 2012, at 7:52 AM, Jolle Carlestam <[hidden email]> wrote:

> 27 nov 2012 kl. 19:28 skrev "Steve Piercy - Web Site Builder" <[hidden email]>:
>
>>
>> In both 8 and 9, I always do:
>>
>> * Save all Lasso script files as UTF-8 with BOM
>
> In Lasso 9 there is no longer any need to use BOM. In fact it can be a hindrance once you start playing with LassoApps.

Also a hindrance if you're creating a shell script whose first line needs to be #! /path/to/lasso9

Brad

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
12