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 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
Thanks for that. First thing, I noticed you used RelWithDebInfo so it
looks like you stopped applying options at the very beginning of
instructions. I am looking at a way to improve them; RelWithDebInfo
isn't too useful for debugging.
On 25 January 2015 at 19:15, Kamalpreet Grewal wrote:
> On Sun
On Sun, Jan 25, 2015 at 11:44 PM, Kamalpreet Grewal
wrote:
> Is something
> more to be inspected to get
to get the necessary details?
--
Kamalpreet Kaur Grewal
Blog: http://kamalpreetgrewal.com/
___
calligra-devel mailing list
calligra-devel@kde.org
h
On Sun, Jan 25, 2015 at 11:17 PM, Jaroslaw Staniek wrote:
> Could you please help us help and give answers to my questions? Others
> would benefit too.
> Instructions can be improved only this way. This is a team sport :)
Yes. And it is done.
--
Kamalpreet Kaur Grewal
Blog: http://kamalpreetgre
On Sun, Jan 25, 2015 at 12:58 AM, Jaroslaw Staniek wrote:
> Hmm, a couple of questions. What's your OS? Please provide all details you
> can.
> The logs shows that's a non-windows, a non-X11 platform.
> Are these entire logs?
I have Linux Mint 17 on my HP laptop. I showed the CMakeError.log
file
On 25 January 2015 at 11:40, Kamalpreet Grewal wrote:
> On Sun, Jan 25, 2015 at 3:10 AM, Boudewijn Rempt wrote:
>> This is about the most basic of issues: you haven't installed the
>> development packages for Qt. That means you have not followed the build
>> instructions I linked to.
>
> I went t
On Sun, Jan 25, 2015 at 3:10 AM, Boudewijn Rempt wrote:
> This is about the most basic of issues: you haven't installed the
> development packages for Qt. That means you have not followed the build
> instructions I linked to.
I went through all the instructions. Something was wrong with
libphonon
Hi Kamalpreet,
This is about the most basic of issues: you haven't installed the
development packages for Qt. That means you have not followed the build
instructions I linked to.
On Sat, 24 Jan 2015, Kamalpreet Grewal wrote:
On Sat, Jan 17, 2015 at 3:07 PM, Boudewijn Rempt wrote:
The fir
Hmm, a couple of questions. What's your OS? Please provide all details you can.
The logs shows that's a non-windows, a non-X11 platform.
Are these entire logs?
Do you have "kdelibs and kdelibs development files " as specified in
the build instructions?
What was your cmake command exactly?
On 24
On Sat, Jan 24, 2015 at 11:45 PM, Jaroslaw Staniek wrote:
> In such cases it's better to paste.kde.org entire cmake cache.
It is here: http://goo.gl/WnUpBy
--
Kamalpreet Kaur Grewal
Blog: http://kamalpreetgrewal.com/
___
calligra-devel mailing list
ca
Hello,
In such cases it's better to paste.kde.org entire cmake cache.
PS: http://community.kde.org/Calligra/First_Contact
On 24 January 2015 at 19:12, Kamalpreet Grewal wrote:
> On Sat, Jan 17, 2015 at 3:07 PM, Boudewijn Rempt wrote:
>> The first step is to build calligra:
>> http://community.
On Sat, Jan 17, 2015 at 3:07 PM, Boudewijn Rempt wrote:
> The first step is to build calligra:
> http://community.kde.org/Calligra/Building/Building_Calligra
> Then, play with the applications to get a good feel for them, then choose a
> subject to work on!
I have got the source code on my syst
Hi Kamalpreet,
The first step is to build calligra:
http://community.kde.org/Calligra/Building/Building_Calligra
Then, play with the applications to get a good feel for them, then choose a
subject to work on!
On Saturday 17 January 2015 Jan 12:22:52 Kamalpreet Grewal wrote:
> Hi
>
> My name i
33 matches
Mail list logo
