https://bugs.kde.org/show_bug.cgi?id=502725

Ron <kdenlive-b...@contact.dot-oz.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kdenlive-b...@contact.dot-o
                   |                            |z.net

--- Comment #8 from Ron <kdenlive-b...@contact.dot-oz.net> ---
(In reply to ellat from comment #6)
> (In reply to balooii from comment #5)
> > Oh and did you check which font was used in the version you reported as last
> > working?
> 
> Well, Arial works in version 22.12.03.

If you're on Linux, there generally is no Arial font unless you've gone well
out of your
way to install it manually.  It's not a freely licenced font, so distros
generally can't
ship it by default.  It will get mapped to some other "similar" font that you
do have
installed on your system.  (and even 'genuine Arial' may not provide the glyphs
you need for this either).

The "empty square box" is the normal fallback behaviour of most font rendering
code
when some font does not have a glyph defined for a codepoint.

So the key point here is you need to find a font that contains all the glyphs
you need
and configure your system to use it when you need those glyphs.  That means you
may
want to select some font other than Arial, if you are supplying subtitle files
and not burning
them in at render time, and you'll need to find a font that is available and
provides the
needed glyphs on all the platforms you want to play this on.

There really is nothing that kdenlive (or any higher level library or tool) can
do to 'fix' this
if you're using a font with missing glyphs.  The best we could do is share a
user-created
list of fonts that people have tested to work portably for certain locales.

What would have changed to 'break' this for you is the default font that either
your system
libraries provided, or that was suggested by something embedded in whichever
packaged
version of kdenlive you used.  It won't have been a change in kdenlive itself
that caused this.

So, I'd be inclined to close this bug as something "we can't fix", and perhaps
open a thread
on the discuss forum for making font suggestions for various locales.

Sorry this bubbled away for so long without any clarification.  I'm currently
working on
improving the subtitle handling, and only just now saw this report for the
first time.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to