[ANN] This Week in LiveCode 264

[panagiotis merakos via use-livecode]

Hi all,

Read about new developments in LiveCode open source and the open source
community in today's edition of the "This Week in LiveCode" newsletter!

Read issue #264 here: https://bit.ly/3o8bBhk

This is a weekly newsletter about LiveCode, focussing on what's been
going on in and around the open source project. New issues will be
released weekly on Mondays. We have a dedicated mailing list that will
deliver each issue directly to your e-mail, so you don't miss any!

If you have anything you'd like mentioned (a project, a discussion
somewhere, an upcoming event) then please get in touch.



-- 
Panagiotis Merakos 
LiveCode Software Developer

Everyone Can Create Apps 
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Finding invisible/non printable characters in a string

[Curry Kenworthy via use-livecode]

David:

> Would I be right in thinking if codepoint count > the number of chars
> in a text string, then it probably contains invisible characters?

Negative; there are other possibilities. Including

Paul:

> There are characters that consist of more than one codepoint -
> composite versions of characters for accents. See
> https://unicode-table.com/en/blocks/combining-diacritical-marks/

Yes! An example would be Hindi: नमस्ते
Which per LC has 6 codepoints and 4 chars.

Another fun accent example is using a "Zalgo" generator:

H̴̱̞͔̺̣̀ĩ̴̱̣̉̀͛̂ͅ ̵͆̒ͅt̷̹̖͖̍͠ḩ̸̛̤̃̄̑̾͝e̵̻̤͙̐̽r̵̙̩̀͂̚̕e̶̗͓̲̞͍̻̎͋͘͠͠

68 codepoints vs 8 chars! Zalgo heaps random accents onto characters.
But as you can see, many languages and notation systems have modifiers.

Typically such accents combine with another character, but thanks to 
the Magic of Bugs you can also see them breaking free and "doing their 
own thing" sometimes, as if they were separate characters, by pasting 
some Thai or Myanmar text into an LC field and resizing that field:


https://quality.livecode.com/show_bug.cgi?id=22373

On the possibility of invisible characters, there is also an LC bug 
which inserts one or more nulls after pasted text on Windows:


https://quality.livecode.com/show_bug.cgi?id=22172

But the nulls count as characters, so the codepoint count still matches. 
I thought there was another category of Unicode values affected besides 
the combining modifiers, but if so, it's eluding me at the moment. :)


Best wishes,

Curry Kenworthy

Custom Software Development
"Better Methods, Better Results"
LiveCode Training and Consulting
http://livecodeconsulting.com/

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Finding invisible/non printable characters in a string

[Kee Nethery via use-livecode]

The ASCII characters at the beginning of the ASCII table (RS, GS, Bell, etc) 
typically display as a box. What you are describing are zero width Unicode 
characters. I think there are four. You could explicitly look for them.

Kee Nethery

> On May 10, 2021, at 7:09 AM, Paul Dupuis via use-livecode 
>  wrote:
> 
> There are characters that consist of more than one codepoint - composite 
> versions of characters for accents. See 
> https://unicode-table.com/en/blocks/combining-diacritical-marks/
> 
> 
> I think the best way is to scan the codepoints looking for codePointToNum 
> values that are 0-31 (exclude tab and cr/lfs if you like) and 127 (DEL). 
> There may be some others in the 128-255 range that are not printable. I 
> forget off the top of my head.
> 
> 
> 
>> On 5/10/2021 5:49 AM, David V Glasgow via use-livecode wrote:
>> Hi folks, hope everyone is well.
>> 
>> Would I be right in thinking if codepoint count > the number of chars in a 
>> text string, then it probably contains invisible characters?
>> 
>> Or would I need to search through Hex to check?
>> 
>> Or something much easier and cleverer that I hadn’t even considered.  
>> Because that’s what this list and working with Livecode is like.
>> 
>> Cheers
>> 
>> David Glasgow
>> ___
>> use-livecode mailing list
>> use-livecode@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@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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Finding invisible/non printable characters in a string

[Paul Dupuis via use-livecode]

There are characters that consist of more than one codepoint - composite 
versions of characters for accents. See 
https://unicode-table.com/en/blocks/combining-diacritical-marks/



I think the best way is to scan the codepoints looking for 
codePointToNum values that are 0-31 (exclude tab and cr/lfs if you like) 
and 127 (DEL). There may be some others in the 128-255 range that are 
not printable. I forget off the top of my head.




On 5/10/2021 5:49 AM, David V Glasgow via use-livecode wrote:

Hi folks, hope everyone is well.

Would I be right in thinking if codepoint count > the number of chars in a text 
string, then it probably contains invisible characters?

Or would I need to search through Hex to check?

Or something much easier and cleverer that I hadn’t even considered.  Because 
that’s what this list and working with Livecode is like.

Cheers

David Glasgow
___
use-livecode mailing list
use-livecode@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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

[ANN] Release 9.6.2 RC-6

[panagiotis merakos via use-livecode]

Dear list members,

We are pleased to announce the release of LiveCode 9.6.2 RC-6.


Getting the Release
===
You can get the release at https://downloads.livecode.com/livecode/ or via
the automatic updater.


Release Contents

LiveCode 9.6.2 RC-6 comes with 3 regression fixes:

- Fix 100% CPU usage when the player control is set to load an unplayable
media file on Macos Big Sur
- Fix rectangle border inset too much when printing on Windows or to PDF
- Ensure externals are not blocked by hardened runtime

For the full list of all fixes, updates and enhancements please see the
release notes:

http://downloads.livecode.com/livecode/9_6_2/LiveCodeNotes-9_6_2_rc_6.pdf


Known issues

- The Browser widget's native layer is not shown in some Linux distros with
Cinnamon window manager.
- The use of the Browser widget is not supported on Ubuntu 18.04 64 bit LTS
yet.


Required Software
=
To build iOS apps with LiveCode you must have the appropriate versions of
Xcode as follows:

  - macOS 10.13.4: Xcode 10.1 - LiveCode builds iOS apps using the iOS 12.1
SDK
  - macOS 10.14.4: Xcode 11.3.x - LiveCode builds iOS apps using the iOS
13.2 SDK
  - macOS 10.15.4+: Xcode 12.1.x - LiveCode builds iOS apps using the iOS
14.1 SDK

There is a full list of working LiveCode/macOS/Xcode combinations here:
https://livecode.com/docs/9-5-0/faq/faq/

Note: Whilst we endeavour to release updated versions of LiveCode
supporting the latest Xcode/iOS SDKs as quickly as possible; we strongly
recommend disabling automatic update of Xcode or downloading the specific
version of Xcode required directly from the Apple developer portal and
installing it separately.

Important: Starting April 26, 2021, all iPhone and iPad apps submitted to
the App Store must be built with Xcode 12 and the iOS 14 SDK or later. This
means that, if you wish to submit apps to the AppStore you will have to be
running at least macOS 10.15.4 in order to be able to install the necessary
version of Xcode.


Feedback

Please report any bugs encountered on our quality center at
http://quality.livecode.com/

We have a forum available for discussing LiveCode Builder at
http://forums.livecode.com/viewforum.php?f=93


Have fun!
The LiveCode Team
--
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Finding invisible/non printable characters in a string

[David V Glasgow via use-livecode]

Hi folks, hope everyone is well.

Would I be right in thinking if codepoint count > the number of chars in a text 
string, then it probably contains invisible characters?  

Or would I need to search through Hex to check?

Or something much easier and cleverer that I hadn’t even considered.  Because 
that’s what this list and working with Livecode is like.

Cheers

David Glasgow
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode