Thanks to all the folks who tested the new version and gave me feedback. I'm
happy to announce I was able to release the new version tonight that can import
passwords from other programs.
Bill Vlahos
_
InfoWallet (http://www.infowallet.com) is about keeping your important life
i
Dave,
Thanks for the comments.
I won't actually know what the source of the text files will be. The most
common examples will be as export files from any other password management
program on Mac or Windows like 1Password, etc. or as a Save As CSV from Excel.
Bill Vlahos
_
InfoW
On 23 Jan 2012, at 03:16, Bill Vlahos wrote:
> put uniDecode(uniEncode(tData, "UTF8")) into tData
Bill,
Using this approach assumes that the original text is either UTF-8 encoded or
that it is plain ASCII with no "funny" characters with a charToNum value above
127. I don't think it will work
How do you guys know this stuff? Awesome.
Bill
On Jan 22, 2012, at 7:16 PM, Bill Vlahos wrote:
> Mark,
>
> Perfect. That's it!
>
> Coincidentally I also found it in the notes section for Open File by
> rod...@oceanbrowser.com:
>> If you are reading in a text file (for example) which contains
Mark,
Perfect. That's it!
Coincidentally I also found it in the notes section for Open File by
rod...@oceanbrowser.com:
> If you are reading in a text file (for example) which contains high ascii
> values (such as curly quotes - numToChar(210) ) you will find that these are
> displayed as garb
Bill,
on mouseUp
answer file "Import Password Text File" with type "Text|txt"
if it is not empty then
put "binfile:" & it into vPathToFile
put URL vPathToFile into fSource
put unidecode(uniencode(fSource,"UTF8")) into fSource
examineImport fSource
else
exit mouseUp
I wonder what the data would look like if you used a shell() command (or some
other non-LC-code means - via a process maybe) to read it. Like so:
on mouseUp
answer file "Import Password Text File" with type "Text|txt"
if it is not empty then
switch the platform
case "Win32"
Phil,
Binfile doesn't make any difference. I did monkey with the unicode settings and
they were unpredictable. For 8bit unicode the text all came in as special
characters. If the text file was 16 bit then it looked OK except it didn't
parse correctly into the table. Some of the cells had both t
Hi Bill,
What happens if you get the file using "binfile" instead of "file"? And then you
might have to monkey with unidecode() or something. I bet Devin Asay can tell
you in his sleep.
Seems to me "binfile" would prevent any char translation, though it would also
prevent line-ending transla
Thanks to the beta testers they discovered a problem that I don't know how to
fix…unicode.
If the text file contains german umlaute ü,ö,ä. And these characters are not
imported correctly. The ü (u umlaut) for example becomes √º
Here is the code:
on mouseUp
answer file "Import Password Text F
I'm looking for people to test the import of passwords into InfoWallet from
tab-delimited or comma-delimited(csv) text files. These would be files exported
from whatever existing password management program you might be using.
If you are interested and don't already have a license for InfoWallet
11 matches
Mail list logo
