Hey that's nice, thanks!
Bob
On Jan 17, 2013, at 6:32 AM, Klaus on-rev wrote:
> Hi friends,
>
> Am 16.01.2013 um 18:15 schrieb Nishok Love :
>
>> ...
>> So I'm still looking for a way for LiveCode to spot whether it's opening a
>> file in UTF-8 or UTF-16 (or something else - aaarrgh!). Can I
Hi friends,
Am 16.01.2013 um 18:15 schrieb Nishok Love :
> ...
> So I'm still looking for a way for LiveCode to spot whether it's opening a
> file in UTF-8 or UTF-16 (or something else - aaarrgh!). Can I access the file
> header? read from file just gives me the data...
I found an old script t
This is the first time I've asked a question on use-livecode and I've been
pleasantly amazed that people have taken the time to give so much useful advice
- much respect, and thankyou to everyone. I think I now have a solution which
works, and I've learnt some interesting things too.
In summary
I will hazard a guess, that when you open the file for reading, you can open
binary first and see if the first two characters amount to FE FF, yes? If so,
treat as UTF-16. If not, treat as UTF-8. I have not tested this strategy
myself, but your second point seems to give the clue to solve this m
I did not see an RTF export option in Pages. Besides, I think he is dealing
with reading text files, the nature of which he does not control.
Bob
On Jan 16, 2013, at 9:22 AM, Richmond wrote:
> On 01/16/2013 07:15 PM, Nishok Love wrote:
>> Thanks, Bob. Your command works but the same results o
On 01/16/2013 07:15 PM, Nishok Love wrote:
Thanks, Bob. Your command works but the same results occur. Further
investigations here found this
When Pages is used to export as "Text", the resulting file may be of two kinds:
(1) if the document contained only characters included in Apple MacRoman
Thanks, Bob. Your command works but the same results occur. Further
investigations here found this
When Pages is used to export as "Text", the resulting file may be of two kinds:
(1) if the document contained only characters included in Apple MacRoman
charset, the file is a pure text file base
Hi from Beautiful Brittany,
Hi Nishok,
If you are a nit-picker, and REALLY want to know
why you have this problem, then my response is
simple - I don't know !
If you want a work-around, it's simple - select
your text when you are in Word, and paste it into
a new text file (TextEdit), and save it
Bob wrote:
No one has talked about what version of pages.
[on my gmail it got connected to a different thread]
I'm on OS X 10.8.2, LC 5.5.3, Pages 4.3, TextWrangler 4.0.1
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url
On Wed, Jan 16, 2013 at 1:54 PM, J. Landman Gay
wrote:
> If the original was unicode,
Again, TextWrangler can help, at the bottom left of the document it
will show the documents encoding which is also a button that allows
you to change it. On my system a new TW document is created as UTF-8,
when
On 1/15/13 11:49 PM, Paul D. DeRocco wrote:
Is it possible that the original text file is in Unicode, so that each
character in the ASCII set is followed by a null, and something is
converting the nulls into blanks? Possibly the display routine itself?
GMTA. :)
--
Jacqueline Landman Gay
On 1/15/13 11:39 PM, Kay C Lan wrote:
If there is not an extra space after EVERY char, then it becomes much
more difficult.
If the original was unicode, which was then converted to plain text,
Pages might be retaining the second byte and inserting a null. In other
words, it's keeping both of
> From: Kay C Lan
>
> Actually I take that back. If Pages places an extra space after EVERY
> char, so there are two spaces between words instead of one, there is a
> space after the last word on a line but before the carriage return,
> and another space after the carriage return and before the fi
On Wed, Jan 16, 2013 at 1:19 PM, Kay C Lan wrote:
> it would be nigh
> impossible for LC to repair this.
Actually I take that back. If Pages places an extra space after EVERY
char, so there are two spaces between words instead of one, there is a
space after the last word on a line but before the
I did that earlier. There are no encoding options available in the export
dialog. It is possible that based on the system and language settings at the
time the file is exported that the encoding might be set to Unicode, but I
couldn't find anything by googling for it.
Bob Sneidar
IT Manager
Ca
What happens when you open the Pages converted file in TextEdit, does
it have the extra spaces? If so the problem is with the conversion
process from Pages, not with LC. If so you need to look at some of the
conversion options Pages offers and see if you can create the file
without the extra spaces
I have seen the behavior Nishok describes. It was some time ago and I don't
remember what the issue was, but I think it was fixable.
-- Peter
Peter M. Brigham
pmb...@gmail.com
http://home.comcast.net/~pmbrig
On Jan 15, 2013, at 1:54 PM, Robert Sneidar wrote:
> I am not sure why you are seeing
I am not sure why you are seeing this. I exported a pages newsletter file as
text, then ran this command on it:
on mouseUp pMouseBtnNo
answer file "Pick a text file" with
"/Users/bobsneidar/Desktop/SneidarNewsletter.txt"
put it into theFile
open file theFile for read
read from fi
Hi All
I have a problem when I open .txt files in OSX, and I don't have much (any!)
experience of reading files in LiveCode.
I have a file originally written in Word on Windows. When I export it as a .txt
from Word for Mac I just accept the default Mac OS encoding option (Western
(Mac OS Roma
19 matches
Mail list logo
