Hi Mac Livecoders,
I have a working solution (alpha stage).
For those interested, please contact me off-list
Regards,
Thierry
2014/1/10 J. Landman Gay :
>
> On 1/10/14 12:00 PM, Ender Nafi Elekcioglu wrote:
>
>> There isn’t any workaround, I guess :/ so, we’ll wait Livecode 7 and
>> in the m
On 10/01/14 17:29, Richard Gaskin wrote:
Richmond wrote:
It shouldn't be necessary to ask these questions; ASCII went out with
the ark,
and in this respect Livecode is seriously backward.
Yes, one might be tempted to think that the folks at RunRev took our
three-quarters-of-a-million-dollars
Hello Jacque,
Thanks for your effort.
I suggested it to my customer, they didn’t accept it.
They are a bit *dummkopf*, sorry for that but they’re what they are :)
Though, I have a dedicated folder for the mobile app in the ftp server.
Now, a colleague of mine {web guy} is trying to create a
On 1/10/14 12:00 PM, Ender Nafi Elekcioglu wrote:
There isn’t any workaround, I guess :/ so, we’ll wait Livecode 7 and
in the meantime find a way to dodge customers’ complaints :)
I tried several things yesterday and couldn't make it work either. Would
it be possible for you to run a script o
Martin,
I’ve tried it, for test purposes of course because it’s no use in iOS; though
still no luck.
_answer file “select file…”
_put it into tFilename
_set the filename of image 1 to tFilename
_put tFilename & cr & the filename of image 1 into field 1
Results are same, Ascii-255 works fi
Richmond wrote:
It shouldn't be necessary to ask these questions; ASCII went out with
the ark,
and in this respect Livecode is seriously backward.
Yes, one might be tempted to think that the folks at RunRev took our
three-quarters-of-a-million-dollars and simply went to the beach in the
sout
On 10/01/14 02:28, Ender Nafi Elekcioglu wrote:
> The situation starts to be clarified a little bit.
>
> First, if *ağaç.txt* opens in Linux as Martin stated but not in OS X and iOS,
> then the underlying OS has a big role.
>
> It seems that in OS X and iOS, Livecode accepts only those chars w
It shouldn't be necessary to ask these questions; ASCII went out with
the ark,
and in this respect Livecode is seriously backward.
Richmond.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe an
Read as:
“resistance is futile, give up!” :)
~ Ender
On Jan 10, 2014, 4:38:44, Mark Wieder wrote:
I once managed on a Windows system to create a file whose name had a
trailing space, and nothing I could do would delete the entry. I tried
all the low-level hacks I could find. When Windows f
On Jan 9, 2014, at 6:38 PM, Mark Wieder wrote:
>
> I once managed on a Windows system to create a file whose name had a
> trailing space, and nothing I could do would delete the entry. I tried
> all the low-level hacks I could find. When Windows finally died I
> didn't bother to reinstall it. I t
Ender-
Thursday, January 9, 2014, 6:28:06 PM, you wrote:
> First, if *agaç.txt* opens in Linux as Martin stated but not in
> OS X and iOS, then the underlying OS has a big role.
I once managed on a Windows system to create a file whose name had a
trailing space, and nothing I could do would de
The situation starts to be clarified a little bit.
First, if *ağaç.txt* opens in Linux as Martin stated but not in OS X and iOS,
then the underlying OS has a big role.
It seems that in OS X and iOS, Livecode accepts only those chars with a unicode
hex point up to U+00FF;
That’s why *épøtç†.
/johndixon/Desktop/épøtç†.png
> Date: Fri, 10 Jan 2014 00:53:59 +
> From: mblivec...@harbourhosting.co.uk
> To: use-livecode@lists.runrev.com
> Subject: Re: Non-Ascii Chars in Filenames
>
> On 09/01/14 23:43, Ender Nafi Elekcioglu wrote:
> > Hi,
> >
> > Is th
On 09/01/14 23:43, Ender Nafi Elekcioglu wrote:
> Hi,
>
> Is there any way to deal with files whose filenames contain non-ascii chars?
> Assume that *tFilename* is *specialFolderPath(“desktop”) & “/ağaç.png”*
>
> _set the filename of image 1 to tFilename
> results with an empty image.
>
>
Thanks for asking this question Ender. I don't have an answer but will
benefit from it as well.
Phil Davis
On 1/9/14, 3:43 PM, Ender Nafi Elekcioglu wrote:
Hi,
Is there any way to deal with files whose filenames contain non-ascii chars?
Assume that *tFilename* is *specialFolderPath(“desktop”
Hi,
Is there any way to deal with files whose filenames contain non-ascii chars?
Assume that *tFilename* is *specialFolderPath(“desktop”) & “/ağaç.png”*
_set the filename of image 1 to tFilename
results with an empty image.
_set the filename of image 1 to URLEncode(tFilename)
same, an em
16 matches
Mail list logo
