at the risk of stating the obvious, I believe that the only way to re-enable the USE_PANGO_WIN32 flag will be to somehow bypass or temporarily disable the OpenType code that was committed in rev 14215. http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/14215
...........................................................
- when using the USE_PANGO_WIN32 flag, the typical call one sees is 'pango_win32_font_cache_load' which comes from the dll 'libpangowin32-1.0-0.dll'
- when not using this flag, the typical call one sees is 'pango_fc_font_lock_face' which comes from the dll 'libpangoft2-1.0-0.dll'.
- the OpenType code committed in rev 14215 introduced a new type of call to 'pango_ot_info_get' which also comes from 'libpangoft2-1.0-0.dll'.
since these two dll's do not seem to overlap in any way, it seems that it will be necessary to avoid executing the OpenType code before the USE_PANGO_WIN32 flag can be re-enabled.
Any feedback of any sort would be greatly appreciated ...
at the risk of stating the obvious, I believe that the only way to re-enable the USE_PANGO_WIN32 flag will be to somehow bypass or temporarily disable the OpenType code that was committed in rev 14215. bazaar. launchpad. net/~inkscape. dev/inkscape/ trunk/revision/ 14215 ....... ....... ....... ....... ....... ....... ....... ... win32_font_ cache_load' which comes from the dll 'libpangowin32- 1.0-0.dll'
http://
.......
- when using the USE_PANGO_WIN32 flag, the typical call one sees is 'pango_
- when not using this flag, the typical call one sees is 'pango_ fc_font_ lock_face' which comes from the dll 'libpangoft2- 1.0-0.dll' .
- the OpenType code committed in rev 14215 introduced a new type of call to 'pango_ot_info_get' which also comes from 'libpangoft2- 1.0-0.dll' .
since these two dll's do not seem to overlap in any way, it seems that it will be necessary to avoid executing the OpenType code before the USE_PANGO_WIN32 flag can be re-enabled.
Any feedback of any sort would be greatly appreciated ...