Package: dict-freedict-eng-hin
Version: 2016.10.22-2
Severity: normal

Dear Maintainer,


In below example, you'd notice that the hindi definition and the english
descripiton, do not not have a separator in between. This leads to
difficult readability

I verified this issue, both, on the TUI client dict, as well as with a
graphical client, goldendict, based on Qt libraries.

I'm not sure if this issue was present earlier or not.

I'm also not sure which way should this be fixed. Should we add a
whitespace as a separator ? Or a newline ?

I'm also not sure what the status is with the other Indic languages.


rrs@learner:~/rrs-home/Community/Packaging$ dict -d fd-eng-hin computer 
television snake jackal
1 definition found

>From  [fd-eng-hin]:

  computer <N>
  1. कम्प्यूटरHe has got a personal computer.
  
1 definition found

>From  [fd-eng-hin]:

  television <N>
  1. दूरदर्शनWe purchased a new television set.
  
2 definitions found

>From  [fd-eng-hin]:

  snake <V>
  1. रेंगनाThe path snakes in the hilly areas.
  

>From  [fd-eng-hin]:

  snake <N>
  1. साँपAll snakes are not poisonous.
  
1 definition found

>From  [fd-eng-hin]:

  jackal <N>
  1. सियारThe Jackal population has gone down in the last few years in this 
forest.
  
2016-12-10 / 21:49:20 ♒♒♒  ☺  

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (990, 'testing-debug'), (990, 'testing'), (500, 
'unstable-debug'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.13+ (SMP w/4 CPU cores)
Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

dict-freedict-eng-hin depends on no packages.

dict-freedict-eng-hin recommends no packages.

Versions of packages dict-freedict-eng-hin suggests:
ii  dicod             2.3-1+b1
ii  dict              1.12.1+dfsg-4
ii  gnome-dictionary  3.20.0-3
ii  goldendict        1.5.0~git20160508.g92b5485-1.1

-- no debconf information

Reply via email to