-livecode-boun...@lists.runrev.com] On Behalf
Of J. Landman Gay via use-livecode
Sent: Wednesday, September 11, 2019 4:54 PM
To: How to use LiveCode
Cc: J. Landman Gay
Subject: Re: Merge and unicode
On 9/11/19 12:28 AM, Richard Gaskin via use-livecode wrote:
> I'll wager using a styledText ar
On 9/11/19 12:28 AM, Richard Gaskin via use-livecode wrote:
I'll wager using a styledText array for this will be fun to write and will
perform very well.
I took a look. You'd win that wager. I didn't test performance (haven't
written the handler yet) but getting the styledText of an existing
I'll wager using a styledText array for this will be fun to write and will
perform very well.Richard GaskinFourth World Systems
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
I wondered about using htmltext in the merge too, but before I started
using merge I was setting the properties one by one in a handler. Here's
part of my original handler, where pResults is a list of lines that
match search criteria:
repeat for each line l in pResults
put item 1 of l &
Because htmlText does not set the metadata to interesting characters, you can
consider this workaround:
Change the quotes in tCONCEPT to and . And, thus, in tMETADATA.
> On Sep 10, 2019, at 12:47 PM, J. Landman Gay via use-livecode
> wrote:
>
> :)
> 1. Jacque is very confused too, but is
I looked at this some more on OS X. I'm not seeing a problem with merge. And
I'm not seeing a problem with metadata per se, I don't think. But I am seeing a
problem with setting metadata with htmlText.
> On Sep 10, 2019, at 1:32 PM, J. Landman Gay via use-livecode
> wrote:
>
> On 9/10/19
On 9/10/19 1:47 PM, J. Landman Gay via use-livecode wrote:
:)
1. Jacque is very confused too, but is afraid of big sticks.
2. Encoding should be identical throughout. I'm working with a large
text block, pulling out sections to create a list. All data is retrieved
from othe same variable,
:)
1. Jacque is very confused too, but is afraid of big sticks.
2. Encoding should be identical throughout. I'm working with a large
text block, pulling out sections to create a list. All data is retrieved
from othe same variable, which is UTF16 native LC text.
3. The metadata is only set at
I extracted an example. The main issue is curly quotes. The text came
from FileMaker in UTF8, which I textDecode to UTF16. You can assume that
all text is LC native throughout the app.
Here is the template I use for merge:
size="16" color="#C77C02">[[tSECTION]][[tCONCEPT]]
In the field, this
Jacque, these are my latest thoughts as far as possible problems.
1. Dar is very confused and off in the wrong direction. Use big stick.
2. Binary data is in an 8-bit char set encoding causing problems with UTF-8
decode. Check encoding.
3. Field, line and character metadata are interfering.
Trusting...
Also, interpreting Latin-1 as UTF-8 can generate some weird characters and lots
of ?-diamond symbols.
> On Sep 10, 2019, at 8:36 AM, Bob Sneidar via use-livecode
> wrote:
>
> Trust me it's better than a feral gander persuit.
>
> Bob S
>
>
>> On Sep 9, 2019, at 17:23 , Dar
Trust me it's better than a feral gander persuit.
Bob S
> On Sep 9, 2019, at 17:23 , Dar Scott Consulting via use-livecode
> wrote:
>
> Sorry, if I am off on a bunny trail...
>
> Dar
___
use-livecode mailing list
use-livecode@lists.runrev.com
I think I'm doing this wrong. This seems to work, too.
on mouseup
put empty into field 1
put numToCodepoint(0x2200) into x
put numToCodepoint(0x1040F) & "V-" into y
put merge(" é{ [[x]] }é [[y]]") into field 1
end mouseup
> On Sep 9, 2019, at 10:25 PM, dsc--- via use-livecode
>
And this, too, looks OK to me.
on mouseup
put empty into field 1
put "A" into field 1
get numToCodepoint(0x2200) & numToCodepoint(0x1040F) & "V-"
set the metadata of char 1 of field 1 to it
put the metadata of char 1 of field 1 after field 1
end mouseup
I guess the problem is in
This quick check seems to work for me.
on mouseup
put "A" into field 1
set the metadata of char 1 of field 1 to "é"
put the metadata of char 1 of field 1 after field 1
end mouseup
> On Sep 9, 2019, at 8:32 PM, J. Landman Gay via use-livecode
> wrote:
>
> Well, I've made some changes to
Well, I've made some changes to the code since I started urlEncoding the
text before merging so I'll check that again. Paul is right that unicode in
htmltext needs to be in hex, but the numbers I'm getting back are very high
(8,000+) and render in the field as strange pictographs. Elsewhere
I think you are trying to think too much about the LC implementation of text.
Maybe.
Text in LC is an abstraction of a sequence of code points. Whether it is UTF16
or not is hidden to me. (mostly)
So,
get textDecode( binaryFromServer, "UTF-8" )
should put that into the correct form, if
Doesn't any Unicode in htmlText of a field need to be in HTML form (i.e.
#;?
I thought htmlText turns any non ASCII into either hex encoded html or,
where html entity names exists, uses html entity names.
On 9/9/2019 6:35 PM, J. Landman Gay via use-livecode wrote:
On 9/9/19 2:39 PM, Paul
It's UTF8 text from a server, which I textDecode to UTF16. When I use
the UTF16 text in a merge, diacriticals and/or curly quotes get mangled.
(Same with setting metadata on field text too.)
On 9/9/19 4:16 PM, Dar Scott Consulting via use-livecode wrote:
I'm not sure I understand.
Do you
On 9/9/19 2:39 PM, Paul Dupuis via use-livecode wrote:
On 9/9/2019 2:13 PM, J. Landman Gay via use-livecode wrote:
On 9/9/19 1:08 PM, J. Landman Gay via use-livecode wrote:
It seems that the merge command doesn't respect unicode. Does anyone
have a workaround? The text I'm inserting is already
I'm not sure I understand.
Do you mean "encoded to UTF-16"? In that case you should decode that to convert
it to internal text. And then try merge. (Which still might have problems, I
suppose.)
> On Sep 9, 2019, at 12:08 PM, J. Landman Gay via use-livecode
> wrote:
>
> It seems that the
On 9/9/2019 2:13 PM, J. Landman Gay via use-livecode wrote:
On 9/9/19 1:08 PM, J. Landman Gay via use-livecode wrote:
It seems that the merge command doesn't respect unicode. Does anyone
have a workaround? The text I'm inserting is already decoded to UTF16.
I misspoke, sorry. It's the
On 9/9/19 1:08 PM, J. Landman Gay via use-livecode wrote:
It seems that the merge command doesn't respect unicode. Does anyone
have a workaround? The text I'm inserting is already decoded to UTF16.
I misspoke, sorry. It's the metadata that doesn't respect unicode.
--
Jacqueline Landman Gay
It seems that the merge command doesn't respect unicode. Does anyone
have a workaround? The text I'm inserting is already decoded to UTF16.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
24 matches
Mail list logo
