On Sun, May 26, 2013 at 4:16 PM, Scott Kostyshak wrote:
> It's good to know that it works for you with TeX Live 2012. The Farsi
> splash was failing under a manual install of TeX Live 2012 also. I
> will look into this.
Good news -- the document compiles with TeX Live 2013.
Scott
Jürgen or Uwe,
Can you try to fix the French User Guide? I can fix it so that it
compiles on 2.1git or so that it compiles on 2.0git but I cannot get
it so that it compiles on both, which I assume is what we want.
Scott
On 05/26/2013 09:35 AM, Liviu Andronic wrote:
Hello,
On Thu, May 23, 2013 at 10:11 PM, Richard Heck wrote:
I have posted a lyx2lyx conversion routine to the bug report
http://www.lyx.org/trac/ticket/8588#comment:23
Please test and let me know if there are problems. If so, please post the
Dear Hashini,
Welcome to Google Summer of Code. Please take things slowly for now and
focus on your exams, as they have the first priority. There is still time
for everything else in two weeks.
Of course we can start brainstorming about some of the details now, as that
does not take much time
On 05/27/2013 10:03 PM, Hashini Senaratne wrote:
Hello all,
I am glad to hear that my proposal "Horizontal scrollbar for tables and math for
LyX" submitted has been accepted for Google Summer of Code 2013. Thank you (all the
developers and specially my two mentors; Jean and Scott) very much fo
Hello all,
I am glad to hear that my proposal "Horizontal scrollbar for tables and math
for LyX" submitted has been accepted for Google Summer of Code 2013. Thank
you (all the developers and specially my two mentors; Jean and Scott) very
much for helping me by providing advice and relevant deta
On Mon, May 27, 2013 at 8:07 PM, Andrew Parsloe wrote:
> On 27/05/2013 8:16 p.m., Scott Kostyshak wrote:
I have some buglettes in random notes that I wanted to eventually look
at. I told someone else that I would organize them and post them. I
will try to do that soon. I will put th
On 27/05/2013 8:16 p.m., Scott Kostyshak wrote:
On Fri, May 3, 2013 at 2:17 PM, Elmar Hinz wrote:
Now I would like to fix some bugs.
I have some buglettes in random notes that I wanted to eventually look
at. I told someone else that I would organize them and post them. I
will try to do that s
Am 27.05.2013 22:26, schrieb Scott Kostyshak:
I just want to note that I can successfully export the Chinese
template ctex.lyx with pdfTeX and with XeTeX.
ctex seems to do all necessary things for the user - very convenient.
I can export both the Chinese Intro and Tutorial files with pdfTeX,
On Mon, May 27, 2013 at 4:05 PM, Uwe Stöhr wrote:
> Due to the problems Scott had with LuaTeX and non-western scripts like
> Arabic, I investigated what the 3 main engines LuaTeX, XeTeX and pdfTeX can
> do and updated their Wiki pages accordingly:
Thanks for doing this.
> In the XeTeX page there
Op 27-5-2013 18:05, Jean-Marc Lasgouttes schreef:
24/05/2013 15:07, Vincent van Ravesteijn:
By the way, this doesn't always work. The kill-gettext branch, for
instance, has master merged in a few times to fix merge conflicts. Now,
rebasing onto the merge-base does do no good.
Vincent, I want t
On Mon, May 27, 2013 at 3:57 PM, Vincent van Ravesteijn wrote:
> But please be sure that you know when something is easy to fix or not ;)..
> (see bug #8664).
Thanks for correcting that, Vincent. OK I will be more careful.
However, I will never be sure unless I actually solve the bug myself.
Op 27-5-2013 22:04, Scott Kostyshak schreef:
On Mon, May 27, 2013 at 3:40 PM, Vincent van Ravesteijn wrote:
On the other hand, I'm not sure whether marking bugs as 'easyfix' will
really help.
I'm fine with this. I just wanted to see if others thought it would
*hurt* anything.
Scott
No, it do
Due to the problems Scott had with LuaTeX and non-western scripts like Arabic, I investigated what
the 3 main engines LuaTeX, XeTeX and pdfTeX can do and updated their Wiki pages accordingly:
http://wiki.lyx.org/LyX/PdfTeX
http://wiki.lyx.org/LyX/XeTeX
http://wiki.lyx.org/LyX/LuaTeX
In the XeTe
On Mon, May 27, 2013 at 3:40 PM, Vincent van Ravesteijn wrote:
> On the other hand, I'm not sure whether marking bugs as 'easyfix' will
> really help.
I'm fine with this. I just wanted to see if others thought it would
*hurt* anything.
Scott
Op 27-5-2013 21:40, Vincent van Ravesteijn schreef:
Op 27-5-2013 21:13, Uwe Stöhr schreef:
Am 27.05.2013 20:10, schrieb Scott Kostyshak:
Scott, please don't mark bugs as easyfix if they are apparently
not that
easy to fix. If this bug would be easy to fix, somebody would
have done
this
Op 27-5-2013 21:13, Uwe Stöhr schreef:
Am 27.05.2013 20:10, schrieb Scott Kostyshak:
Scott, please don't mark bugs as easyfix if they are apparently
not that
easy to fix. If this bug would be easy to fix, somebody would have
done
this in the last 2 years, but nothing happened.
I do no
Am 27.05.2013 20:10, schrieb Scott Kostyshak:
Scott, please don't mark bugs as easyfix if they are apparently not that
easy to fix. If this bug would be easy to fix, somebody would have done
this in the last 2 years, but nothing happened.
I do not agree with the logic of "easy bug" -> "q
>From Uwe posted on #7723
> Comment:
>
> Scott, please don't mark bugs as easyfix if they are apparently not that
> easy to fix. If this bug would be easy to fix, somebody would have done
> this in the last 2 years, but nothing happened.
I do not agree with the logic of "easy bug" -> "quick fix
Am Montag, 27. Mai 2013 um 19:59:44, schrieb Vincent van Ravesteijn
> Op 27-5-2013 18:05, Jean-Marc Lasgouttes schreef:
> > 24/05/2013 15:07, Vincent van Ravesteijn:
> >> By the way, this doesn't always work. The kill-gettext branch, for
> >> instance, has master merged in a few times to fix merg
Op 27-5-2013 18:05, Jean-Marc Lasgouttes schreef:
24/05/2013 15:07, Vincent van Ravesteijn:
By the way, this doesn't always work. The kill-gettext branch, for
instance, has master merged in a few times to fix merge conflicts. Now,
rebasing onto the merge-base does do no good.
Vincent, I want t
Am Montag, 27. Mai 2013 um 18:20:52, schrieb Kornel Benko
> Am Montag, 27. Mai 2013 um 17:18:42, schrieb Hugo Hinterberger
>
> > On Mon, 27 May 2013 10:27:28 +0200
> > Kornel Benko wrote:
> >
> > > If you are not testing, you do not need it for lyx.
> >
> > Hi,
> >
> > I did not change anyt
Am Montag, 27. Mai 2013 um 17:18:42, schrieb Hugo Hinterberger
> On Mon, 27 May 2013 10:27:28 +0200
> Kornel Benko wrote:
>
> > If you are not testing, you do not need it for lyx.
>
> Hi,
>
> I did not change anything in my setup. I try to build the branch
> 'master' of LyX five times a week
24/05/2013 15:07, Vincent van Ravesteijn:
By the way, this doesn't always work. The kill-gettext branch, for
instance, has master merged in a few times to fix merge conflicts. Now,
rebasing onto the merge-base does do no good.
Vincent, I want to merge this kill-gettext branch now. Is there
som
On Mon, 27 May 2013 10:27:28 +0200
Kornel Benko wrote:
> If you are not testing, you do not need it for lyx.
Hi,
I did not change anything in my setup. I try to build the branch
'master' of LyX five times a week with no changes to the source.
I do a fetch and rebase and then I run a clean and
On 05/26/2013 09:35 AM, Liviu Andronic wrote:
Hello,
On Thu, May 23, 2013 at 10:11 PM, Richard Heck wrote:
I have posted a lyx2lyx conversion routine to the bug report
http://www.lyx.org/trac/ticket/8588#comment:23
Please test and let me know if there are problems. If so, please post the
On 05/26/2013 07:30 AM, Liviu Andronic wrote:
On Sun, May 26, 2013 at 12:38 PM, Vincent van Ravesteijn wrote:
I had the same error in the first try. After correcting the eol-style of the
patch file, everything was ok again. To correct the eol-style I used
'dos2unix' in a Git bash shell.
I did
Scott Kostyshak wrote:
> On Sun, May 26, 2013 at 7:28 AM, Jürgen Spitzmüller wrote:
> > Jürgen Spitzmüller wrote:
> > Scott, can you check out the attached patch? It does not fix existing
> > cases
> > (such as the issue in the French UG you mentioned), but it seems to behave
> > correctly when cr
Am Montag, 27. Mai 2013 um 10:18:07, schrieb Hugo Hinterberger
> Hi,
>
> I just want to inform you that the Windows build of branch 'master' has
> a problem:
>
> LINK : warning LNK4075: ignoring '/INCREMENTAL' due to '/FORCE'
> specification
> [D:\Workspace\LyX-Git\lyx-20-build\src\tests\check_
On Wed, May 8, 2013 at 2:59 AM, Elmar Hinz wrote:
> To get started, I would need to do some more simple cases first.
Hi Elmar,
Did you make any progress on this? I know little about unit tests so I
won't be able to help much here, but I'm interested in any progress
you feel like sharing.
Scott
Hi,
I just want to inform you that the Windows build of branch 'master' has
a problem:
LINK : warning LNK4075: ignoring '/INCREMENTAL' due to '/FORCE'
specification
[D:\Workspace\LyX-Git\lyx-20-build\src\tests\check_layout.vcxproj]
support.lib(gettext.obj) : warning LNK4006: "class
std::basic_str
On Fri, May 3, 2013 at 2:17 PM, Elmar Hinz wrote:
>> > Now I would like to fix some bugs.
>>
>> I have some buglettes in random notes that I wanted to eventually look
>> at. I told someone else that I would organize them and post them. I
>> will try to do that soon. I will put the 'easyfix' keywor
32 matches
Mail list logo
