Developer Builds (for testing)

[Oeasy]

I tried the latest 1.5.0-RC-386-g8b3a7a4. The headwords problem of English-Japanese dictionaries still exists.

Try this - GoldenDict-testmap.7z - 1.31 MB.

The problem still exists.

headwords_problem_still_exists.png (134.75 KiB) Viewed 56607 times

[Abs62]

The problem still exists.

Take codes for these extra chars in headwords (look image names in inspector) and create custom font substitution file "afonts_..." (as in dictionary examples on qolibri.sourceforge.jp).

[Alec]

I've just tried the version that is linked to above:
"Re: Developer Builds (for testing)
by Abs62 » Fri May 23, 2014 7:40 am
Oeasy wrote:
I tried the latest 1.5.0-RC-386-g8b3a7a4. The headwords problem of English-Japanese dictionaries still exists.
Try this - GoldenDict-testmap.7z - 1.31 MB."

I got the following error-message:

"The procedure entry point _ZN17QSslConfiguration20defaultConfigurationEv could not be located in the dynamic linked library QtNetwork4.dll"

I was running this on 64-bit Windows 7. Am I misunderstanding something?

[Oeasy]

The problem still exists.

Take codes for these extra chars in headwords (look image names in inspector) and create custom font substitution file "afonts_..." (as in dictionary examples on qolibri.sourceforge.jp).

Dear Abs62, thank you very much. It really works, though still needs some time to sort out all the chars. Now it's perfect for me. Thank you again.

[Oeasy]

I've just tried the version that is linked to above:
"Re: Developer Builds (for testing)
by Abs62 » Fri May 23, 2014 7:40 am
Oeasy wrote:
I tried the latest 1.5.0-RC-386-g8b3a7a4. The headwords problem of English-Japanese dictionaries still exists.
Try this - GoldenDict-testmap.7z - 1.31 MB."

I got the following error-message:

"The procedure entry point _ZN17QSslConfiguration20defaultConfigurationEv could not be located in the dynamic linked library QtNetwork4.dll"

I was running this on 64-bit Windows 7. Am I misunderstanding something?

As Abs62 said here : viewtopic.php?f=4&t=2091&start=270

Take last EA build 1.5.0-RC-358-g6cb186a as base version.

EB library use local 8-bit encoding to handle path. If path to dictionary contains symbols which can't be encoded in 8-bit system locale such error will be occured. Try to move dictionary to other folder with only ASCII symbols in path.

[hanyl05]

The problem still exists.

Take codes for these extra chars in headwords (look image names in inspector) and create custom font substitution file "afonts_..." (as in dictionary examples on qolibri.sourceforge.jp).

Thank you very much, Abs62.
Is it possible to simplify this process?

[Abs62]

Is it possible to simplify this process?

Take Golibri program, select dictionary and use "read all" command. Then look into its cache fonts folder - it will contains all used in dictionary symbol images (except already listed in "afonts_..." file).

[Abs62]

Variant with modified EB library - goldendict-1.5.0-RC-389-g959bac8(EXE only).7z - 1.29 MB.
It should correctly handle path to Epwing dictionary with non-ASCII symbols.

[Oeasy]

Variant with modified EB library - goldendict-1.5.0-RC-389-g959bac8(EXE only).7z - 1.29 MB.
It should correctly handle path to Epwing dictionary with non-ASCII symbols.

Yes, indeed. Thank you very much!

[hanyl05]

Variant with modified EB library - goldendict-1.5.0-RC-389-g959bac8(EXE only).7z - 1.29 MB.
It should correctly handle path to Epwing dictionary with non-ASCII symbols.

Thank you very much, Abs62. Now Goldendict is really the most powerful dictionary software.
It will be much more charming if the support for Gaiji could be more smart.

Best regards.