Your message dated Sun, 20 Dec 2015 12:52:19 +0530
with message-id <[email protected]>
and subject line Re: Bug#714436: This is a upstream issue, now re-assigning to 
fonts-droid-fallback
has caused the Debian Bug report #714436,
regarding fonts-droid: No Hangul characters
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
714436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714436
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: fonts-droid
Version: 1:4.2.r1-2
Severity: normal

Dear Maintainer,

Korean characters do not display properly (they show up as boxes) after the 
package is installed. After further investigation (downloading the .ttf files 
from the Android git repository), I found that:

1. With only DroidSansFallbackFull.ttf (as is the case in fonts-droid), Korean 
characters do not display properly.

2. With DroidSansFallback.ttf present, Korean characters display properly.


-- Package-specific info:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                 Version                 Architecture   
         Description
+++-====================================-=======================-=======================-=============================================================================
ii  fontconfig                           2.10.2-2                amd64          
         generic font configuration library - support binaries
ii  libfreetype6:amd64                   2.4.9-1.1               amd64          
         FreeType 2 font engine, shared library files
ii  libxft2:amd64                        2.3.1-1                 amd64          
         FreeType-based font drawing library for X

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages fonts-droid depends on:
ii  dpkg  1.16.10

fonts-droid recommends no packages.

fonts-droid suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Martin Tang <[email protected]> writes:

> On 20/12/15 01:35 AM, Vasudev Kamath wrote:
>> Martin Tang <[email protected]> writes:
>>
>>> On 19/12/15 11:31 PM, Vasudev Kamath wrote:
>>>>
>>>> Control: tag -1 +upstream
>>>> Control: reassign -1 fonts-droid-fallback
>>>>
>>>> Hello Martin,
>>>>
>>>> Can you please check if the issue you mentioned still exists with
>>>> newer version fonts-droid-fallback?.
>>>>
>>>> If it still exists please consider reporting it to Android upstream as
>>>> that is the right place to fix it.
>>>>
>>>> Cheers,
>>>>
>>>
>>> Originally (at the time this bug was reported), I had installed the
>>> Droid fonts to get a unified font for CJK languages to avoid different
>>> characters in the same sentence all using different fonts (and way
>>> back in time, the Droid fonts did contain Hangul). Nowadays, I think
>>> the "recommended" font for that role is Noto CJK, which I currently
>>> use.
>>
>> So does that mean I can safely close this bug now?.
>>
>> Cheers,
>>
> Yes, I guess so.

Thanks for confirming. I'm here by closing this bug.

--- End Message ---

Reply via email to