2014-04-09 8:40 GMT+02:00 Stephan Witt :
> Can you provide an example, please? If the word cannot be converted to
> Hunspell dictionary encoding
> the dictionary is broken or the language is not correct, isn't it?
>
Depends on how you define "language". Think of names.
> You're right, the user
Am 09.04.2014 um 08:14 schrieb Jürgen Spitzmüller :
> 2014-04-08 22:42 GMT+02:00 Georg Baum:
> The change in src/support/unicode.cpp is problematic: It disables all error
> handling, not only the lyxerr output. Also, if you now throw an exception
> there, you need to make sure that all callers ca
Am 08.04.2014 um 22:30 schrieb Georg Baum :
> Jürgen Spitzmüller wrote:
>
>> 2014-04-07 11:37 GMT+02:00 Vincent van Ravesteijn:
>>
>>> To slightly detail the response. The work-around is already in rc1 and
>>> that's probably the small w that is observed. There will be no change
>>> between 2.1.
2014-04-08 22:42 GMT+02:00 Georg Baum:
> The change in src/support/unicode.cpp is problematic: It disables all error
> handling, not only the lyxerr output. Also, if you now throw an exception
> there, you need to make sure that all callers can cope with that. Maybe one
> solution would be to thro
Vincent van Ravesteijn wrote:
> Dear translators,
Vincent, most of the string in nl section seem to be translated,
except of Listings - can you check?
layouttranslations.review:
nl: "Acknowledgement", "Case", "Chart", (same translation as "Graph") "Claim",
"Condition", "Conjecture", "Corollar
Am 04.04.2014 13:47, schrieb Jürgen Spitzmüller:
I do not see the need to raise a fundamental discussion about LyX 2.1 release
at this point.
Well, we only release a major version ever 2 - 3 years. So we should take the time to bring it to a
shape that we can advertise it. For example if the
Am 04.04.2014 12:01, schrieb Jürgen Spitzmüller:
If you want to see something bad, you will always find something. It hurts
me a lot that you see it like that. Why are you now that formalistic?
Call it formalistic, if you wish. But please note that I am not the only
one asking you for this. Ge
Am 04.04.2014 08:25, schrieb Vincent van Ravesteijn:
Sorry, but there is nothing about Urdu that we support (except an
entry in the languages file),
And with this we support hyphenations, automatic translations of words like "figure" etc. So as
Jamil stated, the output is correct.
What is not
Am 07.04.2014 14:13, schrieb Øyvind Sørbye:
Sorry for not reporting back, I tested LyX-207-Installer-2.exe, it worked
perfect, now I can install and uninstall unattended with the /S-switch, and all
the other icons is still there in the Start Menu. But a forgot to report back
:-(
I tested t
Am 08.04.2014 11:48, schrieb Vincent van Ravesteijn:
Why are you doing those things in private? Translators never respond
to me, you have secret agreements with translators where they can grab
the to-be-translated documents from, I don't see the majority of
translations coming in, then I have to
Jürgen Spitzmüller wrote:
> 2014-04-04 0:19 GMT+02:00 Uwe Stöhr :
>
>> The time you were the manager for 1.5/6.x I also many times upload test
>> installers and you were aware of that. That time the main problem was
>> that I did not had Vista and could not see if a problem that was only
>> repor
Uwe Stöhr wrote:
> Am 03.04.2014 22:12, schrieb Georg Baum:
>
>> I understand your motivation to help people in developing countries (and
>> I appreciate it), but please do not assume that your proposed solution of
>> a particular problem is the only one which is feasible. Claiming that LyX
>> su
Richard Heck wrote:
> I looked through most of this, except for the math bits, which I don't
> feel like I know enough about. There were only a few uninitialized
> variables that seemed to me an issue. But there were a couple problems
> that the script caught that seem real, and I've committed tho
Jürgen Spitzmüller wrote:
> I am not very familiar with iconv/unicode and exception handling, so I
> would appreciate a critical review.
The change in src/support/unicode.cpp is problematic: It disables all error
handling, not only the lyxerr output. Also, if you now throw an exception
there, y
Jürgen Spitzmüller wrote:
> 2014-04-07 11:37 GMT+02:00 Vincent van Ravesteijn:
>
>> To slightly detail the response. The work-around is already in rc1 and
>> that's probably the small w that is observed. There will be no change
>> between 2.1.0 final and rc1.
No, the small w is not the workaroun
Jürgen Spitzmüller wrote:
> 2014-04-08 11:19 GMT+02:00 Vincent van Ravesteijn:
>
> You can still decide to disable this feature (probably as easy as removing
> BIBTEX_ERROR from the ERROR declaration in LaTeX.h:142). Fiddling with the
> feature itself makes no sense at this stage, IMHO.
>
>
>>
Hello,
A thread on lyx-fr was raised on the suject: multi-byte characters are not
supported in this situation.
Among several workarounds, one is to convert the file to latin9 with iconv: I
wonder if it could be possible for LyX to perform the iconv conversion on line.
There is no problem with I
I wonder if a better approach would be to write a converter-agnostic script?
So for example, the script searches for the usual converters - soffice,
textutil, writer2latex, rtf2latex and then cobbles together a chain of formats
to get to lyx?
A script that was more flexible would work on more
Am Dienstag, 8. April 2014 um 11:38:42, schrieb Vincent van Ravesteijn
> > Will commit then. This change effects naming of packages created with target
> > 'package' or 'package_source' of cmake.
> >
> > Probably I am the only one using it?
> >
> > I don't expect any trouble, but even then, it is
2014-04-08 11:19 GMT+02:00 Vincent van Ravesteijn:
> - Documents not compiling anymore because of BibTeX errors. We already
> received a lot of reports and this can prohibit people from updating.
>
You can still decide to disable this feature (probably as easy as removing
BIBTEX_ERROR from the ER
> I did both now.
>
> JMarc
>
Thanks,
Vincent
08/04/2014 11:37, Vincent van Ravesteijn:
I mean, Yes, please add me to the alias, and Yes, please forward the
unprocessed messages.
I did both now.
JMarc
On Tue, Apr 8, 2014 at 11:31 AM, Kornel Benko wrote:
> Am Sonntag, 6. April 2014 um 13:13:08, schrieb Richard Heck
>
>> > > That sort of patch is fine with me, once all of you figure out what
>
>> >
>
>> > > exactly the best
>
>> >
>
>> > > way to do it is.
>
>> >
>
>> > I think the attached patc
On Tue, Apr 8, 2014 at 11:34 AM, Vincent van Ravesteijn wrote:
> On Tue, Apr 8, 2014 at 11:30 AM, Jean-Marc Lasgouttes
> wrote:
>> 08/04/2014 11:19, Vincent van Ravesteijn:
>>
>>> At the moment I've a few issues left that I think need some consideration.
>>>
>>> - As it seems that nearly all comm
On Tue, Apr 8, 2014 at 11:30 AM, Jean-Marc Lasgouttes
wrote:
> 08/04/2014 11:19, Vincent van Ravesteijn:
>
>> At the moment I've a few issues left that I think need some consideration.
>>
>> - As it seems that nearly all communications with the translators are
>> going solely by private mail by Uw
Am Sonntag, 6. April 2014 um 13:13:08, schrieb Richard Heck
> > > That sort of patch is fine with me, once all of you figure out what
> >
> > > exactly the best
> >
> > > way to do it is.
> >
> > I think the attached patch is ready for 2.1.1-staging + 2.2-staging
> >
>
> I don't know enough about
08/04/2014 11:19, Vincent van Ravesteijn:
At the moment I've a few issues left that I think need some consideration.
- As it seems that nearly all communications with the translators are
going solely by private mail by Uwe, and as Uwe apparently left
without further notice after sending his last
At the moment I've a few issues left that I think need some consideration.
- As it seems that nearly all communications with the translators are
going solely by private mail by Uwe, and as Uwe apparently left
without further notice after sending his last e-mails, I've no clue on
what translations
28 matches
Mail list logo
