moi15moi
moi15moi
@justvanrossum I have pushed the change 1 week ago. Is there still something you don't like or are not sure?
Since no maintainers share their opinion, do you still want everything done in ``getEncoding`` from ``_n_a_m_e`` or not?
@justvanrossum Have you any news about from other maintainers?
> The two sets of names should contain the same string so it shouldn't matter which one you pick. Like you said, it **_should_**. It is not always the case....
``` def autoTags(duration: int, interval: int, data1: str, data2: str) -> str: result = "" count = math.ceil(duration/interval) for i in range(count): if i%2 == 0: data = data1 else:...
Would it need to use FrameUtility? I don't see how you can do an acceleration with a shape without creating more than one line in .ass.
Hi, Here is my script to do it. My script **only** split the line. Besides, I didn't follow your example. Here's how I handle it all. Example: START=0,END=40,TEXT=`{\k10}a {\k10}b\N{\k10}c {\k10}d`...
> ICU is waaaay too massive for libass to use, if I’m not mixing anything up. Ok. I don't have a good knowledge of C. > I already have name...
**Reason why I think an FontCollector would need to be part of libass.** Libass has a algorithm to make a choice when it pick font. Any FontCollector need to mimic...
>> Even if the algorithm is not supposed to change, it can (see https://github.com/libass/libass/issues/613). > So, a FontCollector could be obsolete. If libass would propose a FontCollector, it would always...