"Cannot open file" when file on other drive

[stpb...@gmail.com]

AntConc 3.4.3 on Windows 7 gives error "Cannot open file" when file not on same drive or dictionary. No such problem occur with 3.2.4, what can be the cause?

[Laurence Anthony]

Hi,

Thank you for the report. I use AntConc (3.4.3) on Windows all the time accessing corpora on a variety of disks and locations and have never had this problem. Nobody else has reported this problem either. Can you clarify what you mean by "dictionary"? Also, what was the name of the drive you couldn't access?

Regards,

Laurence.

[JFlorian]

Stpbeng, will the file open on the drive it is on?  If you copy the file to your harddrive, will Antconc open it or crash the program?  e.g. Is it the other drive that is the problem?  Or a problem with the file itself?

Professor Anthony,

I still use an old program for making websites.  Sometimes, it misbehaves so I have learned "tricks" to make the program recognize files that the program has associated with it.  One trick is simply navigating to one of the files in Windows, double click it and let the associations set in Properties make the program open it's own file.  This is especially helpful if I moved files to another drive and the webmaking Program is totally confused -- so it crashes rather than opens if I try to normally load the files.

While I realize this relies on file associations and a Notepad file is associated with Windows/Notepad to open, I wondered if a user could change Properties to associate the txt file with Antconc? or if it just wouldn't work that way?  (then, change the association back to Notepad/windows after getting it to open in Antcon)   Just curious...

Judy

[stpb...@gmail.com]

After a bit of testing, it seems not to be dependent of the drive but occurs in a haphazard way. Either it says one file processed (se 02.jpg) but the file name is blank and can't be opened, or everything is ok (03.jpg). Have tried several files, both utf-8 and iso, but mostly it fails. 3.2.4 work fine every time (01.jpg).

[Laurence Anthony]

Hi,

It sounds as though all your encodings understanding is a little confused. You need to tell AntConc the encoding of your files via the Global settings menu.

AntConc 3.2.4 used Latin1 as the default whereas AntConc 3.4.x uses the international standard UTF8.

Try using Latin1 in AntConc 3.4.3 if everything really is working fine in 3.2.4.

But, the real solution is to know the encodings of your files. My EncodeAnt program can help with that.

Also are your filenames using non-ascii?

These should be ASCII just to be safe.

Laurence

On 6 Feb 2015 08:07, <stpb...@gmail.com> wrote:

After a bit of testing, it seems not to be dependent of the drive but occurs in a haphazard way. Either it says one file processed (se 02.jpg) but the file name is blank and can't be opened, or everything is ok (03.jpg). Have tried several files, both utf-8 and iso, but mostly it fails. 3.2.4 work fine every time (01.jpg).

--
You received this message because you are subscribed to the Google Groups "AntConc-discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to antconc+u...@googlegroups.com.
To post to this group, send email to ant...@googlegroups.com.
Visit this group at http://groups.google.com/group/antconc.
For more options, visit https://groups.google.com/d/optout.

[stpb...@gmail.com]

Thanks, what you say is correct! Seems that the problem only occurs when file encoding differs from the menu settings (see pic). The lack of warning confused me, since nothing happens until one tries to make e.g. a word list. Have nowadays a lot of UTF-8 files, so the encoding feature in 3.4.3 will be greatly appreciated.

[Laurence Anthony]

Great news! I'm glad the issue is resolved. I'm sure many others seeing this discussion in the future will find it useful, too.

In the next release of AntConc, I'm going to deal completely with encodings by including the EncodeAnt engine directly inside AntConc.

Laurence.