On Tue, Sep 24, 2013 at 12:32 AM, BNig wrote:
> apparently 8232 is not recognized by Livecode's HTML-parser as linebreak.
>
> So it is probably a Livecode problem
>
> Kind regards
> Bernd
>
Thanks so much for finding this. I was starting to feel foolish. Now I have
something to report to QC.
th
Just noticed that the post did not show the most important information:
the htmlText of the first two paragraphs of your website show at the
paragraph end
groove.ampersand hashmark 8232 semicolon ampersand hashmark 8232 semicolon
The 2013
apparently 8232 is not recognized by Livecode's HTML-par
Stephen,
if I copy from your page the first two paragraphs from Safari into a
LiveCode field resulting in the behavior you describe and then look at the
htmlText of that field it says
groove.
The 2013
apparently Safari serves the line breaks as
which means linebrake
and Livecode's HTML-pars
Stephen-
Monday, September 23, 2013, 7:56:58 PM, you wrote:
> I still like Safari and Webkit
All modern browsers are webkit-based.
--
-Mark Wieder
mwie...@ahsoftware.net
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit thi
yes, it's very possible I've made a total ass out of myself.
On Mon, Sep 23, 2013 at 8:21 PM, Jerry Jensen wrote:
> Straw. Camel's back.
>
>
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe
Straw. Camel's back.
On Sep 23, 2013, at 7:56 PM, stephen barncard
wrote:
> Please don't let particular my problem change your attitude about Safari. I
> am trying to see if it's my web coding. Currently the text on that page is
> placed there with PUT statements and livecode server. I was usin
Please don't let particular my problem change your attitude about Safari. I
am trying to see if it's my web coding. Currently the text on that page is
placed there with PUT statements and livecode server. I was using for
returns and for a new paragraph, which is bad form, but easier to
code with
Jerry-
Monday, September 23, 2013, 5:48:38 PM, you wrote:
> Geez, I'm about to stop using Safari. Running Firefox only when
> something doesn't work in Safari is getting old. I think I'll just
> recommend that people I support start using Firefox by default.
...and Firefox is such a memory hog t
Geez, I'm about to stop using Safari. Running Firefox only when something
doesn't work in Safari is getting old. I think I'll just recommend that people
I support start using Firefox by default.
.Jerry
On Sep 23, 2013, at 5:44 PM, stephen barncard
wrote:
> On Mon, Sep 23, 2013 at 4:25 PM, ste
On Mon, Sep 23, 2013 at 4:25 PM, stephen barncard <
stephenrevoluti...@barncard.com> wrote:
> Should this be reported as a bug? I'm surprised this hasn't happened to
> anyone else...
Here's the next wrinkle : The problem manifests with Safari, but not
Google Chrome or Firefox.gr
--
Tested with LC 6.1.1 and 5.5.5 - same thing
by the way, pasting back from the pasted text of Tex-Edit or TextMate back
to LC looks fine as well.
Should this be reported as a bug? I'm surprised this hasn't happened to
anyone else...
On Mon, Sep 23, 2013 at 4:21 PM, stephen barncard <
stephenre
Directly pasting into an LC field produces the exact same result. Wrong.
On Mon, Sep 23, 2013 at 4:18 PM, stephen barncard <
stephenrevoluti...@barncard.com> wrote:
> Thanks Scott,
> I know how to screen scrape from the html source...
>
> I want to use the contents of the clipboard to just get t
Thanks Scott,
I know how to screen scrape from the html source...
I want to use the contents of the clipboard to just get the part I need.
And this return business is getting in the way I get a block of text
with question marks instead of returns. I'm not sure how actual question
marks show
Do you have to use the copied text or can you use the source HTML text?
set text of fld 1 to url "http://jazzcubed.com/";
Regards,
Scott Rossi
Creative Director
Tactile Media, UX/UI Design
On 9/23/13 3:27 PM, "stephen barncard"
wrote:
>HI gang,
>
>I'm having trouble in pasting copied text
14 matches
Mail list logo
