|
|
"Mr" <m******r******at_hotmail_dot_fr> wrote:
> "Mr" <m******r******at_hotmail_dot_fr> wrote:
> > "An Ordinary Fox" <nomail@nomail> wrote:
> > > "An Ordinary Fox" <nomail@nomail> wrote:
> > > also what this error means:
> >
> > This supposedly means that the file you fed it is not UTF-8 (most standard
> > international text character set). if that file is available online can you
> > share / send it ?
>
>
> Never mind : I managed to generate a file that triggered the exact same error to
> validate my fix. It should again be available to you tomorrow in that same
> place. What the fix does is convert any input file to utf-8 by removing non
> utf-8 characters since these generally can't happen in language directive,
> rather in user declared names. Which shouldn't be a problem as the alteration
> should be quite similar almost everywhere, except when two names differ only by
> one different non uniode char in exactly the same place (like e.g. two
> accentuated similar words with different accents)
>
> Attached image shows morphine molecule from Avogadro pov output with deliberate
> trema accentuated a inside comment, resaved to non utf-8 (nordic) encoding.
>
> Can you try again to import the same file of your own previous attempts to
> confirm it at least no longer reports that error?
why it dosen't apear nothing for me, even the test files?
Post a reply to this message
|
|