Introduction of a "type mode" and an "unicode mode" of input

[Samiur Rahman]

I now see it clearly: Even when you use fonts that you buy, they just
generate a glyph for an unicode character. The good thing about what I
suggest is that you don't actually need to buy that font, the free unicode
font can cover that. So the user just selects "choose character range,"
which is Western European or any other, and then "choose font."

On Sat, Jul 2, 2016 at 7:11 PM, Samiur Rahman <samiur11 at gmail.com> wrote:

> Jaroslaw wrote: "If so, as such place for its implementation isn't at
> Calligra level but at a computer operating system's level, even above Qt
> itself."
>
> You can select to type in your keyboard, by selecting your keyboard in the
> OS, but usually you need to buy or maybe possibly download a font for your
> language or script. The benefit of a "unicode mode" as an input mode in the
> office app is that you don't need to buy or download that font.
>
> Camilla wrote: "we have a dialog that allows you to enter specific
> charactes from any unicode range"
>
> But you can't actually "type" using those characters that you can choose
> as special characters.
>
> Camille also wrote: "yes it is true that the font used to show the text
> has to support the script. But a few free unicode fonts do exist already."
>
> A few unicode fonts do exist but only Arial Unicode MS commonly comes with
> Windows, I don't know what Linux makes available. The best way to use them,
> as I see it, is to implement the "unicode mode" of input in the office
> applications, with the two boxes "choose unicodfoe range" and "choose
> unicode font," in which you first specify which range you are typing it,
> and then choose from a number of fonts that support that range.
>
> Thanks.
>
> On Sat, Jul 2, 2016 at 6:40 PM, Camilla Boemann <cbo at boemann.dk> wrote:
>
>> Hi
>>
>> I don't  understand this either.
>>
>> 1) all text in calligra is unicode
>> 2) we have a dialog that allows you to enter specific charactes from any
>> unicode range
>> 3) yes it is true that the font used to show the text has to support the
>> script. But a few free unicode fonts do exist already
>>
>> On Saturday 02 July 2016 15:13:03 Huxshathra Theudanaz wrote:
>> > A distinction between two types of input, a "type mode" and an "unicode
>> > mode" in all Calligra applications. In "unicode mode," there should be
>> two
>> > boxes, one that asks to "choose unicodfoe range" and the other that
>> asks to
>> > "choose unicode font." Users should select an unicode range, such as
>> Greek
>> > or Cyrillic, and then choose from a number of unicode fonts, which
>> should
>> > come with Calligra, that support that range.
>> >
>> > "Type mode" and "unicode mode" are different even now. If someone wants
>> to
>> > type in non-Western European characters, they usually type in "type
>> mode"
>> > using fonts they buy. Another option is to type in an unicode font such
>> as
>> > Arial Unicode MS, and the other unicode fonts are obscure. As one plus,
>> > "unicode mode" of input will allow these typists to type in their
>> language
>> > or script without having at buy extra fonts.
>> >
>> > Plus word processors and email clients and apps usually do distinguish
>> > between "type" and "unicode." This feature will fully allow someone to
>> > type, create, and share documents in unicode.
>>
>> _______________________________________________
>> calligra-devel mailing list
>> calligra-devel at kde.org
>> https://mail.kde.org/mailman/listinfo/calligra-devel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/calligra-devel/attachments/20160702/2b54bb26/attachment.htm>