1. We already check in configure.ac that harfbuzz is at least 0.9.0, so
those code paths will never get triggered anyway.
2. We don't plan on supporting old harfbuzz anyway. People should just
upgrade harfbuzz (Not really an issue since it's not yet released).
git-svn-id: http://svn.enlightenment.org/svn/e/trunk/evas@73197
7cbeb6ba-43b4-40fd-8cce-
4c39aea84d33
-#if HB_VERSION_CHECK(0,7,0)
- buffer = hb_buffer_create(slen);
-#else
buffer = hb_buffer_create();
buffer = hb_buffer_create();
hb_buffer_set_unicode_funcs(buffer, _evas_common_font_ot_unicode_funcs_get());
hb_buffer_set_unicode_funcs(buffer, _evas_common_font_ot_unicode_funcs_get());
-#if HB_VERSION_CHECK(0,7,0)
- hb_buffer_set_language(buffer, hb_language_from_string(
- evas_common_language_from_locale_get()));
-#else
hb_buffer_set_language(buffer, hb_language_from_string(
evas_common_language_from_locale_get(), -1));
hb_buffer_set_language(buffer, hb_language_from_string(
evas_common_language_from_locale_get(), -1));
hb_buffer_set_script(buffer, _evas_script_to_harfbuzz[props->script]);
hb_buffer_set_direction(buffer,
(props->bidi.dir == EVAS_BIDI_DIRECTION_RTL) ?
hb_buffer_set_script(buffer, _evas_script_to_harfbuzz[props->script]);
hb_buffer_set_direction(buffer,
(props->bidi.dir == EVAS_BIDI_DIRECTION_RTL) ?