On 3 July 2016 at 15:10, Friedrich W. H. Kossebau wrote:
> Am Sonntag, 3. Juli 2016, 12:40:52 CEST schrieb Jaroslaw Staniek:
> > On 3 July 2016 at 11:58, René J.V. wrote:
> > > On Sunday July 03 2016 11:28:28 Jaroslaw Staniek wrote:
> > > >On a GUI level: There's KDE GUI for that (there are many
Am Sonntag, 3. Juli 2016, 12:40:52 CEST schrieb Jaroslaw Staniek:
> On 3 July 2016 at 11:58, René J.V. wrote:
> > On Sunday July 03 2016 11:28:28 Jaroslaw Staniek wrote:
> > >On a GUI level: There's KDE GUI for that (there are many equivalents):
> > >https://utils.kde.org/projects/kcharselect/
> >
On 3 July 2016 at 11:58, René J.V. wrote:
> On Sunday July 03 2016 11:28:28 Jaroslaw Staniek wrote:
>
> >On a GUI level: There's KDE GUI for that (there are many equivalents):
> >https://utils.kde.org/projects/kcharselect/
>
> Does that have a KF5 equivalent yet?
>
Nope and for a reason. In my
On Saturday 02 July 2016 15:58:22 Huxshathra Theudanaz wrote:
> This will be a novel feature. Let's fully utilize unicode.
>
GNU Unifont has a very large coverage of unicode. It even has ⍥ ⏲⏳♘♨.
http://unifoundry.com/unifont.html
Cheers,
Jos
___
cal
On Sunday 03 July 2016 12:06:40 Jos van den Oever wrote:
> On Sunday 03 July 2016 10:54:21 Camilla Boemann wrote:
> > I feel that you mean something else like a way to select several "current
> > fonts" rather than just a single font. And a way to assign what unicode
> > range uses what font. Such
On Sunday 03 July 2016 10:54:21 Camilla Boemann wrote:
> I feel that you mean something else like a way to select several "current
> fonts" rather than just a single font. And a way to assign what unicode
> range uses what font. Such multifont selection is only useful when you mix
> different scrip
On Sunday July 03 2016 11:28:28 Jaroslaw Staniek wrote:
>On a GUI level: There's KDE GUI for that (there are many equivalents):
>https://utils.kde.org/projects/kcharselect/
Does that have a KF5 equivalent yet?
>It's not the input method so someone needs to turn that input method. As
>you can see
On 3 July 2016 at 02:16, Samiur Rahman wrote:
>
> > And yes, free non-unicode fonts that support any range of unicode, such
as a
>
> > language or script, should come with Calligra.
>
> "Maybe on Windows or Mac. Because on Linux font files are typically a
property of operating systems."
>
> It's e
On Saturday 02 July 2016 21:18:05 Samiur Rahman wrote:
> The box should actually say "“Choose character set."
Definitely not. We use unicode and nothing else. We want to support the entire
world. But we don't ship fonts and we don't provide input methods for other
languages. Both tasks fall unde
The box should actually say "“Choose character set."
On Sat, Jul 2, 2016 at 8:45 PM, Samiur Rahman wrote:
> I'm fixing a few mistakes.
>
> > And yes, free non-unicode fonts that support any range of unicode, such
> as a
> > language or script, should come with Calligra.
>
> "Maybe on Windows or
I'm fixing a few mistakes.
> And yes, free non-unicode fonts that support any range of unicode, such
as a
> language or script, should come with Calligra.
"Maybe on Windows or Mac. Because on Linux font files are typically a
property of operating systems."
It's easy to install fonts to the OS, a
> And yes, free non-unicode fonts that support any range of unicode, such
as a
> language or script, should come with Calligra.
"Maybe on Windows or Mac. Because on Linux font files are typically a
property of operating systems."
It's easy to install fonts to the OS, at least in Windows, and can
On 3 July 2016 at 01:37, Samiur Rahman wrote:
> And yes, free non-unicode fonts that support any range of unicode, such as a
> language or script, should come with Calligra.
Maybe on Windows or Mac. Because on Linux font files are typically a
property of operating systems.
"Usually, we presume t
And yes, free non-unicode fonts that support any range of unicode, such as
a language or script, should come with Calligra.
On Sat, Jul 2, 2016 at 7:35 PM, Samiur Rahman wrote:
> What I see is that if it's a practice to include all free unicode fonts in
> an office suite, in order to use them co
What I see is that if it's a practice to include all free unicode fonts in
an office suite, in order to use them commonly, all office suites, even
operating systems, must come with them. But it's a good practice to start
on. Usually, we presume that the user needs only characters for Western
Europe
On 3 July 2016 at 01:11, Samiur Rahman 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 usual
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 We
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 y
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 Saturd
On 2 July 2016 at 23:01,
Huxshathra Theudanaz wrote:
> Let's use my actual name now. I put that name together. Huxshathra is an
> old Iranian name, and Theudanaz is old Germanic for Teuton.
>
> I guess you guys understand.
>
> I really want this feature to be implemented.
>
Hi Huxshathra
Let's use my actual name now. I put that name together. Huxshathra is an
old Iranian name, and Theudanaz is old Germanic for Teuton.
I guess you guys understand.
I really want this feature to be implemented.
On Sat, Jul 2, 2016 at 3:58 PM, Huxshathra Theudanaz
wrote:
> This will be a novel fea
This will be a novel feature. Let's fully utilize unicode.
On Sat, Jul 2, 2016 at 3:13 PM, 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
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
o
23 matches
Mail list logo
