On Sat, Dec 03, 2016 at 10:51:56PM -0700, Joel Kulesza wrote:
> In general, I've had some difficulty getting Korean to work well. There
> seem to have been several issues lately with Arabic, Hebrew, and Korean.
> Would there be value in providing an additional Help menu addressing some
> of the va
On Sat, Dec 3, 2016 at 8:53 PM, Scott Kostyshak wrote:
>
> Indeed. I've seen that mentioned a few places but never tested it.
> I wonder if we should mention this in the GuiSymbols dialog?
In general, I've had some difficulty getting Korean to work well. There
seem to have been several issues l
On 12/02/2016 07:05 PM, Enrico Forestieri wrote:
> On Fri, Dec 02, 2016 at 12:27:03AM +0100, Enrico Forestieri wrote:
>> On Thu, Dec 01, 2016 at 04:31:44PM -0500, Richard Heck wrote:
>>> I'm no expert on this part of the code, but this doesn't look too
>>> dangerous. Since 2.2.3 is still a little w
On Sun, Dec 04, 2016 at 03:27:42AM +0100, Kornel Benko wrote:
> I can see them. You probably have to use different input encoding (here utf8).
Indeed. I've seen that mentioned a few places but never tested it.
I wonder if we should mention this in the GuiSymbols dialog?
Scott
signature.asc
Des
Am Samstag, 3. Dezember 2016 um 21:10:54, schrieb Scott Kostyshak
> On Sat, Dec 03, 2016 at 11:40:49PM +0100, Guillaume Munch wrote:
> > Le 02/12/2016 à 08:03, Scott Kostyshak a écrit :
> > > On Sat, Nov 19, 2016 at 12:41:13AM +0100, Guillaume Munch wrote:
> > >
> > > > I cannot reproduce with t
On Sat, Dec 03, 2016 at 11:40:49PM +0100, Guillaume Munch wrote:
> Le 02/12/2016 à 08:03, Scott Kostyshak a écrit :
> > On Sat, Nov 19, 2016 at 12:41:13AM +0100, Guillaume Munch wrote:
> >
> > > I cannot reproduce with the provided info (2.3dev & Qt5).
> >
> > A bisect led to b3bed292. The attach
On Sat, Dec 03, 2016 at 10:26:17PM +0100, mn wrote:
> On 03.12.16 21:43, Scott Kostyshak wrote:
>
> >> BTW:
> >> Until now I only had simple and short strings entered myself into an
> >> otherwise empty document.
> >> Copying this rather complex but still short example into LyX makes it
> >> quite
On Sat, Dec 03, 2016 at 11:59:33PM +0100, Guillaume Munch wrote:
>
> This is the same as
> https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg196794.html. I
> have now backported the fix.
Hmmm... a quite convoluted patch. There was a one-liner fixing this.
--
Enrico
Le 30/11/2016 à 16:48, Jean-Marc Lasgouttes a écrit :
a useless backtrace
If you have the symbols at hand, then you can get them by hand. For
instance if you have compiled in debug mode, then you can run gdb as you
do usually, only after the fact, and get the symbols with "info symbols
0x123
Le 02/12/2016 à 01:08, Richard Heck a écrit :
On 12/01/2016 06:44 PM, Enrico Forestieri wrote:
On Thu, Dec 01, 2016 at 07:50:19PM +0100, Enrico Forestieri wrote:
This only occurs with 2.2.3dev (not with 2.2.2, nor with 2.3.0dev):
1) Start lyx, make sure the source pane is closed
2) File->New
Le 02/12/2016 à 08:03, Scott Kostyshak a écrit :
On Sat, Nov 19, 2016 at 12:41:13AM +0100, Guillaume Munch wrote:
I cannot reproduce with the provided info (2.3dev & Qt5).
A bisect led to b3bed292. The attached patch fixes it for me, although I
don't understand my patch.
Hello Scott,
Nothi
Op 03-12-16 om 23:03 schreef Cor Blom:
Op 03-12-16 om 22:51 schreef Scott Kostyshak:
The fonts are the issue, both screenfonts and document fonts. Lyx
allows for
both to set only one font and many fonts do not support rtl languages
properly. I think what LibreOffice does (and I think Ms Office d
On 03.12.16 22:51, Scott Kostyshak wrote:
>> The fonts are the issue, both screenfonts and document fonts. Lyx allows for
>> both to set only one font and many fonts do not support rtl languages
>> properly. I think what LibreOffice does (and I think Ms Office does the
>> same) is a way to go: add
Op 03-12-16 om 22:51 schreef Scott Kostyshak:
The fonts are the issue, both screenfonts and document fonts. Lyx allows for
both to set only one font and many fonts do not support rtl languages
properly. I think what LibreOffice does (and I think Ms Office does the
same) is a way to go: add a sepa
On Sat, Dec 03, 2016 at 10:26:17PM +0100, mn wrote:
> On 03.12.16 21:43, Scott Kostyshak wrote:
>
> >> BTW:
> >> Until now I only had simple and short strings entered myself into an
> >> otherwise empty document.
> >> Copying this rather complex but still short example into LyX makes it
> >> quite
Op 03-12-16 om 22:24 schreef mn:
Where can the polyglossia option be set?
This is not obvious to me.
Under doc-settings>language>language package>custom = polyglossia ?
Yes, I have to admit: this is not obvious. The setting "automatic" works
for me, it give me polyglossia (although it is not e
On Sat, Dec 03, 2016 at 10:24:54PM +0100, mn wrote:
> > \newfontfamily\hebrewfont[Script=Hebrew]{SBL Hebrew}
> >
> > For each script a separate font can be set. Options like "Scale"
> > automatically scales the font so that it fits with the rest.
>
> That sounds brilliant.
Depending on your do
On 03.12.16 21:43, Scott Kostyshak wrote:
>> BTW:
>> Until now I only had simple and short strings entered myself into an
>> otherwise empty document.
>> Copying this rather complex but still short example into LyX makes it
>> quite slow to handle and beachballing a lot. There seems to be a proble
On 03.12.16 21:49, Cor Blom wrote:
> Op 03-12-16 om 20:57 schreef mn:
>> This font-switcheroo must go into the preamble, I am guessing now since
>> I am new to Xetex also.
>> But apparently this is not possible within LyX's gui?
>
> No, it is not. You need polyglossia for that (which can be set in
Op 03-12-16 om 21:43 schreef Scott Kostyshak:
Mike, I'm CC'ing a few people who have LyX + Hebrew knowledge. Perhaps
one of them is interested in joining this conversation about how we can
improve LyX to make it easier for users of Hebrew.
If I may offer some suggestions... I am not a programme
Op 03-12-16 om 22:06 schreef Scott Kostyshak:
On Sat, Dec 03, 2016 at 09:49:09PM +0100, Cor Blom wrote:
Op 03-12-16 om 20:57 schreef mn:
This font-switcheroo must go into the preamble, I am guessing now since
I am new to Xetex also.
But apparently this is not possible within LyX's gui?
No, it
On Sat, Dec 03, 2016 at 09:49:09PM +0100, Cor Blom wrote:
> Op 03-12-16 om 20:57 schreef mn:
> > This font-switcheroo must go into the preamble, I am guessing now since
> > I am new to Xetex also.
> > But apparently this is not possible within LyX's gui?
>
> No, it is not. You need polyglossia for
Op 03-12-16 om 20:57 schreef mn:
This font-switcheroo must go into the preamble, I am guessing now since
I am new to Xetex also.
But apparently this is not possible within LyX's gui?
No, it is not. You need polyglossia for that (which can be set in Lyx
gui) and something like this in the pream
On Sat, Dec 03, 2016 at 08:57:14PM +0100, mn wrote:
> On 03.12.16 18:49, Scott Kostyshak wrote:
Mike, I'm CC'ing a few people who have LyX + Hebrew knowledge. Perhaps
one of them is interested in joining this conversation about how we can
improve LyX to make it easier for users of Hebrew. If they
There might be some incorrect or unexpected behavior when switching
output engines in LyX, because Xetex does not support input-encoding
settings:
To reproduce:
Start a document, go to setup:
- first try something for pdflatex and
define under language: input encodig to other (here it was utf8)
(
On 03.12.16 18:49, Scott Kostyshak wrote:
> On Sat, Dec 03, 2016 at 04:42:57PM +0100, mn wrote:
>> So I wanted to get started with ancient Hebrew texts.
>> Using Texlive-full, LyX and my usual setup I ran immediately into
>> problems, quite severe.
>> Searched tutorials for doing such a thing and n
So I wanted to get started with ancient Hebrew texts.
Using Texlive-full, LyX and my usual setup I ran immediately into
problems, quite severe.
Searched tutorials for doing such a thing and nothing of this kind worked.
Not even he-intro.lyx does compile.
That's why this question goes to devel.
As a
On Sat, Dec 03, 2016 at 10:55:37AM +0100, racoon wrote:
> On 03.12.2016 10:35, Andrew Parsloe wrote:
> > I would need to download bleeding-edge lyx to test this and it's not
> > clear to me that this is being maintained now -- there's a reference to
> > master and 2.1.x on the website, no mention
On 03.12.2016 10:35, Andrew Parsloe wrote:
On 2/12/2016 7:11 p.m., Scott Kostyshak wrote:
On Wed, Nov 02, 2016 at 09:56:39AM +1300, Andrew Parsloe wrote:
The assertion message references Paragraph.cpp, line 1723.
Andrew can you reproduce this on current master?
Scott
I would need to downl
On 2/12/2016 7:11 p.m., Scott Kostyshak wrote:
On Wed, Nov 02, 2016 at 09:56:39AM +1300, Andrew Parsloe wrote:
The assertion message references Paragraph.cpp, line 1723.
Andrew can you reproduce this on current master?
Scott
I would need to download bleeding-edge lyx to test this and it's n
30 matches
Mail list logo
