[ft-devel] GSoC Status update and complete API reference website

2018-06-12 Thread Nikhil Ramakrishnan
Hi all, * It's been 4 weeks since the coding period for GSoC began and I have written another status update for weeks 3 & 4: https://github.com/nikramakrishnan/freetype-docs/wiki/GSoC-Status-Update:-Week-3-&-4 * Also, docwriter (https://github.com/nikramakrishnan/freetype-docwriter) can now

Re: [ft-devel] GSoC Status update and complete API reference website

2018-06-12 Thread Werner LEMBERG
>>> I do not like `quoted' text. Do you mean in the input or in the output? Right now, `...' in the input has two purposes. (1) It is used as a poor-man's substitute for inline code snippets – the thing Nikhil is talking. (2) It is *really* used for quotations, i.e., `foo' should be

Re: [ft-devel] GSoC Status update and complete API reference website

2018-06-12 Thread Alexei Podtelezhnikov
>> I do not like `quoted' text. > I do have a suggestion - Changing variable names and inline code snippets > to `foobar` instead of `foobar'. Markdown will add an inline code block > around the text (see attached image). Yes, I would prefer this. There was a reason to use different quotes,

Re: [ft-devel] [Doubt] Error with STREAM_FILE function.

2018-06-12 Thread Werner LEMBERG
> The function STREAM_FILE used to extract file pointer from input > stream is not working. I also tried to use > stream->descriptor.pointer directly but it also gives the same error > with ftview. *(Error: > */home/parth/freetype-demos-deve/bin/.libs/ftview: symbol lookup > error:

Re: [ft-devel] [Doubt] Error with STREAM_FILE function.

2018-06-12 Thread Parth Wazurkar
> > >`STREAM_FILE' is a macro! In other words, it must *never* appear as > >an undefined symbol in the DLL. Doing `git grep STREAM_FILE', I get > > ... > > builds/unix/ftsystem.c: /* We use the macro STREAM_FILE for > convenience to extract the */ > > builds/unix/ftsystem.c:#define

[ft-devel] completed CPAL/COLR support

2018-06-12 Thread Werner LEMBERG
Folks, the CPAL/COLR interface is now implemented and committed to git. However, it is still mainly untested; I'm working on it the next days – be warned that there might be issues. Werner ___ Freetype-devel mailing list

Re: [ft-devel] GSoC Status update and complete API reference website

2018-06-12 Thread Werner LEMBERG
>> * In the `fields' subsection of each element, please reduce the >> space between the elements. In most cases, the descriptions are >> only a single line, and (at least with my Chrome browser) this >> takes too much vertical space IMHO, see attached image. > > I have reduced the space.

Re: [ft-devel] GSoC Status update and complete API reference website

2018-06-12 Thread Nikhil Ramakrishnan
> It is nice that most ordered and unordered lists are picked up. Is it > described somewhere what is recognized as a list? For now any list style supported by markdown should work except in field tables (there is a problem with ordered lists right now, but I am working to fix this). You can

Re: [ft-devel] GSoC Status update and complete API reference website

2018-06-12 Thread Werner LEMBERG
Hello Nikhil! > * Also, docwriter > (https://github.com/nikramakrishnan/freetype-docwriter) can now > output Markdown, and I am in the process of writing code to > automatically generate the `yml' configuration file required by > MkDocs. Great! Will check that within the next few

[ft-devel] [Doubt] Error with STREAM_FILE function.

2018-06-12 Thread Parth Wazurkar
Hi all, The function STREAM_FILE used to extract file pointer from input stream is not working. I also tried to use stream->descriptor.pointer directly but it also gives the same error with ftview. *(Error: */home/parth/freetype-demos-deve/bin/.libs/ftview: symbol lookup error:

Re: [ft-devel] GSoC Status update and complete API reference website

2018-06-12 Thread Nikhil Ramakrishnan
> Right now I've noticed only two issues. > > * Looking at > > https://nikramakrishnan.github.io/freetype-site/ft2-toc/ > > I wonder why the `Docs' link in > > Docs » Table of Contents > > points to the index. Is this intentional? I assume this is a > temporary decision, since

Re: [ft-devel] GSoC Status update and complete API reference website

2018-06-12 Thread Alexei Podtelezhnikov
On Tue, Jun 12, 2018 at 8:26 AM, Nikhil Ramakrishnan wrote: > * The complete API documentation site is now available on > https://nikramakrishnan.github.io/freetype-site/ft2-toc/ > This was generated using docwriter with the header files > updated to commit