2012/6/8 Uwe Stöhr:
> +void GuiDocument::languageChanged(int i)
> +{
> + // some languages only work with polyglossia/XeTeX
> + string current_language = lyx::languages.getLanguage(
> +
> fromqstr(langModule->languageCO->itemData(i).toString()))->lang();
> + if (cur
Am 08.06.2012 05:16, schrieb Richard Heck:
I think the changes are quite straight forward. If possible I would like to
have it in for LyX
2.0.4. I'll now be away for about 2 weeks and cannot commit. So please commit
it if you agree with
the patch.
Hmm, the support for polyglossia is half-bak
On 6/7/12 9:46 PM, Uwe Stöhr wrote:
Attached is a patch for tex2lyx in branch.
It adds support to import the font names when fontspec is used.
It also supports polyglossia so that files using it can directly be
viewed after importing.
I think the changes are quite straight forward. If possible
Attached is a patch for tex2lyx in branch.
It adds support to import the font names when fontspec is used.
It also supports polyglossia so that files using it can directly be viewed
after importing.
I think the changes are quite straight forward. If possible I would like to have it in for LyX
2
Attached is a patch for tex2lyx in branch.
It adds support to import the font names when fontspec is used.
It also supports polyglossia so that files using it can directly be viewed
after importing.
I think the changes are quite straight forward. If possible I would like to have it in for LyX
2
On 07/06/12 06:58, Stephan Witt wrote:
Perhaps. IMHO, the problem is caused by the text drawing algorithm of
LyX. The program does "finger-painting" the text and has to compute
all the positions of the text parts and lines itself.
One question: does LyX redraw the whole screen even when scroll
On 04/06/12 18:22, Richard Heck wrote:
The problem turns out to be that the paragraph we are redrawing here
references a non-existent Layout. This is because the copy_params()
routine in FindAndReplace.cpp, although it MAKES a new DocumentClass,
it never APPLIES this new DocumentClass to its Bu
On 06/07/2012 11:33 AM, Jean-Marc Lasgouttes wrote:
Le 07/06/2012 17:21, Jean-Marc Lasgouttes a écrit :
The branch, master, has been updated.
- Log -
commit 0ef36860c380626cc0930b34144794166fc1adb6
Author: Jean-Marc Lasgouttes
Dat
On 06/07/2012 11:21 AM, Jean-Marc Lasgouttes wrote:
The branch, master, has been updated.
- Log -
commit 0ef36860c380626cc0930b34144794166fc1adb6
Author: Jean-Marc Lasgouttes
Date: Thu Jun 7 17:19:04 2012 +0200
Handle sendi
Le 07/06/2012 17:21, Jean-Marc Lasgouttes a écrit :
The branch, master, has been updated.
- Log -
commit 0ef36860c380626cc0930b34144794166fc1adb6
Author: Jean-Marc Lasgouttes
Date: Thu Jun 7 17:19:04 2012 +0200
Handle sendi
Le 07/06/2012 12:09, Stephan Witt a écrit :
Is there some pkgconfig (*.pc) information in these macports builds? In this
case, the Qt detection code should be able to know what libraries to link
against.
Yes.
[...]
But I'm afraid using pkgconfig results in a LyX with hard macports dependen
Le 04/06/2012 22:54, Jerry a écrit :
On Jun 4, 2012, at 5:09 AM, Pavel Sanda wrote:
Jerry wrote:
__nl_find_msg in libintl.a(dcigettext.o)
Do you have gettext installed? P
On my OSX 10.7.4 system, gettext (and automake and autoconf) are provided by
Macports and live in /opt/local/bi
Am 07.06.2012 um 12:02 schrieb Jean-Marc Lasgouttes:
> Le 07/06/2012 11:58, Stephan Witt a écrit :
>> When using a library from /opt/local/lib, e.g. QtCore, you are forced to use
>> the libs used when building QtCore.
>> If QtCore was build with libiconv from /opt/local/bin you have to use this
Le 07/06/2012 11:58, Stephan Witt a écrit :
When using a library from /opt/local/lib, e.g. QtCore, you are forced to use
the libs used when building QtCore.
If QtCore was build with libiconv from /opt/local/bin you have to use this one
when linking LyX.
But the linker does the implicit lookup o
Am 07.06.2012 um 11:05 schrieb Vincent van Ravesteijn:
> Op 7-6-2012 4:41, Jerry schreef:
>> With help from Benjamin on this list and Ryan from the Macports list, I
>> discovered that I need to include
>> "-liconv" in the LDFLAGS variable. That fixed the problem.
>>
>> Jerry
>
> Shouldn't this
Op 7-6-2012 4:41, Jerry schreef:
With help from Benjamin on this list and Ryan from the Macports list, I
discovered that I need to include
"-liconv" in the LDFLAGS variable. That fixed the problem.
Jerry
Shouldn't this option be set by default ?
Vincent
Am 07.06.2012 um 08:51 schrieb Benjamin Piwowarski:
> Hi,
>
> I am not sure why this happens - it should work. Could you give me the
> command lines you used?
$ export LDFLAGS=-isysroot /Developer/SDKs/MacOSX10.5.sdk -arch i386
-mmacosx-version-min=10.4
$ export CPPFLAGS=-isysroot /Developer/S
17 matches
Mail list logo
