Re: [ft-devel] Problem with `make refdoc'

[Werner LEMBERG]

>> I thus suggest that you change the order of checked binaries for
>> both python and pip in `configure.raw':
>>
>>   AC_CHECK_PROGS([PYTHON], [python3 python2 python], [missing])
>>   AC_CHECK_PROGS([PIP], [pip3 pip2 pip], [missing])
>
> This will work with `make' but I will have to hard-code these values
> in `unixddef.mk' (or use the defaults, which are `python' and
> `pip'), so it may still cause problems with `make devel'.

Yes, the defaults should be `python' and `pip', to be overridden by
the values `configure' is setting up on Unix hosts.  Users of `make
devel' who want to explicitly use `python3', say, have to call

  PYTHON=python3 make refdoc

> [...] Also, the top-level entry can be achieved by naming one of the
> files `index.md' (ideally the TOC).  This will create a
> `docs/reference/index.html' file (which will be the TOC). Should I
> do this?

Yes, please do.

>> * Loading
>>
>>     file:///.../docs/reference/site/ft2-toc/index.html
>>
>>   in my browser(s) the search field doesn't work.  Is this
>>   expected?
>
> No, I am able to use search on `ft2-toc/index.html'.  Is the search
> bar unresponsive, or does it not display any results?

The latter.  I can type in the search bar, but no results are shown.
FYI, I've tried both `python3' and `python2' for `make refdoc', and it
doesn't make a difference.

Opening Chrome's debugging console I see two errors:

  Fetch API cannot load 
file:///.../docs/reference/site/search/search_index.json.
  URL scheme must be "http" or "https" for CORS request.

  Uncaught (in promise) TypeError: Failed to fetch
      at t.data_ (application.a59e2a89.js:1)
      at application.a59e2a89.js:1

I guess the former explains why it fails.

>> * In Firefox, the magnifying glass left to the search field is
>>   displayed as a missing glyph 0xE8B6 (i.e., a box containing these
>>   four digits).  This doesn't happen if I go to
>>
>>     https://www.dxdy.ooo/freetype-web-jekyll/docs/reference/ft2-toc/
>>
>>   A similar issue happens for the small arrows in the left panel –
>>   it seems that you have to load the corresponding web font –
>>   0xE8B6 and friends are characters from the Private Unicode Area
>>   (PUA); this means they are font-specific and not generic.
>
> Firefox comes with a very strict "file uri origin" policy by
> default.  This prevents the local page from accessing the file
> system to get the required font(s).  A workaround is to go to
> `about:config', filter by fileuri and toggle the preference
>
>   security.fileuri.strict_origin_policy
>
> to set it to `false'.

This works, thanks!  At the same time, this enables off-line searching
on Firefox.  I guess I have to do something similar on Chrome, but
what?

> I'll see how this can be solved without changing browser policies.

OK.


    Werner