Re: Windows / font / text futures ...

d=107090> -- Text is poorly rendered to presentation mode canvas -- View this message in context: http://nabble.documentfoundation.org/Windows-font-text-futures-tp4177355p4212514.html Sent from the Dev mailing list archive at Nabble.com. ___ Li

Re: Windows / font / text futures ...

I'm replying from the digest so the thread may mess up. So much good stuff to agree with. I think it's clear that there is a difference between the process of getting glyphs on a screen (rendering) and working out which glyphs should go where at the run level (shaping) and at the paragraph

Re: Windows / font / text futures ...

On 07.03.2016 22:39, Norbert Thiebaud wrote: > I do think that the first step is to push the layouting tweaks/hacks > out of writer and into vcl itself, > make dxarray read-only, > and _then_ we are free to implement/improve stuff in vcl as desired. but wouldn't that mean refactoring 5 VCL

Re: Windows / font / text futures ...

On 2016/03/08 10:42 AM, Stephan Bergmann wrote: While this is an issue for actual math on potentially very large or very small numbers (which is, I assume, why calc is careful with it), and an issue for games with large 3D worlds, it can hardly be an issue for the magnitudes of numbers we deal

Re: Windows / font / text futures ...

On 03/07/2016 06:08 PM, Noel Grandin wrote: On 7 March 2016 at 18:22, Thorsten Behrens wrote: You're getting different rounding even depending on the flags your OS (or driver that happens to be in your process) sets. Seriously - I'm too lazy to dig out references,

Re: Windows / font / text futures ...

On Mon, Mar 7, 2016 at 5:20 PM, Chris Sherlock wrote: > > Do you have any code pointers where writer modifies the layout? sw/source/core/txtnode/fntcache.cxx Norbert ___ LibreOffice mailing list

Re: Windows / font / text futures ...

Not a criticism, when I was trying to follow the code I was feeling the same way! Your comment was very helpful, and I went from frustrated to amused :-) Chris Sent from my iPhone > On 8 Mar 2016, at 10:35 AM, Khaled Hosny wrote: > >> On Tue, Mar 08, 2016 at 10:18:47AM

Re: Windows / font / text futures ...

On Tue, Mar 08, 2016 at 10:18:47AM +1100, Chris Sherlock wrote: > On 8 Mar 2016, at 5:38 AM, Khaled Hosny wrote: > > > > On Mon, Mar 07, 2016 at 02:04:41PM +, Michael Meeks wrote: > >> Hi Thorsten, > >> > >>I missed your mail; please do maintain the CC if you want

Re: Windows / font / text futures ...

On 8 Mar 2016, at 8:39 AM, Norbert Thiebaud wrote: > > On Mon, Mar 7, 2016 at 10:22 AM, Thorsten Behrens > wrote: >> I'm afraid we're in for that regardless. Norbert, Khaled, Tor IIRC & a >> number of other hackers all came to the conclusion

Re: Windows / font / text futures ...

On 8 Mar 2016, at 5:38 AM, Khaled Hosny wrote: > > On Mon, Mar 07, 2016 at 02:04:41PM +, Michael Meeks wrote: >> Hi Thorsten, >> >> I missed your mail; please do maintain the CC if you want a prompt >> reply =) >> >> On Fri, 2016-03-04 at 00:43 +0100, Thorsten

Re: Windows / font / text futures ...

On Mon, Mar 7, 2016 at 10:22 AM, Thorsten Behrens wrote: > I'm afraid we're in for that regardless. Norbert, Khaled, Tor IIRC & a > number of other hackers all came to the conclusion that the vcl font > API / the way Writer is doing layout is in serious need for

Re: Windows / font / text futures ...

On Mon, Mar 7, 2016 at 8:04 AM, Michael Meeks wrote: > >> - as long as so much low-level layouting is still >> happening in Writer (dx arrays, kashida filling etc). > > Hmm; the dx array as I understand it is just a simplified form of > glyph > widths; Not

