>
>> 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
> 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
___
> 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
> 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
_
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.n
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 coup
> 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 n
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,
>
> > 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
> 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
>
> >> 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
> 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 someth
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 !!!
>> 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/mail
> >> 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'
15 matches
Mail list logo
