Re: How to number components of Calligra 3

2016-07-03 Thread Jaroslaw Staniek
On 3 July 2016 at 17:28, Camilla Boemann wrote: > On Sunday 03 July 2016 01:10:52 Jaroslaw Staniek wrote: > > How to number components of Calligra 3? I mean apps and libs. > > Well I wouldn't mind dates or codenames for the public versioning, but > versions numbers are also for internal usage, so

Re: How to number components of Calligra 3

2016-07-03 Thread Camilla Boemann
On Sunday 03 July 2016 01:10:52 Jaroslaw Staniek wrote: > How to number components of Calligra 3? I mean apps and libs. Well I wouldn't mind dates or codenames for the public versioning, but versions numbers are also for internal usage, so we know when we make big api/code changes And I see no

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

2016-07-03 Thread Jaroslaw Staniek
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

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

2016-07-03 Thread Friedrich W. H. Kossebau
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/ > >

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

2016-07-03 Thread 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/ > > Does that have a KF5 equivalent yet? > ​Nope and for a reason. In my

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

2016-07-03 Thread Jos van den Oever
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

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

2016-07-03 Thread Camilla Boemann
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

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

2016-07-03 Thread Jos van den Oever
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

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

2016-07-03 Thread René J . V . Bertin
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

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

2016-07-03 Thread Jaroslaw Staniek
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

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

2016-07-03 Thread Camilla Boemann
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