Re: [Mlt-devel] MLT font property
Brought to you by:
ddennedy,
lilo_booter
From: Dan D. <da...@de...> - 2011-10-20 02:31:16
|
On Sun, Oct 16, 2011 at 8:08 PM, Brian Matherly <pez...@ya...> wrote: > Dan, > >>>>In my opinion, the bare minimum would be: >> >>>>* family >>>>* size >>>>* style (only options are "italic" and "normal") >>>>* weight (only options are "bold" and "normal") >>>> >>> >>>I am ok with this subset for now. >>> >>>>Do you want any help with this? I'd be happy to help (or just do it for you). Just let me know what properties you want and I can make it happen. >>> >>>I am busy on MLT-related stuff despite the way it may appear. Some of that activity will be revealed soon. :-) I would really appreciate you doing this since you have been so active in this area lately. >> >>I'm on it. I'll implement the subset listed above and convert dynamictext to the new properties. At that point, we can re-evaluate. > > > Here you go: > https://github.com/pez4brian/mlt/commit/0cf6b99f5f0300111a05a6e2717b9526c5be3edd > > Here are some discussion points: > > * There was already an undocumented "size" property. It uses absolute size (pixels) rather than points. I left it that way because, in my opinion, when dealing with video, "points" have no meaning - unless you know the physical size of the display the viewer will be using. In my tests, there is a minuscule difference in the size of the text you get when using pixels vs points. I don't think anyone will notice. Additionally, some of the data_show property files already used the size property. If anyone uses the deprecated "font" property, the absolute size property will be ignored. > > * There was already a "weight" property and it takes a range of numbers. So I left it. > > * family, size and style will be ignored if anyone uses the deprecated "font" property. > > * For anyone who did not specify "font" previously, the defaults for "family" and "size" will make the text the same size as before. > > Let me know if you want anything changed. I notice both font and family use the same pango_font_description_from_string(). What do you think about not adding family and just use font? Then, stop encouraging usage of the font as a combo property in the examples and yml? (As a side benefit people authoring stuff by hand will find easier to remember font rather than family regardless of which is more correct. ;-) -- +-DRD-+ |