Not to my knowledge, but I'm sure it's completely doable. I once created an
LC script that could extract embedded JPEGs from inside PDFs. The PDF File
Format docs have been made available by Adobe (back in 2011 I think).
Another option would be to use Shell() function with one of the PDF
command-l
> Richard H. wrote:
> Silly question now that I think of it . . . does t avoid
> the pixelization that the pdf widget performs?
> And for that matter, does it work with cropped sections,
> or just full pages?
The PDf-lib doesn't use image snapshots. It is true PDF:
Copied are pages and all it need
Silly question now that I think of it . . . does t avoid the pixelization that
the pdf widget performs?
And for that matter, does it work with cropped sections, or just full pages?
—
Richard E. Hawkins, Esq.
The Hawkins Law Firm
3430 E. Flamingo Rd.
Suite 232
Las Vegas, NV 89121
(702) 508-846
On Oct 21, 2019, at 10:55 AM, hh via use-livecode
wrote:
>
> I had it ready yesterday for Mac and tried a full day to work
I’ll start pounding the mac version was soon as I get my hands on it . .
—
Richard E. Hawkins, Esq.
The Hawkins Law Firm
3430 E. Flamingo Rd.
Suite 232
Las Vegas, NV 8
It is dependant on using JS from LC, by that it is dependant
on a browser widget.
I had it ready yesterday for Mac and tried a full day to work
around the deficiencies of the browser widget on linux and win
but had no success, sorry.
The stack will be published as "PDF-Tools" (Merge/Mix/Split)
in
doc hawk wrote:
> On Oct 17, 2019, at 12:04 PM, hh wrote:
>> I'll publish this weekend on SampleStacks a pdfLib (split and merge)
>> based on a JS library (via a browser widget). Already 95% are done.
>
> Did it publish?
>
> And will this only be for server?
If it's dependent on a browser widget,
On Oct 17, 2019, at 12:04 PM, hh via use-livecode
wrote:
> I'll publish this weekend on SampleStacks a pdfLib (split and merge)
> based on a JS library (via a browser widget). Already 95% are done.
Did it publish?
And will this only be for server?
Do I sound anxious?
:)
> Hugh Senior wrote:
> Has anyone got an LC-based method to merge pdf files? Just asking...
I'll publish this weekend on SampleStacks a pdfLib (split and merge)
based on a JS library (via a browser widget). Already 95% are done.
___
use-livecode mailing
On Oct 17, 2019, at 9:27 AM, FlexibleLearning.com via use-livecode
wrote:
>
> Has anyone got an LC-based method to merge pdf files?
LC business can’t even output a pdf widget save as low density raster at the
moment.
I’m currently working on an interim solution that creates a PyPdf2 script,
-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 a
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 su
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 & t
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 a
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 1:
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, which
:)
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 the
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. Clear
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 Scot
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
Pl
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
> wr
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 th
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 th
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 wher
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 i
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 Du
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 mean
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 me
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 metada
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
Cool, thanks!
On Fri, Jun 15, 2018 at 7:58 PM Brian Milby wrote:
> I think that as long as you control the string that is passed to merge you
> should be fine. But if the user were able to directly influence the string
> that is passed to merge, then they certainly could inject something.
>
> p
I think that as long as you control the string that is passed to merge you
should be fine. But if the user were able to directly influence the string
that is passed to merge, then they certainly could inject something.
put the text of field 1 into tMerge
put merge(tMerge) into tDangerousUse
put m
On Wed, Aug 2, 2017 at 1:00 PM, Mark Waddingham via use-livecode <
use-livecode@lists.runrev.com> wrote:
> If you evaluate the second expression in that merge in the context (i.e.
> Same handler) of the call to merge does it throw an error?
>
Ahh, it was viciously subtle (and visibly taunting)
I
If you evaluate the second expression in that merge in the context (i.e. Same
handler) of the call to merge does it throw an error?
If a compile or runtime error occurs in any [[ ... ]] bracketed part of the
merge string, then it gets rendered literally and not the value of it (as it
can't be e
36 matches
Mail list logo
