[Fedora-i18n-bugs] [Bug 1335073] New: [abrt] ibus-table: os.py:241:makedirs:FileExistsError: [Errno 17] File exists: '/home/mfabian/.local/share/ibus-table'
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1335073
Bug ID: 1335073
Summary: [abrt] ibus-table: os.py:241:makedirs:FileExistsError:
[Errno 17] File exists:
'/home/mfabian/.local/share/ibus-table'
Product: Fedora
Version: 24
Component: ibus-table
Assignee: mfabian(a)redhat.com
Reporter: mfabian(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dchen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
kent.neo(a)gmail.com, me(a)kaio.net, mfabian(a)redhat.com,
pwu(a)redhat.com, shawn.p.huang(a)gmail.com
Version-Release number of selected component:
ibus-table-1.9.12-1.fc24
Additional info:
reporter: libreport-2.7.0
cmdline: /usr/bin/python3 /usr/share/ibus-table/engine/main.py --xml
executable: /usr/share/ibus-table/engine/main.py
kernel: 4.5.3-300.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor: Fedora Project
reproducible: Not sure how to reproduce the problem
runlevel: N 5
type: Python3
uid: 1000
Truncated backtrace:
os.py:241:makedirs:FileExistsError: [Errno 17] File exists:
'/home/mfabian/.local/share/ibus-table'
Traceback (most recent call last):
File "/usr/share/ibus-table/engine/main.py", line 32, in <module>
import factory
File "/usr/share/ibus-table/engine/factory.py", line 27, in <module>
import tabsqlitedb
File "/usr/share/ibus-table/engine/tabsqlitedb.py", line 36, in <module>
import ibus_table_location
File "/usr/share/ibus-table/engine/ibus_table_location.py", line 102, in
<module>
__module_init = __ModuleInitializer()
File "/usr/share/ibus-table/engine/ibus_table_location.py", line 96, in
__init__
_init()
File "/usr/share/ibus-table/engine/ibus_table_location.py", line 76, in _init
os.makedirs(ibus_table_location['data_home'])
File "/usr/lib64/python3.5/os.py", line 241, in makedirs
mkdir(name, mode)
FileExistsError: [Errno 17] File exists:
'/home/mfabian/.local/share/ibus-table'
Local variables in innermost frame:
name: '/home/mfabian/.local/share/ibus-table'
mode: 511
tail: 'ibus-table'
head: '/home/mfabian/.local/share'
exist_ok: False
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 1 month
[Fedora-i18n-bugs] [Bug 1003412] New: Cinnamon desktop - Failed to Change input method
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1003412
Bug ID: 1003412
Summary: Cinnamon desktop - Failed to Change input method
Product: Fedora
Version: 20
Component: im-chooser
Assignee: tagoh(a)redhat.com
Reporter: aalam(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com
Created attachment 792685
--> https://bugzilla.redhat.com/attachment.cgi?id=792685&action=edit
Screenshot
Description of problem:
while Enabling Ibus with im-chooser in Cinnamon Desktop, it showing crashing
error message.
---
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._imsettings_2derror_2dquark.Code5:
Current desktop isn't targeted by IMSettings.
Please check /home/aalam/.cache/imsettings/log for more details
---
Version-Release number of selected component (if applicable):
cinnamon-1.9.2-0.20.git2d1ac4d.fc20.x86_64
ibus-1.5.3-1.fc20.x86_64
im-chooser-1.6.4-2.fc20.x86_64
How reproducible:
Steps to Reproduce:
1. Log in to Cinnamon desktop
2. Use im-chooser to enable Input method 'IBus'
3. Select ibus
4. Check message produced
Actual results:
ibus failed to enabled
Expected results:
it should work
Additional info:
1) I upgraded from Fedora 19 to Fedora 20
2) Log /home/aalam/.cache/imsettings/log
---
[ 1378076147.681857]: IMSettings-Daemon[4911]: INFO: Starting
imsettings-daemon...
[ 1378076147.682409]: IMSettings-Daemon[4911]: INFO:
[HOME=/home/aalam/.config/imsettings]
[ 1378076147.682698]: IMSettings-Daemon[4911]: INFO:
[XINPUTRCDIR=/etc/X11/xinit/]
[ 1378076147.682935]: IMSettings-Daemon[4911]: INFO:
[XINPUTDIR=/etc/X11/xinit/xinput.d/]
[ 1378076147.683171]: IMSettings-Daemon[4911]: INFO:
[MODULEDIR=/usr/lib64/imsettings]
[ 1378076147.683402]: IMSettings-Daemon[4911]: INFO: [MODULES=gsettings, qt]
[ 1378076147.688695]: IMSettings-Qt backend[4911]: WARNING **: Unable to obtain
the DefaultInputMethod: Key file does not have group 'Qt'
[ 1378076147.717047]: IMSettings-Qt backend[4911]: WARNING **: Unable to obtain
the DefaultInputMethod: Key file does not have group 'Qt'
[ 1378076147.763503]: IMSettings-Qt backend[4911]: WARNING **: Unable to obtain
the DefaultInputMethod: Key file does not have group 'Qt'
[ 1378076147.785706]: IMSettings-Qt backend[4911]: WARNING **: Unable to obtain
the DefaultInputMethod: Key file does not have group 'Qt'
imsettings information
==========================
XINPUTRC: /home/aalam/.config/imsettings/xinputrc
File: ‘/home/aalam/.config/imsettings/xinputrc’ ->
‘/etc/X11/xinit/xinput.d/ibus.conf’
Size: 33 Blocks: 0 IO Block: 4096 symbolic link
Device: 803h/2051d Inode: 3408583 Links: 1
Access: (0777/lrwxrwxrwx) Uid: ( 1000/ aalam) Gid: ( 1000/ aalam)
Context: unconfined_u:object_r:config_home_t:s0
Access: 2013-09-01 17:44:05.355457571 -0500
Modify: 2013-08-18 11:45:55.552064953 -0500
Change: 2013-08-18 11:45:55.552064953 -0500
Birth: -
Is DBus enabled: yes
Is imsettings enabled: yes
Is GTK+ supported:
[ 1378076147.908926]: IMSettings-Qt backend[4911]: WARNING **: Unable to obtain
the DefaultInputMethod: Key file does not have group 'Qt'
[ 1378076147.931150]: IMSettings-Qt backend[4911]: WARNING **: Unable to obtain
the DefaultInputMethod: Key file does not have group 'Qt'
yes
Is Qt supported:
[ 1378076147.963524]: IMSettings-Qt backend[4911]: WARNING **: Unable to obtain
the DefaultInputMethod: Key file does not have group 'Qt'
[ 1378076147.986057]: IMSettings-Qt backend[4911]: WARNING **: Unable to obtain
the DefaultInputMethod: Key file does not have group 'Qt'
yes
DESKTOP: cinnamon
GUESS_DESKTOP: $GDMSESSION
DISABLE_IMSETTINGS:
IMSETTINGS_DISABLE_DESKTOP_CHECK:
DBUS_SESSION_BUS_ADDRESS:
unix:abstract=/tmp/dbus-phX8IXOece,guid=831715cb30aa1e83d67a027c5223c5f3
GTK_IM_MODULE:
QT_IM_MODULE: ibus
XMODIFIERS: @im=ibus
IMSETTINGS_MODULE: IBus
IMSETTINGS_INTEGRATE_DESKTOP: yes
[ 1378076150.254946]: IMSettings-Qt backend[4911]: WARNING **: Unable to obtain
the DefaultInputMethod: Key file does not have group 'Qt'
[ 1378076152.050008]: IMSettings-Daemon[4911]: INFO: Attempting to switch IM to
IBus [lang=pa_IN.utf8, update=false]
** org.gnome.settings-daemon.plugins.keyboard.active is true. imsettings is
going to be disabled.
[ 1378076157.117726]: IMSettings-Daemon[4911]: WARNING **: Current desktop
isn't targeted by IMSettings.
[ 1378076157.161819]: IMSettings-Daemon[4911]: INFO: Unloading imesttings
module: qt
[ 1378076157.162348]: IMSettings-Daemon[4911]: INFO: Unloading imesttings
module: gsettings
[ 1378076157.162712]: IMSettings-Daemon[4911]: INFO: imsettings-daemon is shut
down.
[ 1378077301.984146]: IMSettings-Daemon[6447]: INFO: Starting
imsettings-daemon...
[ 1378077301.985509]: IMSettings-Daemon[6447]: INFO:
[HOME=/home/aalam/.config/imsettings]
[ 1378077301.985722]: IMSettings-Daemon[6447]: INFO:
[XINPUTRCDIR=/etc/X11/xinit/]
[ 1378077301.985892]: IMSettings-Daemon[6447]: INFO:
[XINPUTDIR=/etc/X11/xinit/xinput.d/]
[ 1378077301.986059]: IMSettings-Daemon[6447]: INFO:
[MODULEDIR=/usr/lib64/imsettings]
[ 1378077301.986226]: IMSettings-Daemon[6447]: INFO: [MODULES=gsettings, qt]
[ 1378077305.888658]: IMSettings-Daemon[6447]: INFO: Attempting to switch IM to
IBus [lang=pa_IN.utf8, update=true]
** org.gnome.settings-daemon.plugins.keyboard.active is true. imsettings is
going to be disabled.
[ 1378077306.544504]: IMSettings-Daemon[6447]: WARNING **: Current desktop
isn't targeted by IMSettings.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=hXXx7rBFUY&a=cc_unsubscribe
6 years, 3 months
[Fedora-i18n-bugs] [Bug 844555] New: new IME switcher prevents to send the key events to kvm
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=844555
Bug ID: 844555
QA Contact: extras-qa(a)fedoraproject.org
Severity: unspecified
Version: 17
Priority: unspecified
CC: i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
Assignee: tfujiwar(a)redhat.com
Summary: new IME switcher prevents to send the key events to
kvm
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: tagoh(a)redhat.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: ibus
Product: Fedora
Description of problem:
With the latest version of ibus on f17, ibus can't be turned on on kvm. it
works back when ibus on host machine is disabled.
Version-Release number of selected component (if applicable):
ibus-1.4.99.20120428-2.fc17.x86_64
How reproducible:
always
Steps to Reproduce:
1.run ibus on both host and guest
2.press ctrl+space on kvm
3.
Actual results:
the key events was ate on host. no IM activated on guest
Expected results:
should be turned on on kvm
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 4 months
[Fedora-i18n-bugs] [Bug 1319111] New: incorrect use of Requires(pre)?
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1319111
Bug ID: 1319111
Summary: incorrect use of Requires(pre)?
Product: Fedora
Version: rawhide
Component: ibus-table-extraphrase
Assignee: dchen(a)redhat.com
Reporter: jsilhan(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dchen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
liangsuilong(a)gmail.com
We've identified your package for having `Requires(pre)` RPM flag without
`Requires` [1]. `Requires(pre)` rpm tag could be interpreted wrongly, so to
prevent any harm to Fedora users I am notifying you about this fact.
Any package that is specified in `Requires(pre)` could be freely removed.
Citing from RPM pages:
```
If there are no other dependencies on the package providing /usr/sbin/useradd,
that package is permitted to be removed from the system after installation(!)
``` [2]
If you really rely on dependency just during the installation process and your
package don't necessary require the dependency for the proper run of your
application then ignore this bug report and close it as NOTABUG. Otherwise add
to your spec file additional `Requires` for the dependency, please.
[1] paste.fedoraproject.org/341611/82208431
[2] http://www.rpm.org/wiki/PackagerDocs/MoreOnDependencies
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 4 months
[Fedora-i18n-bugs] [Bug 1351287] New: Wrong placement of polish glyph Ogonek
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1351287
Bug ID: 1351287
Summary: Wrong placement of polish glyph Ogonek
Product: Fedora
Version: rawhide
Component: liberation-fonts
Assignee: psatpute(a)redhat.com
Reporter: riemersebastian(a)hotmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, psatpute(a)redhat.com
Description of problem:
The following text when using font "LiberationSans-Regular" renders the polish
Ogonek far to the right which does not seem correct when compared to other
fonts.
INPUT: "Lektura dla pocza̜tkuja̜cych"
Version-Release number of selected component (if applicable):
version 2.0.0 (Downloaded from
https://www.fontsquirrel.com/fonts/liberation-sans)
How reproducible:
Just use the text "Lektura dla pocza̜tkuja̜cych" and the problem should be
visible (and see below)
Steps to Reproduce:
1. Go to https://www.fontsquirrel.com/fonts/liberation-sans
2. Go to tab "Test drive"
3. Enter text "Lektura dla pocza̜tkuja̜cych"
Actual results:
The result shows the Ogonek way to the right and AFAIK it should render
centered below the letter 'a'.
Expected results:
Compare by same steps as above, but e.g. choose as font: Junicode
(https://www.fontsquirrel.com/fonts/Junicode)
Additional info:
None
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 4 months
[Fedora-i18n-bugs] [Bug 733106] New: fonts.alias refer to encodings not listed in fonts.dir
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: fonts.alias refer to encodings not listed in fonts.dir
https://bugzilla.redhat.com/show_bug.cgi?id=733106
Summary: fonts.alias refer to encodings not listed in fonts.dir
Product: Fedora
Version: rawhide
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: sazanami-fonts
AssignedTo: tagoh(a)redhat.com
ReportedBy: viy(a)altlinux.org
QAContact: extras-qa(a)fedoraproject.org
CC: tagoh(a)redhat.com, fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
Story Points: ---
Type: ---
fonts.alias files refer to jisx020*.19??-0 font encodings while fonts.dir does
not list them.
looks like a fonts.scale/fonts.dir generation bug.
/usr/share/X11/fonts/encodings/large/*
encodings should be present during fonts.scale/fonts.dir generation.
sazanami-fonts-0.20040629-15.fc15.src.rpm
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
6 years, 4 months
[Fedora-i18n-bugs] [Bug 825081] New: Lohit Kannada font does not properly handle vowel signs in consonant clusters
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=825081
Bug ID: 825081
QA Contact: extras-qa(a)fedoraproject.org
Severity: unspecified
Version: 16
Priority: unspecified
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, psatpute(a)redhat.com
Assignee: psatpute(a)redhat.com
Summary: Lohit Kannada font does not properly handle vowel
signs in consonant clusters
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: samjnaa(a)gmail.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: lohit-kannada-fonts
Product: Fedora
Created attachment 586752
--> https://bugzilla.redhat.com/attachment.cgi?id=586752&action=edit
ODT and PDF for test-case
Description of problem:
This seems to be a resurfacing of bug #223971 but since I saw no way to reopen
that bug (sorry if I'm wrong) I'm reporting this again.
Version-Release number of selected component (if applicable):
2.5.1
How reproducible:
In a word processor, select Lohit Kannada font and input Kannada Unicode
sequences having consonant clusters of the format CCV. I have attached a sample
ODT.
Actual results:
Except in a few cases of "popular" consonant clusters like K.SSA ಕ್ಷ and J.NYA
ಜ್ಞ, the vowel signs are not attached properly.
When the same text is rendered with other fonts (like Tunga of Microsoft even
loaded into Linux's LibreOffice) the sequences are shown properly without
overlaps or malformed glyphs.
Expected results:
The Kannada language uses lots of Sanskrit-based words and hence has many
consonant clusters with two and even three consonants. Also, when English words
are transliterated in Kannada script like ಎಕ್ಸ್ಪ್ಲೋರ್ (explore) etc for
sign-boards etc, even more consonant clusters will occur. In all these cases
Lohit Kannada should be able to gracefully handle such consonant clusters and
not output overlapping or malformed glyphs.
Additional info:
I have attached an ODT and PDF file demonstrating the problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 4 months
[Fedora-i18n-bugs] [Bug 827516] New: [kn_IN] Vowel Signs U and UU do not correctly attach to many consonants in Lohit Kannada
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=827516
Bug ID: 827516
QA Contact: extras-qa(a)fedoraproject.org
Severity: unspecified
Version: 16
Priority: unspecified
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, psatpute(a)redhat.com
Assignee: psatpute(a)redhat.com
Summary: [kn_IN] Vowel Signs U and UU do not correctly attach
to many consonants in Lohit Kannada
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: samjnaa(a)gmail.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: lohit-kannada-fonts
Product: Fedora
Created attachment 588536
--> https://bugzilla.redhat.com/attachment.cgi?id=588536&action=edit
ODT and PDF for test-case
Description of problem:
While most other CONSONANT + VOWEL SIGN combinations in Lohit Kannada are
mapped to precomposed glyphs, there are no pre-composed glyphs for vowel signs
U and UU except for the consonants PA, PHA and VA (where the stroke for U/UU
needs to come from below the consonant rather than the normal right side of the
consonant).
While in most cases, by virtue of appropriate RSB and LSB values of the
consonant glyph and vowel sign glyph, the simple sequence of the two glyphs
creates an appropriate appearance, this leaves out several instances where the
glyphs do not overlap at all and hence appear disjointed. For a professional
appearance of the font, this should be fixed.
Version-Release number of selected component (if applicable):
2.5.1
How reproducible:
Input all possible sequences of Kannada consonants with vowel signs U and UU.
(See attached ODT for text. Use BabelMap
[http://www.babelstone.co.uk/software/babelmap.html] if you want the
codepoints.)
Actual results:
You can see (as in the attached PDF) that some consonants do not properly get
attached to the vowel signs U and UU.
Expected results:
All consonants should properly get attached to the vowel signs U and UU.
Additional info:
Consonants which are not properly joined with vowel sign U:
KA* NYA DDA DA BA RA SSA** RRA LLLA***
* = see at high magnification
** = may need separate precomposed glyph with some adjustment to shape of left
side of vowel sign
*** = so-called FA of Kannada Unicode
Consonants which are not properly joined with vowel sign UU:
Those already listed above for U, plus GHA and LLA, due to the shorter height
of the left-side ending node of this vowel sign.
I think in most cases appropriate kerning should solve the problem, except for
SSA + -U/-UU, GHA + -UU and LLA + -UU where separate glyphs would be advisable.
It is curious to note that DDA DA and BA are all disjointed whereas their
aspirated counterparts DDHA DHA and BHA which all have only an additional
notch-like stroke at the bottom are correctly joined with the vowel sign. I
think the LSB RSB values are carelessly allotted in some cases, unfortunately.
Other problems:
CU JU -- the pointed part on the left of the vowel sign U passes through the
consonants and comes out above (see carefully) -- actually *negative* kerning
is needed here so that the pointed part should only enter the consonant and not
again exit it.
(It seems this problem does not occur for vowel sign UU due to the shorter
height of the left-side ending node of this vowel sign which causes a problem
with GHA and LLA instead -- see above!)
Note:
Unfortunately I will not be able to provide a TTF patch for this as I am
already short of time on my official projects. Please take care of it. Thank
you!
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 4 months
[Fedora-i18n-bugs] [Bug 839303] New: [ta_IN] Submission of glyphs for Tamil fractions/symbols to be included in the Lohit Tamil fonts
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=839303
Bug ID: 839303
QA Contact: extras-qa(a)fedoraproject.org
Severity: unspecified
Version: rawhide
Priority: unspecified
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, psatpute(a)redhat.com
Assignee: psatpute(a)redhat.com
Summary: [ta_IN] Submission of glyphs for Tamil
fractions/symbols to be included in the Lohit Tamil
fonts
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: samjnaa(a)gmail.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: lohit-tamil-fonts
Product: Fedora
Created attachment 597580
--> https://bugzilla.redhat.com/attachment.cgi?id=597580&action=edit
Lohit Tamil, Lohit Tamil Classical and Lohit Tamil Chart fonts with new
characters
Contributing new Tamil glyphs to Lohit Tamil family:
----------------------------------------------------
I have prepared a proposal to encode 62 characters for old Tamil fractions and
symbols to be encoded in Unicode. Seven of these are being proposed for the
Tamil BMP block and rest for a new Tamil Supplement block in the SMP.
For the glyphs required for the code chart I have largely devised new glyphs
based on existing Lohit Tamil glyphs under the derivative rights granted by the
OFL. Some glyphs which could not be derived, I created myself using Inkscape
and other tools.
I would like to donate all these glyphs to the Lohit project under the OFL for
eventual inclusion into the Lohit Tamil/Tamil Classical fonts. For now they may
be included in the PUA of an unofficial fork of the Lohit Tamil fonts. When
they are eventually encoded in Unicode, they may be officially mapped to the
new codepoints and included in the official distribution of the Lohit
Tamil/Tamil Classical fonts.
Using Lohit Tamil glyphs for Unicode code chart:
------------------------------------------------
In the proposal, I am also requesting the Unicode / ISO 10646 project editors
to use the Lohit Tamil font for the Unicode Tamil code charts (Tamil block, and
newly proposed Tamil Supplement block) because:
1) When the new characters are encoded and my glyphs used for the code chart,
it would look good to maintain stylistic uniformity in the code chart, and my
designed glyphs are stylistically like the Lohit Tamil glyphs as they are
mostly derived from them. So it would be good to use Lohit Tamil glyphs
throughout.
2) There are currently 72 Tamil characters in Unicode 6.1.0. The present
proposal almost doubles the number with 62 new characters. It would be a
significant and unnecessary effort for anyone else to duplicate my glyph design
work for so many characters to keep in with the current Tamil code chart font
style. So switching to Lohit Tamil for all glyphs is easier and advisable.
3) Personally I think the glyphs of Lohit Tamil are much "cleaner" than the
existing Tamil code chart font, and more representative of the nature and
beauty of the Tamil script.
4) The OFL already permits the use of the Lohit Tamil font (and its
derivatives) for any purpose, so there are (hopefully) no legal issues
pertaining which need to be cleared between Unicode and Red Hat (but of course,
IANAL).
I also sincerely request the cooperation of the Lohit / Fedora / Red Hat people
in permitting the Lohit Tamil glyphs to be used for the Unicode Tamil code
charts (i.e. for two blocks).
Fonts with new glyphs:
----------------------
I attach herewith a ZIP file containing three font files:
1) Lohit Tamil font, with newly proposed character glyphs mapped to the PUA.
2) Lohit Tamil Classical font, likewise.
3) Lohit Tamil Chart font, containing only glyphs required for the code chart
(for existing and new characters, totalling 134 in number, across two blocks
Tamil and Tamil Supplement) mapped to the existing and proposed characters for
convenience of Unicode / ISO 10646 editors.
Behaviour of new characters and requirement from the fonts' side:
-----------------------------------------------------------------
None of the newly proposed characters are combining characters in the sense of
combining marks. However, most of them are proposed for a new SMP Tamil block
and care might need to be taken for proper mapping so that on all platforms the
SMP characters are accessible.
There is only one sequence of characters which needs to ligate: TAMIL DIGIT ONE
௧ + TAMIL SIGN KALAM (which looks like TAMIL LETTER LLA ள) should always
ligate. I have also provided the ligature glyph after the glyphs for the
individual characters (mapped to PUA E03F) in the fonts 1 and 2 above. I have
not added any substitution mapping however as it is for now only temporarily in
the PUA.
Etcetera:
---------
It is my intention to submit the proposal within a week or so and I will
upload/link here a copy of the proposal.
If at all any changes are required to the set of glyphs as a result of any
feedback from scholars or other sources, I will upload fresh TTF font files.
I thank everyone, especially Pravin Satpute, for their support regarding this.
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 4 months