On Mon, Sep 24, 2018 at 8:32 AM Eric Pruitt wrote:
>
> On Sun, Sep 23, 2018 at 11:19:46PM -0700, AR Garbe wrote:
> > On 23 September 2018 at 11:56, Eric Pruitt wrote:
> > > It's not just about Emoji or anti-aliasing. If you work with languages
> > > that use non-Latin characters, support for fall
On Mon, Sep 24, 2018 at 09:15:55AM +0200, Silvan Jegen wrote:
> On Mon, Sep 24, 2018 at 8:32 AM Eric Pruitt wrote:
> >
> > On Sun, Sep 23, 2018 at 11:19:46PM -0700, AR Garbe wrote:
> > > On 23 September 2018 at 11:56, Eric Pruitt wrote:
> > > > It's not just about Emoji or anti-aliasing. If you w
Hiltjo Posthuma writes:
> On Mon, Sep 24, 2018 at 09:15:55AM +0200, Silvan Jegen wrote:
>> On Mon, Sep 24, 2018 at 8:32 AM Eric Pruitt wrote:
>> >
>> > On Sun, Sep 23, 2018 at 11:19:46PM -0700, AR Garbe wrote:
>> > > On 23 September 2018 at 11:56, Eric Pruitt wrote:
>> > > > It's not just about
On Mon, Sep 24, 2018 at 09:35:11AM +0200, Hiltjo Posthuma wrote:
> > I don't think we should throw out support for a feature that more than a
> > billion
> > people on the planet rely on. That doesn't mean that we can't rethink how we
> > go about supporting that feature though.
I remember the ti
On Mon, Sep 24, 2018 at 12:28:21PM +, sylvain.bertr...@gmail.com wrote:
> On Mon, Sep 24, 2018 at 09:35:11AM +0200, Hiltjo Posthuma wrote:
> > > I don't think we should throw out support for a feature that more than a
> > > billion
> > > people on the planet rely on. That doesn't mean that we
Anselm wrote:
> Back in the days I also concluded that the introduction of Xinerama
> and multihead support was a bad idea after all.
>
> What do you guys think about this idea?
A couple of ideas:
1. Having Xft and Xinerama support in the patches section
2. Create ifdefs for Xft as they are now
On Mon, Sep 24, 2018 at 09:35:11AM +0200, Hiltjo Posthuma wrote:
> > I don't think we should throw out support for a feature that more than a
> > billion
> > people on the planet rely on. That doesn't mean that we can't rethink how we
> > go about supporting that feature though.
Of course no, I a
On Sun, Sep 23, 2018 at 05:20:27PM +, sylvain.bertr...@gmail.com wrote:
> On Sun, Sep 23, 2018 at 09:22:00AM -0700, AR Garbe wrote:
> > On Sun, 23 Sep 2018 at 06:37, wrote:
>
> And has st a wayland backend or fork?
Yes, Michael Forney wrote it.
On Sun, Sep 23, 2018 at 10:07:45PM +0200, Silvan Jegen wrote:
> The author of the fork also maintains a simple Wayland drawing library[2]
> (which is also used in the Wayland st fork) and a Wayland compositor[3]
> library.
The author is the current maintainer of sbase.
> On 24 Sep 2018, at 17:27, Manu Raster wrote:
>
> Hiltjo Posthuma writes:
>
> On Mon, Sep 24, 2018 at 09:15:55AM +0200, Silvan Jegen wrote:
> On Mon, Sep 24, 2018 at 8:32 AM Eric Pruitt wrote:
>
>> On Sun, Sep 23, 2018 at 11:19:46PM -0700, AR Garbe wrote:
>> On 23 Septemb
Hi,
It seems my previous message did not went through.
I was showing how mlterm reach this goal:
in a config file, in a table in the config header for st, a mapping
between style(bold/non-bold)/unicode range to a font name.
--
Sylvain
Couldn't this be done like rxvt-unicode (or the current st fontarray patch)? You
specify a list of fonts, and the program iterates on it until it finds one that
provide the required character. With a very basic cache, it's pretty simple and
doesn't causes problems.
Of course, the range:font mappin
On Mon, Sep 24, 2018 at 05:44:40PM +0200, Hadrien Lacour wrote:
> Of course, the range:font mapping is more granular, but I find it a little bit
> more complex to configure than this type of fallback.
It does as some asian fonts do contain some latin glyphs. You have to specify
the unicode range,
> On 24 Sep 2018, at 21:14, Roberto E. Vargas Caballero wrote:
>
> On Mon, Sep 24, 2018 at 09:35:11AM +0200, Hiltjo Posthuma wrote:
>>> I don't think we should throw out support for a feature that more than a
>>> billion
>>> people on the planet rely on. That doesn't mean that we can't rethink h
On Mon, Sep 24, 2018 at 04:08:17PM +, sylvain.bertr...@gmail.com wrote:
> On Mon, Sep 24, 2018 at 05:44:40PM +0200, Hadrien Lacour wrote:
> > Of course, the range:font mapping is more granular, but I find it a little
> > bit
> > more complex to configure than this type of fallback.
>
> It does
On Mon, 24 Sep 2018 18:28:16 +0200, Hadrien Lacour
wrote:
> Then you put your latin font first, since those usually don't contain CJK
> characters. The only case where it could gives problems is if you don't want
> fallback but really a merger of your fonts: e.g. using Terminus but wanting a
>
Hi there,
On Mon, 24 Sep 2018 at 06:42, Cág wrote:
> Anselm wrote:
> > Back in the days I also concluded that the introduction of Xinerama
> > and multihead support was a bad idea after all.
> >
> > What do you guys think about this idea?
>
> A couple of ideas:
> 1. Having Xft and Xinerama suppor
"Eon S. Jeon" writes:
>>> Hiltjo Posthuma writes:
>>> I agree its useful. (Complex) fall-back font support has been on my mind
>>> also.
>>> An idea could be of instead of supporting fallback fonts we could write some
>>> font merge script (pre-runtime).
>>
>> Very good! That's where the prob
[2018-09-24 16:16] "Roberto E. Vargas Caballero"
>
> On Sun, Sep 23, 2018 at 10:07:45PM +0200, Silvan Jegen wrote:
> > The author of the fork also maintains a simple Wayland drawing library[2]
> > (which is also used in the Wayland st fork) and a Wayland compositor[3]
> > library.
>
> The author
On Mon, Sep 24, 2018 at 09:22:14PM +0600, Eon S. Jeon wrote:
> Hello, Manu.
>
> Sorry, but merging font is not a good option.
>
> Each font contains settings like height, padding and hinting
> parameters, which are optimized for its glyphs by designers. So,
> merging fonts (or importing glyphs from
20 matches
Mail list logo
