> "Alexander" == Alexander Streit <[EMAIL PROTECTED]> writes:
Alexander> I couldn't find a bugzilla report on this, just waiting for
Alexander> my account to be created so that I can submit one. I am
Alexander> using beta 2 and it happens quite regularly.
Could it be that the cursor is left
> "Jürgen" == Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
Jürgen> The risk it that we implement it in a way that is not
Jürgen> thoroughly pondered (because of lacking time). Georg already
Jürgen> pointed out that he sees several things that have to be
Jürgen> thought about carefully with t
Uwe Stöhr wrote:
> > 1. open the file "armenian-article.lyx" from the examples
> > 2. change the document layout from "article (armenian)" to "article" and
> > save the file under a new name.
> > 3. change the document language from Armenian to Korean
> >
> > -> Crash:
>
> This problem is more gene
Timothy Reaves <[EMAIL PROTECTED]> writes:
Any idea's as to why I'm getting the following?
cat qt4_l10n.pot layouts_l10n.pot languages_l10n.pot ui_l10n.pot | \
msguniq -o LyX-1.5.po && rm -f qt4_l10n.pot layouts_l10n.pot
languages_l10n.pot
ui_l10n.pot
msguniq: found 4 fatal errors
make[3
Timothy Reaves <[EMAIL PROTECTED]> writes:
>
> Any idea's as to why I'm getting the following?
>
>
> Dusty >
>
>
Hi, I had the same problem and I found the following workaround:
echo "" > po/language_i18n.pot
emptying the above file seems to fix the compilation problem, I guess it will
ha
> 1. validation: wrong arguments will be passed to latex, If Abdel can
> implement a property editor GUI, validation can do done over there.
This is important.
It is a lot of work to validate ~ 130 parameters!! I guess I can do
that before 1.5.0 because validation is arguably the most importa
Any idea's as to why I'm getting the following?
cat qt4_l10n.pot layouts_l10n.pot languages_l10n.pot ui_l10n.pot | \
msguniq -o LyX-1.5.po && rm -f qt4_l10n.pot layouts_l10n.pot languages_l10n.pot
ui_l10n.pot
msguniq: : warning: Charset missing in header.
Message co
On Sun, May 06, 2007 at 10:46:57PM +0300, Dov Feldstern wrote:
> Andre Poenitz wrote:
> >On Sun, May 06, 2007 at 03:19:05AM +0300, Dov Feldstern wrote:
> >>Attached is a fix for (1) and (2) (but not (3)) of bug 3551
> >>(http://bugzilla.lyx.org/show_bug.cgi?id=3551). I'd be happy to hear any
> >>
On Sunday 06 May 2007 20:02:03 Bo Peng wrote:
> Two problems remains:
>
> 1. validation: wrong arguments will be passed to latex, If Abdel can
> implement a property editor GUI, validation can do done over there.
This is important.
> 2. option value with ". I quote params_ with "" in .lyx file,
On Sunday 06 May 2007 20:14:50 Bo Peng wrote:
> Anyway, I agree with Georg to put lstinputlisting there, although
> JMarc seems to prefer 'external material'.
A long term goal, that dates back to inset external creation, is the merging
of external inset with graphics and with include insets.
So
On Sunday 06 May 2007 22:56:45 [EMAIL PROTECTED] wrote:
> Is Bo's listing stuff going in? (I'm ambivalent, but just want a
> decision)
I did not mention this before because I am still trying to put in
perspective all the different issues involved.
Bo has worked really hard on the details, an
Bo Peng wrote:
Dear list,
I am trying to add a lstlisting environment to my layout file (using
listings package) and arrive at the following:
Style Listings
MarginStatic
LatexTypeEnvironment
LatexNamelstlisting
NextNoIndent1
LeftMarginMMM
RightM
> 11 May - beta 3
>
> Starting from this date and until the stable release all svn commits should
> have an associated bugzilla number.
Fine by me.
> --- Crash bugs ---
> Good news, we only have 5 confirmed crashes left:
Now whe have a new one :-(:
LyX crashes when changing the document langu
On Sun, 6 May 2007, José Matos wrote:
Hi all,
feedback is welcome for this message.
The reason for this tight scheduled is that if we are not able to fix
the really serious bugs in a month we will not solve the issues and this
only stagnates the development.
Proposed schedule to 1.
Uwe Stöhr schrieb:
1. open the file "armenian-article.lyx" from the examples
2. change the document layout from "article (armenian)" to "article" and
save the file under a new name.
3. change the document language from Armenian to Korean
-> Crash:
This problem is more general and only appea
I wrote:
I need the help of people using CJK-LyX or taking care it to test the
following patch: ...
The known issue has been solved and I committed the patch. But of course the
call for testers remain.
regards Uwe
After the commit, the unicodesymbols file is no longer correctly read. I've
seen it too late.
The unicodesymbols file itself is read, but not the second token with the command. So when you now
create a new document and insert a
€, or µ, or ×
character, you don't get
\texteuro, \textmu, or \tex
Hi Elazar!
If I understand correctly, this patch is intended to provide "visual
mode" cursor movement?
So a few comments:
1) I find it a little confusing to have two different patches going
around (the one I suggested yesterday, and this one), which are intended
to solve the same issue (Bid
Can you list some examples (and what is to be output for those instead of
babel)?
OK, the babel stuff works now for me - had some wrong entries in my tree.
As you all wanted that I commit it, I tested the patch again and put it in:
http://www.lyx.org/trac/changeset/18216
While testing I foun
Hi all,
feedback is welcome for this message.
The reason for this tight scheduled is that if we are not able to fix the
really serious bugs in a month we will not solve the issues and this only
stagnates the development.
The fact that lots of bugs have proposed patches is also an hint t
Abdelrazak Younes wrote:
Dov Feldstern wrote:
Attached is a fix for (1) and (2) (but not (3)) of bug 3551
(http://bugzilla.lyx.org/show_bug.cgi?id=3551). I'd be happy to hear
any comments, I'm not sure that I understand everything that I did,
but it does work.
At least the changes look sensi
Andre Poenitz wrote:
On Sun, May 06, 2007 at 03:19:05AM +0300, Dov Feldstern wrote:
Attached is a fix for (1) and (2) (but not (3)) of bug 3551
(http://bugzilla.lyx.org/show_bug.cgi?id=3551). I'd be happy to hear any
comments, I'm not sure that I understand everything that I did, but it
does w
Whether or not InsetListings should be
collapsible is open to discussion.
My reasons for using InsetCollapsable are that program listings
1. can be long (maybe over several pages) so CLOSE mode can be usable.
2. can be short or inlined (lstinline) so INLINE mode can be usable.
3. can float.
On Sunday 06 May 2007 20:11:28 Dov Feldstern wrote:
> By default, the rtl option will be set to true. We can, however, keep it
> as a flag, which can be used to turn it off on really slow machines if
> the user knows that rtl won't be needed. So that option would probably
> belong in an optimizatio
On Fri, 4 May 2007, Andreas K. wrote:
Now in, have a look:
http://www.lyx.org/about/press.php
/C
--
Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
Dov Feldstern wrote:
José Matos wrote:
On Sunday 06 May 2007 09:58:28 Abdelrazak Younes wrote:
Objections?
Dov gave some reasons the last time this option was raised, not that
I remember them BTW. :-)
Abdel.
No, actually I'm okay with this. I think that at one point we had
suggeste
i only took a look at the result (not the code), and it made me wonder
what exactly is gained by this?
A non-ERT way to use listings package.
implementation wise i find it strange to have code in a collapseable
inset (i also tried ERT, as in attached, and found that this is pretty
similar ui w
José Matos wrote:
On Sunday 06 May 2007 09:58:28 Abdelrazak Younes wrote:
Objections?
Dov gave some reasons the last time this option was raised, not that I
remember them BTW. :-)
Abdel.
No, actually I'm okay with this. I think that at one point we had
suggested the following:
By
On Wed, 2 May 2007, [EMAIL PROTECTED] wrote:
It's more than the changes to ANNOUNCE, so I've attached the diff. If no
one has any comments, I'll apply it soon.
Now committed.
/C
--
Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
Elazar Leibovich wrote:
There's a small bug I'd like to fix about the Bidirectional cursor drawing.
When is an RTL paragraph the cursor is right before a mathed inset, that is
HEBREW TEXT |math
it is drawn after the inset, ie
HEBREW TEXT math|
Where is the code that is responsible of drawing the
Attached please find a much improved InsetListings patch. The
implementation can now be reviewed...
I will explain more about the params issue.
Herbert's patch has a big dialog which handles around 10 commonly used
parameters. I tried but I was not able to port it to qt4, due to my
limited know
On technical grounds I think that another option is to have:
language=Python
float
I will explain what I have done in another thread.
Bo
On Saturday 05 May 2007 08:37:28 Jürgen Spitzmüller wrote:
> I still think it's too early. With the semanticc markup above, however, we
> could put some information (or even a style file) on the wiki, which lets
> the user experiment with changes.sty instead of soul.
I mostly agree with Jürgen.
There's a small bug I'd like to fix about the Bidirectional cursor drawing.
When is an RTL paragraph the cursor is right before a mathed inset, that is
HEBREW TEXT |math
it is drawn after the inset, ie
HEBREW TEXT math|
Where is the code that is responsible of drawing the cursor?
On Sunday 06 May 2007 10:24:10 Jürgen Spitzmüller wrote:
> FWIW, I agree. But I guess this is José's call.
Since this improves LyX I think that it should go in. Any remaining issues
will/should be fixed afterwards.
Proceed.
> Jürgen
--
José Abílio
On Sunday 06 May 2007 09:58:28 Abdelrazak Younes wrote:
> Objections?
Dov gave some reasons the last time this option was raised, not that I
remember them BTW. :-)
> Abdel.
--
José Abílio
I think this is a very clever approach. Nowadays 99% of modern
program supports Unicode and thus RTL out of the box.
On 5/6/07, Abdelrazak Younes <[EMAIL PROTECTED]> wrote:
Dov Feldstern wrote:
> While looking into the issue of cursor direction in RTL paragraphs,
> using the latest svn version,
Please try this patch for second approach. Please make sure I'm not
breaking anything.
See discussion here http://bugzilla.lyx.org/show_bug.cgi?id=3551
Index: Text2.cpp
===
--- Text2.cpp (revision 18129)
+++ Text2.cpp (working copy)
@
On Saturday 05 May 2007 16:43:47 Bo Peng wrote:
> The only solution I can think of is the HTML way, where special
> characters are encoded in &1023; etc for storage and transportation.
> Does anyone know how to implement this?
On technical grounds I think that another option is to have:
language=
On Saturday 05 May 2007 14:53:34 Jürgen Spitzmüller wrote:
> Michael Gerz wrote:
> > Is this needed? Two lines above, the tool tip is already set.
>
> Yes. This is the text that gets displayed beside the icon when the window
> is too small for the toolbar and you press the » arrow to get the missin
On Saturday 05 May 2007 11:05:02 Abdelrazak Younes wrote:
> OK for me.
>
> Abdel.
If no one opposes by tomorrow you can put it in.
--
José Abílio
On Saturday 05 May 2007 15:14:33 Jürgen Spitzmüller wrote:
> OK to go in?
It seems so, what has Jean-Marc to say about this? If this code is OK with
Jean-Marc it can go in. I am trying to be cautious here, even with this code
tested by both you and Uwe, since this code always brings me unexpec
On Friday 04 May 2007 16:15:12 Abdelrazak Younes wrote:
> The preamble is part of the LyX file right? So it is susceptible to
> contain non latin unicode characters.
Do we a bug number and a user report for that one? ;-)
What would it be different between latin and non latin unicode?
I tri
Hello,
the attached patch tries to decouple change tracking output from dvipost.
The overall approach is to define two commands \lyxinserted and
\lyxdeleted that are mapped on either dvipost, soul (in the future), or
"nothing".
Unfortunately, the patch produces some artifacts with dvipost. S
On Sunday 06 May 2007 16:35:56 Dov Feldstern wrote:
> Hi Abdel, and all the other who have replied to this thread!
>
> I certainly didn't intend to cause you guys to lose motivation :( ---
> yes, you're definitely doing a great job, 1.5 is *much* *much* cleaner
> and stabler than 1.4, a lot of the
Bo Peng wrote:
Attached please find a much improved InsetListings patch. The
implementation can now be reviewed...
i only took a look at the result (not the code), and it made me wonder
what exactly is gained by this?
some impressions:
implementation wise i find it strange to have code in a
On Sunday 06 May 2007 09:36:45 Michael Gerz wrote:
> OK, boys, it's bug fixing time!
+1000
> Michael
--
José Abílio
On Sunday 06 May 2007 09:38:48 Peter Kümmel wrote:
> Abdel don't get this complaining about the development process too serious.
> We will see if 1.5 is so bad how all those pessimists claim.
We have been having this discussion everytime that we are near a stable
release, at least as far as I r
Uwe Stöhr wrote:
> There's one issue why I don't think this can be committed right now:
>
> babel is called every time because it is hardcoded in lyxrc.cpp. But babel
> shouldn't or even mustn't be called for some languages.
Can you list some examples (and what is to be output for those instead of
Am Sonntag, 6. Mai 2007 12:03 schrieb Michael Gerz:
> Oh, that means that there are some byte combinations that don't make a
> UTF-8 character. Interesting.
There is a table of illegal sequences at
http://en.wikipedia.org/wiki/UTF-8.
> However, with 8-bit local encoding, every file should be a
Abdelrazak Younes wrote:
Dov, I don't deny you the right to express your opinion (it is of course
welcome) but I'd like to clarify one thing: the tree is _not_
destabilizing! 1.5 is much cleaner and stabler than 1.4, period.
Sorry but I am a bit fad up with this continuous flagellation about
Am Samstag, 5. Mai 2007 23:27 schrieb Dov Feldstern:
> Georg Baum wrote:
> > Am Dienstag, 10. April 2007 14:04 schrieb Jean-Marc Lasgouttes:
> >
> > I fixed this problem by not outputting the \inputencoding command in
> > sections. The attached file works fine now, but if you uncomment the
TOC
Uwe Stöhr wrote:
> I btw. reverted a change you made in r18198 because it broke the
> inputencoding setting: http://www.lyx.org/trac/changeset/18210
Yes, thanks, I missed the logic. I noticed I was wrong while studying the
pending patch of Georg and you.
Jürgen
>>Apart from that, the patch looks straightforward from a first glance, and
it cleans up things
>> significantly.
>>
>>It certainly needs some testing (especially wrt CJK and thailatex), but
it looks like the
>> right thing in general, from what I can judge.
>
> Then I suggest to commit
I need the help of people using CJK-LyX or taking care it to test the following
patch:
http://bugzilla.lyx.org/attachment.cgi?id=1602
This patch makes it possible to set the document language from within LyX's menu, the correct
encoding for the document is then set automatically.
Comments?
> Uwe, this unrelated fix slipped in by accident.
Yes, sorry. Thanks for taking care.
I btw. reverted a change you made in r18198 because it broke the inputencoding
setting:
http://www.lyx.org/trac/changeset/18210
regards Uwe
I propose a deal ;-) :
You promise to fix all remaining issues (if any) WRT your features and
then this feature can go in (AFAIAC of course). Straight out of my head,
here are some bugs related to your work:
If you promise to change my simple QEditBox to property editors (like
what qt designer
Peter Kümmel wrote:
> encoding. But therefore we need a new dialog and a new conversion function
> docstring const from_encoding(std::string const & s);
> Or how is the conversion from an arbitrary encoding done?
/// convert \p s from encoding \p encoding to ucs4.
/// \p encoding must be a valid
Peter Kümmel schrieb:
Are you sure? As I understand it local8bit is the concrete value of the system
which iconv uses, for instance ARMSCII-8 (
http://www.gnu.org/software/libiconv/ )
and then it is still possible that converting fails.
A file is made up of bytes that are interpreted accordi
Bo Peng wrote:
> Attached please find a much improved InsetListings patch. The
> implementation can now be reviewed...
>
> Changes:
>
> Better organized InsetListingsParams functions
> Autotools support
> InsetListings now derives from InsetERT
> Use LISTINS_CODE
> Code cleaning
> and more...
l
Abdelrazak Younes wrote:
Dov, I don't deny you the right to express your opinion (it is of course
welcome) but I'd like to clarify one thing: the tree is _not_
destabilizing! 1.5 is much cleaner and stabler than 1.4, period.
Sorry but I am a bit fad up with this continuous flagellation about o
Peter Kümmel wrote:
> So why should Jürgen's patch not be correct?
> When from_utf8 is used then we need a utf8 encoding.
Several things need to be considered:
- Is it correct to always use utf8 for preview? Basically, this breaks
preview-latex for older distributions that do not feature utf8. I
Michael Gerz wrote:
> Peter Kümmel schrieb:
>>> Is there any way to determine the encoding of a file? Can't any file be
>>> considered as UTF-8 (even if it is not encoded in UTF-8)?
>>>
>>
>> Georg's comment in bugzilla is
>>
>>
> Yes, LyX treats all text files as utf8, and iconv can cho
--- Additional Comment #4 From Juergen Spitzmueller 2007-05-05 12:02
---
The problem is that LyX passes the text to preview-latex as a utf8-encoded
file, but doesn't indicate that with an appropriate inputenc option.
Have a look at the FIXME in PreviewLoader.cpp: 573. A simple way to g
Peter Kümmel schrieb:
Is there any way to determine the encoding of a file? Can't any file be
considered as UTF-8 (even if it is not encoded in UTF-8)?
Georg's comment in bugzilla is
Yes, LyX treats all text files as utf8, and iconv can choke on
non-utf8 text
Oh, that
Michael Gerz wrote:
> Peter Kümmel schrieb:
>> http://bugzilla.lyx.org/show_bug.cgi?id=3203:
>>
>>
>>> Yes, LyX treats all text files as utf8, and iconv can choke on
>>> non-utf8 text
>>> interpreted as utf8. I see the same here.
>>> Since it is not possible to detect the file encoding reliably f
Peter Kümmel schrieb:
http://bugzilla.lyx.org/show_bug.cgi?id=3203:
Yes, LyX treats all text files as utf8, and iconv can choke on non-utf8 text
interpreted as utf8. I see the same here.
Since it is not possible to detect the file encoding reliably from the contents
the only option I see to
Abdelrazak Younes wrote:
> Then I suggest to commit it. AFAIU the file format is not going to
> change even if there's some errors in processing CJK. That's the only
> way to move forward.
FWIW, I agree. But I guess this is José's call.
Jürgen
Jürgen Spitzmüller wrote:
Jürgen Spitzmüller wrote:
I found my mistakes now and updated the patch agian. But anyway, I need
somebody who examines the patch and testers.
A minor thing:
Apart from that, the patch looks straightforward from a first glance, and it
cleans up things significantly.
http://bugzilla.lyx.org/show_bug.cgi?id=3203:
>Yes, LyX treats all text files as utf8, and iconv can choke on non-utf8 text
>interpreted as utf8. I see the same here.
>Since it is not possible to detect the file encoding reliably from the contents
>the only option I see to make this work is to let
Dov Feldstern wrote:
While looking into the issue of cursor direction in RTL paragraphs,
using the latest svn version, I ran into a lot of stability issues and
crashes. I'm attaching a file I created, which causes LyX to crash when
I try to view the dvi. I haven't investigated this.
By the wa
Dov Feldstern wrote:
While looking into the issue of cursor direction in RTL paragraphs,
using the latest svn version, I ran into a lot of stability issues and
crashes. I'm attaching a file I created, which causes LyX to crash when
I try to view the dvi. I haven't investigated this.
It may be
Abdelrazak Younes wrote:
> Dov Feldstern wrote:
>> some directions that LyX is taking --- I feel that we're gaining
>> features (which is of course good) at the expense of stability (which
>> is less good...). And I fear that your leaving the list will only
>> accelerate that trend...).
>
> Dov, I
Jürgen Spitzmüller wrote:
> Please revert
I did.
Jürgen
Abdelrazak Younes schrieb:
Dov Feldstern wrote:
some directions that LyX is taking --- I feel that we're gaining
features (which is of course good) at the expense of stability (which
is less good...). And I fear that your leaving the list will only
accelerate that trend...).
Dov, I don't den
[EMAIL PROTECTED] wrote:
> Modified: lyx-devel/trunk/src/Cursor.cpp
> URL: http://www.lyx.org/trac/file/lyx-devel/trunk/src/Cursor.cpp?rev=18206
> ===
>=== --- lyx-devel/trunk/src/Cursor.cpp (original)
> +++ lyx-devel/trunk/src
Jürgen Spitzmüller wrote:
> > I found my mistakes now and updated the patch agian. But anyway, I need
> > somebody who examines the patch and testers.
>
> A minor thing:
Apart from that, the patch looks straightforward from a first glance, and it
cleans up things significantly.
It certainly need
On Sun, May 06, 2007 at 03:19:05AM +0300, Dov Feldstern wrote:
> Attached is a fix for (1) and (2) (but not (3)) of bug 3551
> (http://bugzilla.lyx.org/show_bug.cgi?id=3551). I'd be happy to hear any
> comments, I'm not sure that I understand everything that I did, but it
> does work.
Have you
Dov Feldstern wrote:
some directions that LyX is taking --- I feel that we're gaining
features (which is of course good) at the expense of stability (which is
less good...). And I fear that your leaving the list will only
accelerate that trend...).
Dov, I don't deny you the right to express y
Uwe Stöhr wrote:
> I found my mistakes now and updated the patch agian. But anyway, I need
> somebody who examines the patch and testers.
A minor thing:
# A plain utf8 encoding that does not use the inputenc package.
# Such an encoding is required for XeTeX.
-Encoding utf8-plain utf8-plain UTF-
Dov Feldstern wrote:
Attached is a fix for (1) and (2) (but not (3)) of bug 3551
(http://bugzilla.lyx.org/show_bug.cgi?id=3551). I'd be happy to hear any
comments, I'm not sure that I understand everything that I did, but it
does work.
At least the changes look sensible. JMarc will tell for s
Li Wang wrote:
> Hi,
>
> Which directory should I put the file "fancyhdr.sty" ?
About the same where you put setspace.sty.
> How can I post further questions on usage to the lyx-users list ? the link
> address?
http://www.lyx.org/internet/mailing.php
> Thanks,
>
> Li Wang
Jürgen
Uwe Stöhr wrote:
> Works here as expected, so yes, put it in.
Since it's trivial, I've done that.
Jürgen
83 matches
Mail list logo