Re: Windows / font / text futures ...

On Mon, Mar 07, 2016 at 02:04:41PM +, Michael Meeks wrote: > Hi Thorsten, > > I missed your mail; please do maintain the CC if you want a prompt > reply =) > > On Fri, 2016-03-04 at 00:43 +0100, Thorsten Behrens wrote: > > > Having looked at this heap; and worse - the two different

Re: Windows / font / text futures ...

On Fri, Mar 04, 2016 at 12:04:38PM +, Caolán McNamara wrote: > On Thu, 2016-03-03 at 13:44 +, Michael Meeks wrote: > > Hi guys, > > > Anyhow - what to do ? > >  > > While we could switch to DirectWrite on windows, which may > > solve some > > of our problems; this will be in

Re: Windows / font / text futures ...

On 7 March 2016 at 18:22, Thorsten Behrens wrote: > You're getting different rounding even depending on the flags your OS > (or driver that happens to be in your process) sets. Seriously - I'm > too lazy to dig out references, but consider floating point math to be >

Re: Windows / font / text futures ...

Michael Meeks wrote: > I missed your mail; please do maintain the CC if you want a prompt > reply =) > Setting Reply-To would help me to remember that next time. ;) > Hmm; the dx array as I understand it is just a simplified form of > glyph widths; we could use rectangles for those

Re: Windows / font / text futures ...

Hi Michael, Am 07.03.2016 um 15:29 schrieb Michael Meeks: Hi Armin, Interesting mail; please do CC me on replies =) On Fri, 2016-03-04 at 11:25 +0100, Armin Le Grand wrote: On the danger no-one wants to hear it :-) - Primitives. If all text rendering would use them, all text

Re: Windows / font / text futures ...

Hi Armin, Interesting mail; please do CC me on replies =) On Fri, 2016-03-04 at 11:25 +0100, Armin Le Grand wrote: > On the danger no-one wants to hear it :-) - Primitives. If all text > rendering would use them, all text rendering could be handled in > system-specific renderer

Re: Windows / font / text futures ...

Hi Thorsten, I missed your mail; please do maintain the CC if you want a prompt reply =) On Fri, 2016-03-04 at 00:43 +0100, Thorsten Behrens wrote: > > Having looked at this heap; and worse - the two different heaps for > > Windows text rendering, and also the big pile of strange

Re: Windows / font / text futures ...

Caolan McNamara wrote: > On Windows, peer apps like firefox and chromium etc seem to follow > the pattern of eventually rendering their harfbuzz layouted text > with the DirectWrite apis, whether directly, or through skia or > through a forked cairo, that *seems* be where things end up. So that >

Re: Windows / font / text futures ...

On Thu, 2016-03-03 at 13:44 +, Michael Meeks wrote: > Hi guys, > Anyhow - what to do ? >  > While we could switch to DirectWrite on windows, which may > solve some > of our problems; this will be in itself disruptive. > > So - I believe that we should switch to using

Re: Windows / font / text futures ...

Hi Thorsten and Michael, Am 04.03.2016 um 00:43 schrieb Thorsten Behrens: Hi Michael, you write: Having looked at this heap; and worse - the two different heaps for Windows text rendering, and also the big pile of strange cross-platform issues with stacking diacritics, emojis etc. I'm

Re: Windows / font / text futures ...

Hi Michael, you write: > Having looked at this heap; and worse - the two different heaps for > Windows text rendering, and also the big pile of strange cross-platform > issues with stacking diacritics, emojis etc. I'm pretty convinced that > we cannot do a good job of consistent text

Windows / font / text futures ...

Hi guys, I've had the (mixed) pleasure of digging through the windows font rendering in recent days; and I must say - I'm not thoroughly thrilled with it =) Let me highlight a few of the problems. First we are using GDI for text rendering, and this is ~obsolete. Several