A few ideas: 1. Maybe whatever char you get back from 'the files' will work. If you need to process the files in a folder just look at the files and look for a pattern that ignores the delimiter. Or take the file list and convert colon and numToChar(240) to "/" and then process.
2. I'm assuming that files saved on Windows have the dot, numtoChar(240), and files saved on Mac have the colon. But files saved on Windows but read from a Mac have the dot look like eth, numToChar(240). The different views are because of the different encodings used. I might have some bad assumptions in there. If you are building names, then just use numToChar(240) for your date delimiter to get files saved on Windows. The dot and the eth are just two ways of interpreting 240. It will look like dot on Windows and eth on Mac. If I'm understanding your situation right. So, just use numToChar(240) as the delimiter blindly when getting the file that was saved on a Windows machine and ":" when getting the file when saved on a Mac. If you are not sure which, try one then the other. 3. Maybe somebody has an idea on how to use '"?" in a file name to match those. 4. Or, maybe, I realize this might be hard, have the doctor use some other character. Dar On Jul 19, 2013, at 2:27 AM, André Bisseret wrote: > Thank you much Dar for your reply. > > This morning I tried on Windows: > replace ":" with numToChar(240) in tDocName > no success > > but, actually, when I past the mysterious char (kind of period) in the > message box, I get "ð > I mean I get quote followed by ð > So I tried > put quote & numToChar(240) into tVar > replace ":" with tVar in tDocName > again no success > > When I paste the mysterious char directly in the script it is immediately > replaced by "?" > so I tried > replace ":" with "?" in tDocName > no success > > I am completely lost. > What could I do? > > Thanks in advance for any suggestion > > Best regards > > André > > > > > Le 18 juil. 2013 à 22:47, Dar Scott a écrit : > >> That is a lower case eth. The Unicode is 00F0, F0 in Latin-1. Windows uses >> some other font encoding. >> >> You might be able to use that character directly whatever it looks like. >> Windows will just see the code for it. On Windows. >> >> If it was saved to Windows and you are looking at it on Mac, then it might >> look different. In all cases, if saved on Windows, then try numToChar(240) >> whatever it looks like. >> >> Similarly, if it was saved on Mac, use the appropriate numToChar( ...). >> >> Dar >> >> >> On Jul 18, 2013, at 1:57 PM, André Bisseret wrote: >> >>> ð >> >> _______________________________________________ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
