how newpipe team fix captions size?

[GreenMystic]

Checklist

• I made sure that there are no existing issues or discussions - open or closed - which I could contribute my information to.
• I have read the FAQ and my question isn't listed.
• I have taken the time to fill in all the required details. I understand that the question will be dismissed otherwise.
• I have read and understood the contribution guidelines.

What is/are your question(s)?

i was wondering how newpipe team fix caption size issues?
because in old release cc are too big

Additional information

iirc old version of newpipe have this issues where subtitle / CC / Caption are too big but in newer / latest release later issues are fixed

[ShareASmile]

I think it was in #11806, it improved the experience for users who use captions in v0.27.6 upwards versions, as issue of caption sizes not being changed have addressed there, at least I can find.

[GreenMystic]

i ask this because in specific newpipe fork i face this issues it's hard fork thuz using old newpipe codebase
the CC is giantic madness there sadly the dev that responsible to a hard fork refuse to fix such thing and tell user to use global OEM Caption setting instead 🥲🥲

[ShareASmile]

Please report a fork's issue in their tracker, btw you can use NewPipe, it is great open source software. Being it a open source app with GNU General Public License anyone can fork it, customize the code, respecting the terms of its license, that's where GNU & open source software gives you the freedom.

Although fork maintainers should give due credits to the code owners of upstream "NewPipe" and NewPipe Extractor" when they use their code, sadly that's not the case in a given fork😒.

[GreenMystic]

Please report a fork's issue in their tracker, btw you can use NewPipe, it is great open source software. Being it a open source app with GNU General Public License anyone can fork it, customize the code, respecting the terms of its license, that's where GNU & open source software gives you the freedom.

1. i can't code
2. i open the issue but the respective fork dev refuse yo do something about it
   at least there's lot of fork thought so no stress i guess