Re: Logging Library-GSOC

2020-07-05 Thread Priyesh kumar 
>






*Since debugging isn't time critical it might be necessary to add an>
additional step that scans tracing messages for newline characters,> then
massaging the output by inserting the time stamp.  In other> words, all
occurrences of>  `\n`> should be replaced with>  `\n[time stamp] `> or
something similar.*

I also came up with the same idea but thought that string comparison will
take
plenty amount of time, therefore, I dropped this idea...
But, as you said so I will try to implement it...
Thanks,
Priyesh


On Sun, Jul 5, 2020 at 1:17 AM Werner LEMBERG  wrote:

>
> > Throughout this week I have integrated dlg with FreeType and I was
> > able to achieve the following goals: [...]
>
> Thanks!
>
> > [...] I am facing a problem with printing FT_COMPONENT and
> > Time-Stamp along with log messages part...  The problem is that this
> > extra information is printed every time there is a call to dlg's API
> > to handle trace/error logs.
>
> Indeed, this is a problem.  The time stamp should only be printed if
> the last character of the last message was a newline character.
>
> Or rather, the printing of a newline character should trigger the
> printing of the time stamp.
>
> > I have attached a log file related to this problem.  I am working on
> > this but in the meantime, if I could get some suggestions it would
> > be very helpful...
>
> Since debugging isn't time critical it might be necessary to add an
> additional step that scans tracing messages for newline characters,
> then massaging the output by inserting the time stamp.  In other
> words, all occurrences of
>
>   `\n`
>
> should be replaced with
>
>   `\n[time stamp] `
>
> or something similar.
>
>
> Werner
>

Re: Overlap oversampling

2020-07-05 Thread Nikolaus Waxweiler 
I have 0 idea actually. I think macOS triggers different rendering 
automatically when it encounters any OVERLAP_* thingy.

Re: Overlap oversampling

2020-07-05 Thread Alexei Podtelezhnikov 
Hi Nikolaus 

> Random thought: Test with Cascadia Code 
> (https://github.com/microsoft/cascadia-code/releases/tag/v2007.01). The 
> (variable) font is very Lego-like in its construction.

You have seen a lot of these fonts. How often the variation fonts set 
OVERLAP_SIMPLE or OVERLAP_COMPOSITE even though it is not required? I wonder if 
those flags are sufficiently respected to trigger FT_OUTLINE_OVERLAP. What 
would be equivalent on the CFF2 side?

Thanks,
Alexei

Re: [patch] Simplify ftconfig.h

2020-07-05 Thread Werner LEMBERG 

> Yes, here's it is as a bundle of 5 intermediate commits.  As a
> reminder, to use it, do:
> 
> git remote add bundle /path/to/bundle
> git fetch bundle

Thanks!  I've normalized the commit messages by converting them to
proper ChangeLog entries, then committed to git.

Note, however, that there are serious issues which I ask you to fix
ASAP:

* After compiling the library with `make devel; make', compilation of
  the the demo programs fails with

freetype2-demos/src/ftbench.c: In function ‘face_requester’:
  freetype2-demos/src/ftbench.c:165:5: warning:
implicit declaration of function ‘FT_UNUSED’ 
[-Wimplicit-function-declaration]
   FT_UNUSED( face_id );
   ^
freetype2-demos/src/ftbench.c:165:5: warning:
  nested extern declaration of ‘FT_UNUSED’ [-Wnested-externs]

[...]

/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld:
 ftbench.o: in function `face_requester':
   freetype2-demos/src/ftbench.c:165: undefined reference to `FT_UNUSED'

[...]


* Compilation with

make multi CC=c++

  now fails with

In file included from freetype2/devel/ft2build.h:36:0,
 from freetype2/src/base/ftsystem.c:28:
  freetype2/include/freetype/config/ftheader.h:52:24: error:
expected declaration before ‘}’ token
 #define FT_END_HEADER  }
^
freetype2/include/freetype/config/ftconfig.h:48:1: note:
  in expansion of macro ‘FT_END_HEADER’
 FT_END_HEADER
 ^


* Compilation with

make multi

  aborts with

  In file included from freetype2/src/pcf/pcfutil.c:35:0:
freetype2/src/pcf/pcfutil.h:38:3: warning:
  return type defaults to ‘int’ [-Wreturn-type]
 FT_LOCAL( void )
 ^~~~
  freetype2/src/pcf/pcfutil.h: In function ‘FT_LOCAL’:
freetype2/src/pcf/pcfutil.h:39:3: error:
  expected declaration specifiers before ‘BitOrderInvert’
 BitOrderInvert( unsigned char*  buf,
 ^~
  freetype2/src/pcf/pcfutil.h:42:3: error:
expected declaration specifiers before ‘FT_LOCAL’
 FT_LOCAL( void )
 ^~~~
  freetype2/src/pcf/pcfutil.h:46:3: error:
expected declaration specifiers before ‘FT_LOCAL’
 FT_LOCAL( void )
 ^~~~
  freetype2/src/pcf/pcfutil.c:42:3: error:
expected declaration specifiers before ‘FT_LOCAL_DEF’
 FT_LOCAL_DEF( void )
 ^~~~
  freetype2/src/pcf/pcfutil.c:64:3: error:
expected declaration specifiers before ‘FT_LOCAL_DEF’
 FT_LOCAL_DEF( void )
 ^~~~
  freetype2/src/pcf/pcfutil.c:83:3: error:
expected declaration specifiers before ‘FT_LOCAL_DEF’
 FT_LOCAL_DEF( void )
 ^~~~
  freetype2/src/pcf/pcfutil.c:100:3: error:
expected ‘{’ at end of input
 }
 ^
  freetype2/src/pcf/pcfutil.c:100:3: warning:
control reaches end of non-void function [-Wreturn-type]
 }
 ^


Werner

Re: Overlap oversampling

2020-07-05 Thread Nikolaus Waxweiler 
Random thought: Test with Cascadia Code 
(https://github.com/microsoft/cascadia-code/releases/tag/v2007.01). The 
(variable) font is very Lego-like in its construction.