Re: [nkoo, N'KO identification issue on Ubuntu 20.04] (Re: Freetype-devel Digest, Vol 186, Issue 28)

[Moustapha KOUROUMA]

Hello my dear,
I see why i haven't be able to find
libkf5pimcommonakonadi5
In your first message you wrote 
libkf5pimcommonakodi5 and not 

libkf5pimcommonakonadi5
Anyway thank you !


Cordialement,Moustapha KOUROUMATel: (0033) 06 17 91 97 12/ 02 23 25 87 31
 "L'homme qui peut crier fort, c'est le citoyen libre et souverain".Fode Tass 
Sylla       
Pensez à l'environnement, n'imprimez ce mail que si c'est nécessaire !
 

On Tuesday, 21 July 2020, 07:30:21 CEST, Moustapha KOUROUMA 
 wrote:  
 
 Hello, i talk about libkf5pimcommonakodi5.I have already install onak ans the 
font. I think it's not googling case. One side to solve the issue and another 
side to have traces for others users in the forum.I wish you understand me.

Sent from Yahoo Mail on Android 
 
  On Tue, 21 Jul 2020 at 0:45, Hin-Tak Leung 
wrote:

On Monday, 20 July 2020, 21:37:14 GMT+1, Moustapha KOUROUMA 
 wrote:  

> Do you know where i can find libkf5pimcommonakodi5 ?

Is it so hard to find? 
https://packages.ubuntu.com/onak

I'll write this again: It is somewhat unfair for some of us to do your 
Google'ing for you though...
  

Re: Logging Library-GSOC

[Vincent Torri]

On Tue, Jul 21, 2020 at 6:27 AM Werner LEMBERG  wrote:
>
> > I have also updated the GitHub repo containing this example @ here
> > 
>
> Alas, I don't use Windows so I can't check this.

install on your linux distro mingw-w64 toolchain to compile. Install
wine to test it

Vincent Torri

new compiler warnings in freetype 2.10.2 32-bit

[Hin-Tak Leung via FreeType development]

Hi,

There seems to be a new warning in 2.10.2 (compared to 2.10.1) when compiling 
for 32-bit:

===
freetype-2.10.2/src/sfnt/sfwoff2.c:327:39: warning: passing argument 3 of 
'BrotliDecoderDecompress' from incompatible pointer type 
[-Wincompatible-pointer-types]
  327 |   _size,
  |   ^~
  |   |
  |   FT_ULong * {aka long unsigned int 
*}
===

Also have had a bunch of strncat related warning (probably gcc 10 specific, or 
some compiler switch specific) in ft2-demos, for a while: 

===
inlined from 'RunIns' at src/ttdebug.c:2105:11:
/usr/include/bits/string_fortified.h:136:10: warning: '__builtin___strncat_chk' 
output may be truncated copying 31 bytes from a string of length 31 
[-Wstringop-truncation]
  136 |   return __builtin___strncat_chk (__dest, __src, __len, __bos (__dest));
--
inlined from 'RunIns' at src/ttdebug.c:2105:11:
/usr/include/bits/string_fortified.h:136:10: warning: '__builtin___strncat_chk' 
output may be truncated copying 8 bytes from a string of length 31 
[-Wstringop-truncation]
  136 |   return __builtin___strncat_chk (__dest, __src, __len, __bos (__dest));
--
inlined from 'RunIns' at src/ttdebug.c:2105:11:
/usr/include/bits/string_fortified.h:136:10: warning: '__builtin___strncat_chk' 
output may be truncated copying 8 bytes from a string of length 31 
[-Wstringop-truncation]
  136 |   return __builtin___strncat_chk (__dest, __src, __len, __bos (__dest));
--
inlined from 'RunIns' at src/ttdebug.c:2105:11:
/usr/include/bits/string_fortified.h:136:10: warning: '__builtin___strncat_chk' 
output may be truncated copying 8 bytes from a string of length 31 
[-Wstringop-truncation]
  136 |   return __builtin___strncat_chk (__dest, __src, __len, __bos (__dest));
--
inlined from 'RunIns' at src/ttdebug.c:2105:11:
/usr/include/bits/string_fortified.h:136:10: warning: '__builtin___strncat_chk' 
output may be truncated copying 8 bytes from a string of length 31 
[-Wstringop-truncation]
  136 |   return __builtin___strncat_chk (__dest, __src, __len, __bos (__dest));
--
inlined from 'RunIns' at src/ttdebug.c:2105:11:
/usr/include/bits/string_fortified.h:136:10: warning: '__builtin___strncat_chk' 
output may be truncated copying 8 bytes from a string of length 31 
[-Wstringop-truncation]
  136 |   return __builtin___strncat_chk (__dest, __src, __len, __bos (__dest));
--
inlined from 'RunIns' at src/ttdebug.c:2105:11:
/usr/include/bits/string_fortified.h:136:10: warning: '__builtin___strncat_chk' 
output may be truncated copying 8 bytes from a string of length 31 
[-Wstringop-truncation]
  136 |   return __builtin___strncat_chk (__dest, __src, __len, __bos (__dest));
--
inlined from 'FTDemo_Install_Font' at src/ftcommon.c:534:5:
/usr/include/bits/string_fortified.h:106:10: warning: '__builtin___strncpy_chk' 
specified bound depends on the length of the source argument 
[-Wstringop-overflow=]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
--
===

Argh, that's just one line in ttdebug which generates multiple warnings, plus 
another one in ftcommon.c

I haven't gotten round to look at either, just in case somebody are bothered 
enough to have a look...

Hin-Tak

Re: Logging Library-GSOC

[Priyesh kumar]

Hi Werner,

*> What do your GNU/Linux tests show?*

So, I was analyzing time taken by the example program @ here

and this time for comparison purpose I have made dlg write logs
to stderr.
I have used FT2_DEBUG=any:7 with:
./test arial.ttf *qwertyuiopasdfghjklzxcvbnm*
and I have got following results:
FT_LOGGING: 387ms ( here dlg writes logs to stderr )
FT_DEBUG_LEVEL_TRACE: 305 ms ( FreeType writes logs to stderr, no
redirection to text file)
Please provide feedback...

I have also updated `builds/freetype.mk` so that in Linux, dlg is built
like rest of the
modules in FreeType.
And I wanted to ask that should I also go ahead add a visual studios
project in `src/dlg`
to build dlg on windows?
For this, we have to add a Windows command script to copy the files from
`submodules/dlg/` to `src/dlg`...

Thanks,
Priyesh