-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't open/import Pajek file #27
Comments
Hello, that message indicates that SocNetV thinks you are trying to open a XML (GraphML) file. Pajek files should be imported via the menu Network -> Import (and have a .pajek or .net or .paj extension). Did you try that? If you did and still have errors, please upload a part (the beginning of) the file here to inspect it. |
Yes, i try to open using import method. I just downloaded version 2.1 and
its is working fine on that version.
…On Tue, May 30, 2017 at 9:43 AM, Dimitris Kalamaras < ***@***.***> wrote:
Hello, that message indicates that SocNetV thinks you are trying to open a
XML (GraphML) file.
Pajek files should be imported via the menu Network -> Import (and have a
.pajek or .net or .paj extension). Did you try that?
If you did and still have errors, please upload a part (the beginning of)
the file here to inspect it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#27 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ARVCFZ3ec8CugRqR1dypqGTOM9VmfJ6Kks5r_B0KgaJpZM4NqRUR>
.
|
ΟΚ, closing this. |
I'd prefer using the latest revision. Is this fixed in the dev build?
|
Hello, can you please upload your data file to debug this problem in 2.2 ? |
Ok, now i can load the pajek file in V2.2 This is the test file (text.net) I used |
I am not sure what has happened here and what the problem/explanation is. |
Everytime I try to open a Pajek formatted file, including my own or the one provided in SocNetv manual, I'm getting an error message "XML tokenstring at line 1 is invalid".
The text was updated successfully, but these errors were encountered: