Re: [ft-devel] Clustering in freetype2-demos
> >> It's intended behaviour (well, let's say that `ftview' is rather >> dumb :-). Those glyphs all have zero width. > > IMHO, there should be some default width for glyph having zero > width. What's your opinion? 1/2 ppem?___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Problem in ft2-demo compilation.
> Maybe an X11 library is missing. Thanks for the files. Please send the output of `ldd /path/to/installed/ftview'. Please also send the result of make &> make.log (for the demo programs) And finally, where is your `libX11.so' file (or files)? Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Clustering in freetype2-demos
> It's intended behaviour (well, let's say that `ftview' is rather > dumb :-). Those glyphs all have zero width. > IMHO, there should be some default width for glyph having zero width. What's your opinion? Ankit ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Clustering in freetype2-demos
> In freetype2-demo "ftview" program, for some character > (unic300,301,302...) are clustering in OpenSans fonts. Is this > intended behaviour or bug in the demo program. It's intended behaviour (well, let's say that `ftview' is rather dumb :-). Those glyphs all have zero width. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
[ft-devel] Clustering in freetype2-demos
In freetype2-demo "ftview" program, for some character (unic300,301,302...) are clustering in OpenSans fonts. Is this intended behaviour or bug in the demo program. Regards, Ankit ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Indirection issue with 'ft_trace_levels'
On 04/09/2018 16:43, Alexei Podtelezhnikov wrote: ftbase.c wraps ftlcdfil.c and many others. You are not suppose to compile all C files. Are you using builds/windows/vc2010/freetype.vcxproj ? Oops... I'm actually using my own VC project file but you're right - I'd accidentally included a couple of files which already get built via ftbase.c BTW ... On 04/09/2018 14:49, Alexei Podtelezhnikov wrote: I do not think the special windows version is needed actually. It only tee's the output to Windows debugger, which can be done with "#ifdef WIN32" or something.I will try that. If I abandon 'builds/windows/ftdebug.c' and I replace it with 'src/base/ftdebug.c', that does solve the compiler error that I originally reported (C2372). Thanks, John ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Indirection issue with 'ft_trace_levels'
> As a separate (unrelated) issue, MSVC now gives me these linker warnings > which I don't remember seeing previously:- > > ftbase.obj : warning LNK4006: _FT_Library_SetLcdGeometry already > defined in ftlcdfil.obj; second definition ignored ftbase.c wraps ftlcdfil.c and many others. You are not suppose to compile all C files. Are you using builds/windows/vc2010/freetype.vcxproj ? ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Indirection issue with 'ft_trace_levels'
On 04/09/2018 14:49, Alexei Podtelezhnikov wrote: After updating from git master this morning, I'm finding a compilation error in 'builds/windows/ftdebug.c' when I try to build with MSVC. I do not think the special windows version is needed actually. It only tee's the output to Windows debugger, which can be done with "#ifdef WIN32" or something.I will try that. Thanks Alexei. As a separate (unrelated) issue, MSVC now gives me these linker warnings which I don't remember seeing previously:- ftbase.obj : warning LNK4006: _FT_Library_SetLcdGeometry already defined in ftlcdfil.obj; second definition ignored ftbase.obj : warning LNK4006: _FT_Get_X11_Font_Format already defined in ftfntfmt.obj; second definition ignored ftbase.obj : warning LNK4006: _FT_Library_SetLcdFilter already defined in ftlcdfil.obj; second definition ignored ftbase.obj : warning LNK4006: _FT_Get_Font_Format already defined in ftfntfmt.obj; second definition ignored ftbase.obj : warning LNK4006: _ps_property_get already defined in ftpsprop.obj; second definition ignored ftbase.obj : warning LNK4006: _FT_Library_SetLcdFilterWeights already defined in ftlcdfil.obj; second definition ignored ftbase.obj : warning LNK4006: _ps_property_set already defined in ftpsprop.obj; second definition ignored ftbase.obj : warning LNK4006: _ft_lcd_padding already defined in ftlcdfil.obj; second definition ignored ftbase.obj : warning LNK4006: _FT_Palette_Set_Foreground_Color already defined in ftcolor.obj; second definition ignored ftbase.obj : warning LNK4006: _FT_Palette_Select already defined in ftcolor.obj; second definition ignored ftbase.obj : warning LNK4006: _FT_Palette_Data_Get already defined in ftcolor.obj; second definition ignored The warnings appear when linking either a Debug build or a Release build (so they're not connected to the issue with 'ftdebug.c') John ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Problem in ft2-demo compilation.
> > > These are running totally fine. > > > >> Maybe an X11 library is missing. BTW, tracing with FT2_DEBUG doesn't > >> help in this case, since the error is not located in the FreeType > >> library. > > > > > > Yes. > > Yes or no? > `libX11-devel' is properly installed and is up to date. Your set up is clearly miscommunicating with X server. > Ok. I will check. Can you give any lead, how can I test it? Thank you Parth ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Problem in ft2-demo compilation.
> These are running totally fine. > >> Maybe an X11 library is missing. BTW, tracing with FT2_DEBUG doesn't >> help in this case, since the error is not located in the FreeType >> library. > > > Yes. Yes or no? Your set up is clearly miscommunicating with X server. Make sure that your libX11 is properly installed especially libX11-devel should be up to date. ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Problem in ft2-demo compilation.
>
> >> Are you running an X server? Some GNU/Linux boxes use Wayland
> >> instead; on such machines X11 must be handled separately.
> >
> > Yes, I am running X11, I checked with `echo $XDG_SESSION_TYPE',
> > although many ubuntu distributions use wayland instead. Still, it
> > is causing the same problem, can there be any other problem? I am
> > attaching the debugged log.
>
> Can you run any other basic X program, for example, `xclock' or
> `xeyes'?
>
These are running totally fine.
Maybe an X11 library is missing. BTW, tracing with FT2_DEBUG doesn't
> help in this case, since the error is not located in the FreeType
> library.
Yes.
You might get more information with
>
> strace ftview ... &> strace.log
>
I am not able to understand this file. I am attaching it with this mail.
You might also have a look into your local `.xsession-errors' file
> (for me, it's in my home directory) or the global `Xorg.log' file (see
> directory `/var/log' or something similar) for relevant messages.
>
I could not find these files in my ubuntu 18.04 installation, so I tried
to tweak with the X11 library, and it ended a disaster, I have now
newly installed ubuntu 16.04 and it still is giving the same problem,
I don't know why. I am attaching the `.xsession-errors' and `Xorg.log'
files
here. Please help.
Thank you
Parth
.xsession-errors
Description: Binary data
execve("./ftview", ["./ftview", "20", "6x13B.bdf"], [/* 67 vars */]) = 0
brk(NULL) = 0x2242000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=88383, ...}) = 0
mmap(NULL, 88383, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f3f95193000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libtinfo.so.5", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0p\310\0\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=167240, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f3f95192000
mmap(NULL, 2264256, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f3f94d5b000
mprotect(0x7f3f94d8, 2093056, PROT_NONE) = 0
mmap(0x7f3f94f7f000, 20480, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x24000) = 0x7f3f94f7f000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libdl.so.2", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\240\r\0\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=14608, ...}) = 0
mmap(NULL, 2109680, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f3f94b57000
mprotect(0x7f3f94b5a000, 2093056, PROT_NONE) = 0
mmap(0x7f3f94d59000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x7f3f94d59000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0
mmap(NULL, 3971488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f3f9478d000
mprotect(0x7f3f9494d000, 2097152, PROT_NONE) = 0
mmap(0x7f3f94b4d000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c) = 0x7f3f94b4d000
mmap(0x7f3f94b53000, 14752, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f3f94b53000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f3f95191000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f3f9519
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f3f9518f000
arch_prctl(ARCH_SET_FS, 0x7f3f95190700) = 0
mprotect(0x7f3f94b4d000, 16384, PROT_READ) = 0
mprotect(0x7f3f94d59000, 4096, PROT_READ) = 0
mprotect(0x7f3f94f7f000, 16384, PROT_READ) = 0
mprotect(0x6f3000, 4096, PROT_READ) = 0
mprotect(0x7f3f951a9000, 4096, PROT_READ) = 0
munmap(0x7f3f95193000, 88383) = 0
open("/dev/tty", O_RDWR|O_NONBLOCK) = 3
close(3)= 0
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=10219008, ...}) = 0
mmap(NULL, 10219008, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f3f93dce000
close(3)= 0
brk(NULL) = 0x2242000
brk(0x2243000) = 0x2243000
brk(0x2244000) = 0x2244000
brk(0x2245000) = 0x2245000
getuid()
Re: [ft-devel] Indirection issue with 'ft_trace_levels'
> After updating from git master this morning, I'm finding a compilation > error in 'builds/windows/ftdebug.c' when I try to build with MSVC. I do not think the special windows version is needed actually. It only tee's the output to Windows debugger, which can be done with "#ifdef WIN32" or something.I will try that. ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
[ft-devel] Indirection issue with 'ft_trace_levels'
After updating from git master this morning, I'm finding a compilation error in 'builds/windows/ftdebug.c' when I try to build with MSVC. It gives me an error at line 114:- /* array of trace levels, initialized to 0 */ int ft_trace_levels[trace_count]; // <--- compilation fails here !!! and the error is:- error C2372: 'ft_trace_levels' : redefinition; different types of indirection AFAICT ftdebug.c itself hasn't changed since I last built freetype2 - so has there maybe been a change to 'ft_trace_levels' somewhere which needs to get reflected here? If this doesn't ring any immediate bells with anyone I'll do a bit more digging... John ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Documentation guidelines file
>> What do you think of calling this file `DOCGUIDE'? > > Sounds good, should I add it? Yep. > Any other formatting requirements? I don't think so. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Documentation guidelines file
> >> I've just done some minor improvements in > >> > >> > https://github.com/nikramakrishnan/freetype-docs/wiki/Documentation-Guidelines-for-The-FreeType-Project > > > > Thanks! Should we add this file in the `docs' directory? > > Yes, please add. What do you think of calling this file `DOCGUIDE'? > Sounds good, should I add it? Any other formatting requirements? -- Nikhil ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Documentation guidelines file
>> Thanks. Just curious: Where can I find the fix for @foo to be >> displayed with ...? > > Just released in docwriter 1.0.2. OK, thanks. >> I've just done some minor improvements in >> >> https://github.com/nikramakrishnan/freetype-docs/wiki/Documentation-Guidelines-for-The-FreeType-Project > > Thanks! Should we add this file in the `docs' directory? Yes, please add. What do you think of calling this file `DOCGUIDE'? Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Documentation guidelines file
> >> Have you already pushed the changes to the repository? > > > > Not yet, will do it today. > > Thanks. Just curious: Where can I find the fix for @foo to be > displayed with ...? > Just released in docwriter 1.0.2. > > Oh, and is there anything left to add in the `DOCUMENTATION' file? > > I've just done some minor improvements in > > > https://github.com/nikramakrishnan/freetype-docs/wiki/Documentation-Guidelines-for-The-FreeType-Project > Thanks! Should we add this file in the `docs' directory? -- Nikhil ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
