Charset problems with .lc web page

Tim Selander selander at tkf.att.ne.jp
Thu Dec 24 08:25:33 EST 2015


Hi Alex,

Got it!

The .lc file shows:
/usr/local/cpanel/cgi-sys/livecode-server-6.6.2

The .irev file shows
/usr/local/cpanel/cgi-sys/ireviam-engine

And the .irev file continues to show utf-8 (Japanese) correctly 
while the .lc file does not. Actually tested it with the exact 
same file, simply re-tagging the <?lc as <?rev in the file, and 
changing the file extension to .irev. All other content in the 
file untouched.

.irev works, and .lc doesn't.

This is true even when I tried Lyn's suggestion of adding the 
charset command right in the <?lc script.

I wonder if this is a bug? (Not that I know how to report it if 
it is!)

At this point, I'm content to use .irev & <?rev

Thanks all,

Tim Selander
Tokyo, Japan



On 12/24/15, 17:37, Alex Tweedly wrote:
> Sorry Tim, I should have been clearer - it is literally 
> $_SERVER["SCRIPT_FILENAME"] that you want to print.
> That's one of the built-in $_SERVER variables, showing which 
> 'cgi' script (i.e. which version of the engine is running).
>
> So you'll get something like
>
>   /usr/local/cpanel/cgi-sys/livecode-server-6.6.2
>
> -- Alex.
>
> On 24/12/2015 08:33, Tim Selander wrote:
>> Hi Alex,
>>
>> Thanks.
>>
>> I added
>> <?lc put $_SERVER["http://www.pba.on-rev.com/5_today.lc"] & 
>> "<br>" & CR ?>
>>
>> and also
>> <?lc put $_SERVER["5_today.lc"] & "<br>" & CR ?>
>>
>> in the script but it didn't return any info.
>>
>> I'm using On-Rev, the server is sage -- so whatever installs 
>> they have is what I'm using. I do find it curious that the 
>> older .irev works while .lc does not!
>>
>> Tim
>>
>>
>> On 15/12/24 17:18, Alex Tweedly wrote:
>>> Hi Tim,
>>>
>>> I'm afraid I know little or nothing about charsets, so I 
>>> can't directly help :-)
>>>
>>> The difference between .irev and .lc is which version of the 
>>> server engine they are running - and obviously that depends 
>>> on your server setup. So, to help with answering this, we 
>>> (might) need to know which versions are being used on your 
>>> server.
>>>
>>> You could add
>>>    put $_SERVER[" SCRIPT_FILENAME"] & "<br>" & CR
>>>
>>> Presumably it will be a pre-Unicode and a post-Unicode 
>>> version - but knowing which ones might help someone answer 
>>> your question.
>>>
>>> -- Alex.
>>>
>>>
>>> On 24/12/2015 07:55, Tim Selander wrote:
>>>> Dear list,
>>>>
>>>> I'm having trouble making a .lc web pages correctly show the 
>>>> charset.
>>>>
>>>> I have two test files:
>>>> http://www.pba.on-rev.com/5_today.lc
>>>> http://www.pba.on-rev.com/5_today.irev
>>>>
>>>> They are identical except for the .lc/.irev file extensions, 
>>>> and also the <?lc ?> and <?rev ?> tags in the html.
>>>>
>>>> The .irev file correctly shows Japanese UTF8, the .lc file 
>>>> does not.
>>>>
>>>> Anyone else having problems with this? Can .lc files not 
>>>> handle charset correctly?
>>>>
>>>> Thanks,
>>>>
>>>> Tim Selander
>>>> Tokyo, Japan
>>>>
>>>> _______________________________________________
>>>> use-livecode mailing list
>>>> use-livecode at lists.runrev.com
>>>> Please visit this url to subscribe, unsubscribe and manage 
>>>> your subscription preferences:
>>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>>
>>> _______________________________________________
>>> use-livecode mailing list
>>> use-livecode at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage 
>>> your subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>>
>>
>>
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage 
>> your subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your 
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>





More information about the Use-livecode mailing list