Le 10/04/2013 16:34, Guenter Milde a écrit :
Where do I have to apply.
(For my Sourceforge username, have a look at the mail address:)
Hi Günter,
I kind of forgot about you :)
Does the lyx.org address work?
Can you send a ssh public key to me ?
JMarc
Le 10/04/13 21:43, Pavel Sanda a écrit :
Guenter Milde wrote:
Where do I have to apply.
Pretty much by screaming here.
I will try to do that asap (but I am a bit busy). What is your preferred
username? mi...@lyx.org?
JMarc
Pavel Sanda wrote:
> Guenter Milde wrote:
>> Where do I have to apply.
>
> Pretty much by screaming here.
>
> The usual prerequisity is that you stay around for some time
> while providing patches, willingness to fix problems
> caused by your commits and at least in the beginning
> asking for ac
Guenter Milde wrote:
> Where do I have to apply.
Pretty much by screaming here.
The usual prerequisity is that you stay around for some time
while providing patches, willingness to fix problems
caused by your commits and at least in the beginning
asking for ack before any commit is done.
In you
On 2013-04-10, Kornel Benko wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> Am Dienstag, 9. April 2013 um 22:12:08, schrieb Uwe Stöhr
>> Am 03.04.2013 15:33, schrieb Guenter Milde:
>> >>> With the current state of textcyr, the fix should be far more easy ---
>> >>> change the de
Am Dienstag, 9. April 2013 um 22:12:08, schrieb Uwe Stöhr
> Am 03.04.2013 15:33, schrieb Guenter Milde:
>
> >>> With the current state of textcyr, the fix should be far more easy ---
> >>> change the default latex input encoding to ASCII.
> >
> >> I don't have much time at the moment, could you p
Am 03.04.2013 15:33, schrieb Guenter Milde:
With the current state of textcyr, the fix should be far more easy ---
change the default latex input encoding to ASCII.
I don't have much time at the moment, could you please take over?
I can provide a patch, but I am not a developer, so I cannot
On 2013-04-02, Uwe Stöhr wrote:
> Am 22.03.2013 09:42, schrieb Guenter Milde:
>> So, maybe for the time being it could be better to just exclude
>> Kazakh from the "Cyrillic languages" to let the "textcyr" feature
>> work.
>> With the current state of textcyr, the fix should be far mo
Am 22.03.2013 09:42, schrieb Guenter Milde:
So, maybe for the time being it could be better to just exclude
Kazakh from the "Cyrillic languages" to let the "textcyr" feature
work.
With the current state of textcyr, the fix should be far more easy --- change
the default latex input encoding to
On 2013-03-22, Uwe Stöhr wrote:
> Am 20.03.2013 21:58, schrieb Guenter Milde:
>> Thinking about it, I realize that also the basic support for other languages
>> is optional -- my Debian system has lots of "texlive-language-*" packages.
>> I don't think we should completely disable using a language
Am 20.03.2013 21:58, schrieb Guenter Milde:
Thinking about it, I realize that also the basic support for other languages
is optional -- my Debian system has lots of "texlive-language-*" packages.
I don't think we should completely disable using a language that is not
properly supported, but a wa
On 2013-03-19, Uwe Stöhr wrote:
> Am 19.03.2013 12:27, schrieb Guenter Milde:
> I found now a babel support for Serbian Cyrillic:
> http://www.ctan.org/tex-archive/macros/latex/contrib/babel-contrib/serbianc
> it works fine, the same as the other non-native babel support files
> like e.g. for Lit
On Tue, Mar 19, 2013 at 7:53 PM, Uwe Stöhr wrote:
> Am 19.03.2013 17:24, schrieb Scott Kostyshak:
>
>
>> It would be nice to have export tests for many different languages,
>
>
> I don't think so. As non-native speaker you cannot decide if e.g. all
> shorthands are correct and there are countless
Am 19.03.2013 17:24, schrieb Scott Kostyshak:
It would be nice to have export tests for many different languages,
I don't think so. As non-native speaker you cannot decide if e.g. all shorthands are correct and
there are countless combinations. We know that some language combinations won't wo
Am 19.03.2013 12:27, schrieb Guenter Milde:
For Kazakh there is no babel file
available at all, but a colleague of mine is from Kazakhstan and I
will ask him to create one.
Good idea. Maybe we can also find someone for Serbian (Cyrillic).
Hi Günter,
I found now a babel support for Serbian C
On Tue, Mar 19, 2013 at 7:27 AM, Guenter Milde wrote:
> Dear Uwe,
>
> On 2013-03-18, Uwe Stöhr wrote:
>> Am 16.03.2013 16:24, schrieb Guenter Milde:
>
>>> Besides try-and error with different Cyrillic-using languages, you can
>>> also look into Babel's *.ldf files for the respective languages. For
Dear Uwe,
On 2013-03-18, Uwe Stöhr wrote:
> Am 16.03.2013 16:24, schrieb Guenter Milde:
>> Besides try-and error with different Cyrillic-using languages, you can
>> also look into Babel's *.ldf files for the respective languages. For
>> example russian.ldf comes with code to set the font encoding
Am 16.03.2013 16:24, schrieb Guenter Milde:
Besides try-and error with different Cyrillic-using languages, you can
also look into Babel's *.ldf files for the respective languages. For
example russian.ldf comes with code to set the font encoding to one of
the Cyrillic encodings (OT2, T2A, T2B, T2
Am 15.03.2013 23:37, schrieb Enrico Forestieri:
I simply changed the document language of
http://www.lyx.org/trac/raw-attachment/ticket/8590/cyrillic.lyx
I still can only reproduce this for Serbian and Kazakh. The reason is that babel has no support for
Cyrillic Serbian and that there is no s
On 2013-03-15, Enrico Forestieri wrote:
> On Thu, Mar 14, 2013 at 11:37:58PM +0100, Uwe Stöhr wrote:
>> Am 13.03.2013 15:20, schrieb Enrico Forestieri:
...
>> Thanks for the pointer, this is indeed a general issue. On my MiKTeX
>> system I only get problems with Serbian and Kazakh, Belorussian an
On Thu, Mar 14, 2013 at 11:37:58PM +0100, Uwe Stöhr wrote:
> Am 13.03.2013 15:20, schrieb Enrico Forestieri:
>
> >>I tested the patch with many language combinations and it works so
> >>far. But I would like to hear from anybody who is familiar with
> >>Cyrillic or Greek and/or the font encoding
Am 14.03.2013 11:50, schrieb Guenter Milde:
Babel's Serbian support misses the auto set-up of a cyrillic font
encoding present in Babel's support for Russian and other languages using
the Cyrillic script. Instead, it relies on the user to hand-insert the
T2A option.
Thanks for this info, I was
Am 13.03.2013 15:20, schrieb Enrico Forestieri:
I tested the patch with many language combinations and it works so
far. But I would like to hear from anybody who is familiar with
Cyrillic or Greek and/or the font encoding business. Jürgen Milde,
Enrico?
I don't think the patch is correct. For
On 2013-03-13, Uwe Stöhr wrote:
> Currently Cyrillic Serbian documents are uncompilable which is a
> regression to LyX 2.0.5. This bug was uncovered by commit 25e4bf4b2 by
> Enrico which correctly loads the T2A font encoding. The problem is
> that Cyrillic Serbian (and only that language) requir
On Wed, Mar 13, 2013 at 01:59:43AM +0100, Uwe Stöhr wrote:
> Attached is a patch that fixes bug 8590
> http://www.lyx.org/trac/ticket/8590
>
> Currently Cyrillic Serbian documents are uncompilable which is a regression
> to LyX 2.0.5.
Not at all, given that lyx 2.0.5 is not able to compile those
25 matches
Mail list logo
