Georg == Georg Baum [EMAIL PROTECTED] writes:
Georg That looks sensible. Note that something like that is already
Georg planned with the current file format: The encoding parameter
Georg that formerly specified both .lyx and .tex encoding has not
Georg been removed, but declared to specify .tex
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> That looks sensible. Note that something like that is already
Georg> planned with the current file format: The encoding parameter
Georg> that formerly specified both .lyx and .tex encoding has not
Georg> been removed, but declared to
Am Montag, 16. Oktober 2006 11:00 schrieb Jean-Marc Lasgouttes:
What _I_ would like to see is a choice for the user of the output
encoding. LyX would use iconv to get this output. When one cannot find
a given unicode character in the output format, we would use a table
to convert. A starting
Am Montag, 16. Oktober 2006 11:00 schrieb Jean-Marc Lasgouttes:
> What _I_ would like to see is a choice for the user of the output
> encoding. LyX would use iconv to get this output. When one cannot find
> a given unicode character in the output format, we would use a table
> to convert. A
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars I think the most crucial part as of now is output, especially
Lars output to latex and how to handle that. Will it mean
Lars Omega/Lambda, some utf8 packages for LaTeX? How to solve this
Lars with (La)TeX is pretty open.
What _I_ would
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> I think the most crucial part as of now is output, especially
Lars> output to latex and how to handle that. Will it mean
Lars> Omega/Lambda, some utf8 packages for LaTeX? How to solve this
Lars> with (La)TeX is pretty open.
Abdelrazak Younes [EMAIL PROTECTED] writes:
| Lars Gullik Bjønnes wrote:
| Michael Gerz [EMAIL PROTECTED] writes:
| | Lars Gullik Bjønnes wrote:
| | | I think you can continue as you have outlined. Please try to
| not make
| | anything (except CT) more unusable than it already is. If not it
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Michael Gerz <[EMAIL PROTECTED]> writes:
| > | Lars Gullik Bjønnes wrote:
| > | | >I think you can continue as you have outlined. Please try to
| > not make
| > | >anything (except CT) more unusable than it already is.
Michael == Michael Gerz [EMAIL PROTECTED] writes:
Michael BTW: I think there is slow progress regarding unicode. Do you
Michael have any idea how to overcome the current situation? It seems
Michael some people are waiting for a sign :-)
I believe the sign will come from Denmark, soonish.
JMarc
Lars Gullik Bjønnes wrote:
Michael Gerz [EMAIL PROTECTED] writes:
| Lars Gullik Bjønnes wrote:
|
| I think you can continue as you have outlined. Please try to not make
| anything (except CT) more unusable than it already is. If not it might
| create difficulties for us, when we go into hard
On Mon, Oct 09, 2006 at 10:34:32AM +0200, Jean-Marc Lasgouttes wrote:
Michael == Michael Gerz [EMAIL PROTECTED] writes:
Michael BTW: I think there is slow progress regarding unicode. Do you
Michael have any idea how to overcome the current situation? It seems
Michael some people are waiting
> "Michael" == Michael Gerz <[EMAIL PROTECTED]> writes:
Michael> BTW: I think there is slow progress regarding unicode. Do you
Michael> have any idea how to overcome the current situation? It seems
Michael> some people are waiting for a sign :-)
I believe the sign will come from Denmark,
Lars Gullik Bjønnes wrote:
Michael Gerz <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
|
| >I think you can continue as you have outlined. Please try to not make
| >anything (except CT) more unusable than it already is. If not it might
| >create difficulties for us, when we go into
On Mon, Oct 09, 2006 at 10:34:32AM +0200, Jean-Marc Lasgouttes wrote:
> > "Michael" == Michael Gerz <[EMAIL PROTECTED]> writes:
>
> Michael> BTW: I think there is slow progress regarding unicode. Do you
> Michael> have any idea how to overcome the current situation? It seems
> Michael> some
Hello,
this is the first patch that I would like to commit to trunk.
It breaks CT temporarily but should not affect the rest of LyX.
Any comments?
Michael
Index: src/insets/insettabular.C
===
--- src/insets/insettabular.C
Michael Gerz [EMAIL PROTECTED] writes:
| Hello,
|
| this is the first patch that I would like to commit to trunk.
|
| It breaks CT temporarily but should not affect the rest of LyX.
|
| Any comments?
What is it doing?
Only name change? (close to)
--
Lgb
Lars Gullik Bjønnes wrote:
What is it doing?
Only name change? (close to)
Not exactly:
* rename output_changes to outputChanges
* rename tracking_changes to trackChanges
* add FIXMEs for later revision
* remove trackChanges(); the CT data structure will always be set up
* decouple LFUNs
Michael Gerz [EMAIL PROTECTED] writes:
| Lars Gullik Bjønnes wrote:
|
| What is it doing?
|
| Only name change? (close to)
|
| Not exactly:
|
| * rename output_changes to outputChanges
| * rename tracking_changes to trackChanges
| * add FIXMEs for later revision
| * remove trackChanges(); the
Lars Gullik Bjønnes wrote:
I think you can continue as you have outlined. Please try to not make
anything (except CT) more unusable than it already is. If not it might
create difficulties for us, when we go into hard working mode during
the Denmark thing.
Thank you for your trust.
BTW: I
Michael Gerz [EMAIL PROTECTED] writes:
| Lars Gullik Bjønnes wrote:
|
| I think you can continue as you have outlined. Please try to not make
| anything (except CT) more unusable than it already is. If not it might
| create difficulties for us, when we go into hard working mode during
| the
Hello,
this is the first patch that I would like to commit to trunk.
It breaks CT temporarily but should not affect the rest of LyX.
Any comments?
Michael
Index: src/insets/insettabular.C
===
--- src/insets/insettabular.C
Michael Gerz <[EMAIL PROTECTED]> writes:
| Hello,
|
| this is the first patch that I would like to commit to trunk.
|
| It breaks CT temporarily but should not affect the rest of LyX.
|
| Any comments?
What is it doing?
Only name change? (close to)
--
Lgb
Lars Gullik Bjønnes wrote:
What is it doing?
Only name change? (close to)
Not exactly:
* rename output_changes to outputChanges
* rename tracking_changes to trackChanges
* add FIXMEs for later revision
* remove trackChanges(); the CT data structure will always be set up
* decouple LFUNs
Michael Gerz <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
|
| >What is it doing?
| >
| >Only name change? (close to)
| >
| Not exactly:
|
| * rename output_changes to outputChanges
| * rename tracking_changes to trackChanges
| * add FIXMEs for later revision
| * remove
Lars Gullik Bjønnes wrote:
I think you can continue as you have outlined. Please try to not make
anything (except CT) more unusable than it already is. If not it might
create difficulties for us, when we go into "hard working mode" during
the Denmark thing.
Thank you for your trust.
BTW: I
Michael Gerz <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
|
| >I think you can continue as you have outlined. Please try to not make
| >anything (except CT) more unusable than it already is. If not it might
| >create difficulties for us, when we go into "hard working mode" during
|
26 matches
Mail list logo
