Re: about the meson build systel
Hello David any news on the meson build system ? regards Vincent Torri
Re: Logging Library-GSOC
Hello, On Tue, Aug 18, 2020 at 1:03 PM Priyesh kumar wrote: > > Hi Werner, > I was trying to compile FreeType on Windows using Cygwin and I was > getting the following error while executing `sh autogen.sh' command even > though I have installed the required packages from the Cygwin package > installer: > -- > > Can't locate Automake/Config.pm in @INC (you may need to install the > Automake::Config module) (@INC contains: /usr/share/automake-1.16 > /usr/lib/perl5/site_perl /usr/share/perl5/site_perl /usr/lib/perl5/vendor_p > > erl /usr/share/perl5/vendor_perl /usr/lib/perl5/core_perl > /usr/share/perl5/core_perl) at /c/cygwin/bin/aclocal-1.16 line 36. > > -- > The commands like `make devel;make' which do not use `sh autogen.sh' script > are executing fine... > I have searched about this error online but didn't get any helpful answers. > Could you please take a look at it as it the only remaining platform to test > the changes. If you want I can tell you how I compile freetype on Windows using MSYS2 and mingw-w64 (or even on linux with cross compilation) regards Vincent Torri
Re: Logging Library-GSOC
> I was trying to compile FreeType on Windows using Cygwin and I was > getting the following error while executing `sh autogen.sh' command > even though I have installed the required packages from the Cygwin > package installer: > -- > > > *Can't locate Automake/Config.pm in @INC (you may need to install the > Automake::Config module) (@INC contains: /usr/share/automake-1.16 > /usr/lib/perl5/site_perl /usr/share/perl5/site_perl > /usr/lib/perl5/vendor_p* > > *erl /usr/share/perl5/vendor_perl /usr/lib/perl5/core_perl > /usr/share/perl5/core_perl) at /c/cygwin/bin/aclocal-1.16 line 36.* > > -- Obviously there is a problem with Perl. No idea how to solve it, sorry. In case you can't generate the `configure` script simply copy it to your Cygwin environment from, say, your GNU/Linux box. We don't guarantee that a build directly from the git repository works on all platforms. However, the tarball created by `make dist` should work. > I have searched about this error online but didn't get any helpful > answers. Could you please take a look at it as it the only > remaining platform to test the changes. IMHO it's not worth that you examine this in more detail. > I also wanted to ask that other than using `make' and `cmake' is > there some other way to compile FreeType on Mac platforms? No idea. What exactly are you interested in? > After this, I will proceed towards updating the `docs/DEBUG' file > and wrap up the project. Thanks! Werner
4×4 oversampling is even better than FreeType antialiasing
Includes FreeType code to do 4×4 oversampling
ÿþI f i n d 4 × 4 o v e r s a m p l i n g t o b e e v e n
b e t t e r t h a n F r e e T y p e a n t i a l i a s i n g .
" 4 × 4 o v e r s a m p l i n g w i l l r e n d e r a f u l l
p i x e l e v e n w h e n t i n y p a r t s o f i t a r e
o u t s i d e o f t h e o u t l i n e .
" 4 × 4 o v e r s a m p l i n g d o e s n o t h a v e t h e
p o s i t i o n a l u n c e r t a i n t y o f a r e a
m a t c h i n g , t h e r e f o r e m u l t i p l e o f t h e
s a m e o u t l i n e o n t o p o f e a c h o t h e r d o
n o t l o s e s m o o t h n e s s , a n d i t i s p o s s i b l e
t o s t a c k r e n d e r e d g l y p h s s e a m l e s s l y .
" 4 × 4 o v e r s a m p l i n g h a s t h e s a m e
r a s t e r i z e r a s t h e b i l e v e l r e n d e r e r ,
m a k i n g f o r c o n s i s t e n t r e n d e r i n g , a n d
h a s t h e e x a c t s a m e f e a t u r e s s u c h a s
d r o p o u t c o n t r o l .
" 4 × 4 o v e r s a m p l i n g i s a c c u r a t e
a n t i - a l i a s i n g t o w h a t i s u s e d i n a
s t a n d a r d T r u e T y p e r e n d e r e r , t h e c l a s s i c
G D I r e n d e r e r .
H o w t o d o 4 × 4 o v e r s a m p l i n g ?
" C r e a t e h i n t e d o u t l i n e , l i k e i n
b i l e v e l r e n d e r i n g b u t w i t h a g r a y s c a l e
G E T I N F O
" S c a l e t h e o u t l i n e f o u r t i m e s
h o r i z o n t a l l y a n d f o u r t i m e s v e r t i c a l l y
" R e n d e r b i l e v e l r e n d e r i n g
H o w t o r e p r e s e n t 4 × 4 o v e r s a m p l i n g i n
F r e e T y p e ?
F T _ U I n t i n t e r p r e t e r _ v e r s i o n =
T T _ I N T E R P R E T E R _ V E R S I O N _ 3 5 ;
F T _ P r o p e r t y _ S e t ( l i b r a r y ,
" t r u e t y p e " , " i n t e r p r e t e r - v e r s i o n " ,
& i n t e r p r e t e r _ v e r s i o n ) ;
i f ( F T _ G e t _ G a s p ( f a c e ,
p p e m ) & F T _ G A S P _ D O _ G R A Y ) {
F T _ L o a d _ G l y p h ( f a c e , g l y p h ,
F T _ L O A D _ N O _ B I T M A P | F T _ L O A D _ T A R G E T _ N O R M A L | F T _ L O A D _ N O _ A U T O H I N T ) ;
f o r ( i n t _ f a s t 6 4 _ t i = 0 ;
i < f a c e - > g l y p h - > o u t l i n e . n _ p o i n t s ; i + + ) {
f a c e - > g l y p h - > o u t l i n e . p o i n t s [ i ] . x * = 4 ;
f a c e - > g l y p h - > o u t l i n e . p o i n t s [ i ] . y * = 4 ;
}
F T _ R e n d e r _ G l y p h ( f a c e - > g l y p h ,
F T _ R E N D E R _ M O D E _ M O N O ) ;
}
e l s e {
F T _ L o a d _ G l y p h ( f a c e , g l y p h ,
F T _ L O A D _ T A R G E T _ M O N O | F T _ L O A D _ N O _ A U T O H I N T | F T _ L O A D _ R E N D E R | F T _ L O A D _ M O N O C H R O M E ) ;
}
A f t e r F r e e T y p e r e n d e r i n g , h o w t o s t a c k
4 × 4 o v e r s a m p l e d g l y p h s ?
" T h e s a m e a s i n b i l e v e l r e n d e r i n g : u s e
t h e o r g a t e ' | '
" D i s c a r d p i x e l s a b o v e f o n t h e i g h t
b o u n d a r i e s ( s c a l e d f o u r t i m e s )
A f t e r t e x t l i n e r e n d e r i n g , h o w t o w r i t e
t h e 4 × 4 o v e r s a m p l i n g l i n e o f t e x t t o
p i x e l s ?
" F i n d t h e a m o u n t o f p i x e l s i n e a c h 4 × 4
s q u a r e
" R e p l a c e e a c h 1 w i t h 0
" C o n v e r t f o r e g r o u n d c o l o r a n d
b a c k g r o u n d c o l o r f r o m s R G B t o R G B
( l o o k u p t a b l e f o r w h i c h R G B v a l u e
c o r r e s p o n d s t o e a c h s R G B v a l u e )
" U s e l i n e a r i n t e r p o l a t i o n a s s u m i n g
e a c h 0 i s b a c k g r o u n d c o l o r a n d e a c h 1 6
i s f o r e g r o u n d c o l o r
" C o n v e r t t h e r e s u l t i n g R G B c o l o r s t o
s R G B ( l o o k u p t a b l e f o r w h a t i s t h e
f i r s t R G B v a l u e t h a t c o r r e s p o n d s t o
e a c h s R G B v a l u e w i t h e i g h t s t e p b i n a r y
s e a r c h )
Re: Logging Library-GSOC
Hi Werner, I was trying to compile FreeType on Windows using Cygwin and I was getting the following error while executing `sh autogen.sh' command even though I have installed the required packages from the Cygwin package installer: -- *Can't locate Automake/Config.pm in @INC (you may need to install the Automake::Config module) (@INC contains: /usr/share/automake-1.16 /usr/lib/perl5/site_perl /usr/share/perl5/site_perl /usr/lib/perl5/vendor_p* *erl /usr/share/perl5/vendor_perl /usr/lib/perl5/core_perl /usr/share/perl5/core_perl) at /c/cygwin/bin/aclocal-1.16 line 36.* -- The commands like `make devel;make' which do not use `sh autogen.sh' script are executing fine... I have searched about this error online but didn't get any helpful answers. Could you please take a look at it as it the only remaining platform to test the changes. I also wanted to ask that other than using `make' and `cmake' is there some other way to compile FreeType on Mac platforms? After this, I will proceed towards updating the `docs/DEBUG' file and wrap up the project. Thanks, Priyesh
Re: Migrate to github
Hello Anurag, thanks for your thoughts. > *#1: Migrate development over to github:* > Host the git repo on GitHub, use the GitHub issues and PR tracker > instead of GNU Savannah and e-mail No. We won't migrate to github. If at all, gitlab would be a possible choice. > *3. Easier for newbies:* > *4. Attracts younger developers:* This doesn't convince me. A developer who is attracted to a project by the use of github or gitlab only is probably a developer we don't need. > *#2: Join GitHub sponsors program:* > Text rendering has a profound impact on the user experience and > there would be many people willing to sponsor improvements to text > rendering, particularly linux folks, so it would be great if there > was a way to channel their support. Believe me, sponsoring is not a problem – I have been sponsored by Google and Adobe to do *a lot* for FreeType, and I actually don't need money for working on FreeType. Neither does David, Alexei, or Toshiya. It's rather a matter of stamina, interest, and time. > *Benefits:* > Increase incentive for developers to contribute to freetype, the > money could be used to hire part time devs, support website > infrastructure, etc. Mhmm, not convinced. > GitHub actions can be used to setup a ci for freetype and make > issue/PR tracking easier with bots. Yes, we will eventually use CI features. > Overall, the proposed changes would decrease friction for new > developers, What new developers? > These are my points (I am a newbie too), I hope this post starts a > discussion and we are able to reach a conclusion. The most important thing would be to find a capable person who is willing to invest time into a transition of the main developing platfrom from Savannah to gitlab, which is a tedious and very time-consuming process. I'm also working for GNU LilyPond; a transition to gitlab was done recently, and it took a few months to iron out everything. You might check the 'lilypond-devel' mailing list for e-mails on this topic (mainly from Jonas Hahnfeld), starting at https://lists.gnu.org/archive/html/lilypond-devel/2020-02/msg00249.html We were really lucky that this guy appeared recently... Werner
