On Sat, Dec 10, 2022 at 01:02:15PM +0100, Jürgen Spitzmüller wrote:
> Am Freitag, dem 09.12.2022 um 12:08 -0500 schrieb Scott Kostyshak:
> > Changing \inputencoding from utf8 to auto-legacy leads to no iconv
> > error. Is that a reasonable thing to do? I don't understand encodings
> > well.
>
> Th
Am Freitag, dem 09.12.2022 um 12:08 -0500 schrieb Scott Kostyshak:
> Changing \inputencoding from utf8 to auto-legacy leads to no iconv
> error. Is that a reasonable thing to do? I don't understand encodings
> well.
This is one possibility. The other one, which makes more sense in
contemporary LaT
Am Samstag, dem 10.12.2022 um 12:34 +0100 schrieb Kornel Benko:
> The error shows while checking IEEEabrv.bib, which is latin1 encoded
> (and not UTF-8 as
> expected).
> The problem is with the name
> 'Nicolás Barabino'. (bibtex/bib/ieeetran/IEEEabrv.bib:24)
Fixed.
--
Jürgen
signature.as
Am Sat, 10 Dec 2022 08:52:25 +0100
schrieb Kornel Benko :
> Am Fri, 9 Dec 2022 14:41:03 -0500
> schrieb Scott Kostyshak :
>
> > On Fri, Dec 09, 2022 at 07:28:03PM +0100, Kornel Benko wrote:
> > > Am Fri, 9 Dec 2022 12:08:27 -0500
> > > schrieb Scott Kostyshak :
> > >
> > > > When opening I
Am Fri, 9 Dec 2022 14:41:03 -0500
schrieb Scott Kostyshak :
> On Fri, Dec 09, 2022 at 07:28:03PM +0100, Kornel Benko wrote:
> > Am Fri, 9 Dec 2022 12:08:27 -0500
> > schrieb Scott Kostyshak :
> >
> > > When opening IEEEtran-Conference.lyx I get iconv errors:
> > >
> > > Error 84 returned fro
On Fri, Dec 09, 2022 at 07:28:03PM +0100, Kornel Benko wrote:
> Am Fri, 9 Dec 2022 12:08:27 -0500
> schrieb Scott Kostyshak :
>
> > When opening IEEEtran-Conference.lyx I get iconv errors:
> >
> > Error 84 returned from iconv when converting from UTF-8 to UCS-4LE:
> > Invalid or incomplete mu
Am Fri, 9 Dec 2022 12:08:27 -0500
schrieb Scott Kostyshak :
> When opening IEEEtran-Conference.lyx I get iconv errors:
>
> Error 84 returned from iconv when converting from UTF-8 to UCS-4LE:
> Invalid or incomplete multibyte or wide character Converted input:
> 0x0a 0x49 ... [cut]
>
> Chan
El 10.09.2017 a las 14:18, Uwe Stöhr escribió:
I just compiled the current 2.3.x branch to perform some final tests. I
noted some avoidable compiler warnings in libiconv, see below
I reported the warnings to the email address and got already a reply.
They will analyze the signed/unsigned
On Wed, Mar 01, 2017 at 05:35:45PM +, Guenter Milde wrote:
> This confirms it as an instance of #9871 (or related to it).
Good, I added the information to the ticket.
Scott
signature.asc
Description: PGP signature
On 2017-03-01, Kornel Benko wrote:
> Am Mittwoch, 1. März 2017 um 11:35:45, schrieb Guenter Milde
>
>> On 2017-03-01, Scott Kostyshak wrote:
>> >> > Note that this affects lib/examples/es/linguistics.lyx
>> >> >
>> >> > Can anyone else reproduce? Is the problem obvious?
>> >> >
>> >> > I can r
On Wed, Mar 01, 2017 at 11:35:45AM +, Guenter Milde wrote:
> 36b9645b is part of the fix to #9740 (XeTeX with TeX fonts).
> (BTW: how do you get the content/description of a change-set given this
> strange number only?)
git show 36b9645b
Does that do what you want? The number is referred to
On Wed, Mar 01, 2017 at 11:41:50AM +, Guenter Milde wrote:
> On 2017-02-28, Scott Kostyshak wrote:
> > On Tue, Feb 28, 2017 at 02:07:38PM -0500, Scott Kostyshak wrote:
>
> >> Note that this affects lib/examples/es/linguistics.lyx
>
> >> Can anyone else reproduce? Is the problem obvious?
>
>
Am Mittwoch, 1. März 2017 um 11:35:45, schrieb Guenter Milde
> On 2017-03-01, Scott Kostyshak wrote:
> > On Tue, Feb 28, 2017 at 06:24:51PM -0500, Scott Kostyshak wrote:
> >> On Tue, Feb 28, 2017 at 02:07:38PM -0500, Scott Kostyshak wrote:
>
> >> > Note that this affects lib/examples/es/linguist
On 2017-02-28, Scott Kostyshak wrote:
> On Tue, Feb 28, 2017 at 02:07:38PM -0500, Scott Kostyshak wrote:
>> Note that this affects lib/examples/es/linguistics.lyx
>> Can anyone else reproduce? Is the problem obvious?
>> I can reproduce the issue on 2.2.0 and on master. I cannot reproduce on
>> 2
On 2017-03-01, Scott Kostyshak wrote:
> On Tue, Feb 28, 2017 at 06:24:51PM -0500, Scott Kostyshak wrote:
>> On Tue, Feb 28, 2017 at 02:07:38PM -0500, Scott Kostyshak wrote:
>> > Note that this affects lib/examples/es/linguistics.lyx
>> >
>> > Can anyone else reproduce? Is the problem obvious?
>>
On Tue, Feb 28, 2017 at 06:24:51PM -0500, Scott Kostyshak wrote:
> On Tue, Feb 28, 2017 at 02:07:38PM -0500, Scott Kostyshak wrote:
>
> > Note that this affects lib/examples/es/linguistics.lyx
> >
> > Can anyone else reproduce? Is the problem obvious?
> >
> > I can reproduce the issue on 2.2.0 a
On Tue, Feb 28, 2017 at 02:07:38PM -0500, Scott Kostyshak wrote:
> Note that this affects lib/examples/es/linguistics.lyx
>
> Can anyone else reproduce? Is the problem obvious?
>
> I can reproduce the issue on 2.2.0 and on master. I cannot reproduce on
> 2.1.0. I can do a git bisect if someone t
On 2009-03-27, John McCabe-Dansted wrote:
> On Fri, Mar 27, 2009 at 8:43 PM, Guenter Milde wrote:
>> Setting Document>Settings>Language>Encoding to UTF8 (ucs enhanced/utf8x)
>> solves this particular problem.
> Would this be a sensible default?
No, because
a) it does not solve all cases
b) the u
On Fri, Mar 27, 2009 at 8:43 PM, Guenter Milde wrote:
> Setting Document>Settings>Language>Encoding to UTF8 (ucs enhanced/utf8x)
> solves this particular problem.
Would this be a sensible default?
> IMO, it is correct not to use the LaTeX transcription from
> "unicodesymbols" for ERT, as ERT is
On 2009-03-27, John McCabe-Dansted wrote:
> On Thu, Mar 26, 2009 at 5:44 PM, Guenter Milde wrote:
>> On 2009-03-26, John McCabe-Dansted wrote:
> Well, I agree that this isn't a real solution, but for the sake of
> argument:
>>> I get iconv errors quite regularly. I have written a python script
>>
On 2009-03-27, John McCabe-Dansted wrote:
> On Thu, Mar 26, 2009 at 6:54 PM, Jean-Marc Lasgouttes
> wrote:
>> John McCabe-Dansted writes:
>>> In the long run I don't think users should be expected to spend time
>>> manually fixing iconv errors.
>> No, but they should report them so that we can
Well, I agree that this isn't a real solution, but for the sake of argument:
On Thu, Mar 26, 2009 at 5:44 PM, Guenter Milde wrote:
> On 2009-03-26, John McCabe-Dansted wrote:
>> I get iconv errors quite regularly. I have written a python script
>> (filter) to remove all UTF characters. This is su
On Thu, Mar 26, 2009 at 6:54 PM, Jean-Marc Lasgouttes
wrote:
> John McCabe-Dansted writes:
>> In the long run I don't think users should be expected to spend time
>> manually fixing iconv errors. At worst LyX could pop up a dialog box:
>> "LyX cannot handle the following characters ... [Remove]
John McCabe-Dansted writes:
> In the long run I don't think users should be expected to spend time
> manually fixing iconv errors. At worst LyX could pop up a dialog box:
> "LyX cannot handle the following characters ... [Remove] [Replace]
> [Cancel]".
No, but they should report them so that we
On 2009-03-26, John McCabe-Dansted wrote:
> I get iconv errors quite regularly. I have written a python script
> (filter) to remove all UTF characters. This is sufficient for my
> purposes since I hardly ever use UTF
However, this is no solution for us umlaut-, accent-, Greek-, and
Cyrillic-loving
On Aug 22, 2006, at 12:14 PM, Jean-Marc Lasgouttes wrote:
"Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Bennett Helm wrote:
On Aug 22, 2006, at 9:55 AM, Jean-Marc Lasgouttes wrote:
And the second one? I think it is better.
That works, too. Bennett
Angus> Why does tex2lyx n
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Bennett Helm wrote:
>> On Aug 22, 2006, at 9:55 AM, Jean-Marc Lasgouttes wrote:
>>> And the second one? I think it is better.
>> That works, too. Bennett
Angus> Why does tex2lyx need all those -framework flags? It's a pure
Angus>
Bennett Helm wrote:
On Aug 22, 2006, at 9:55 AM, Jean-Marc Lasgouttes wrote:
And the second one? I think it is better.
That works, too.
Bennett
Why does tex2lyx need all those -framework flags? It's a pure console
app. Does it really need to link against Carbon, OpenGL, AGL and QuickTime?
> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
>> And the second one? I think it is better.
Bennett> That works, too.
This is applied now.
JMarc
On Aug 22, 2006, at 9:55 AM, Jean-Marc Lasgouttes wrote:
"Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Try the following patch.
Bennett> That does it -- thanks!
And the second one? I think it is better.
That works, too.
Bennett
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Jean-Marc" == Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
|
| > "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
| Bennett> After having been away for a couple weeks, I now find that
| Bennett> tex2lyx does not compile for me
> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
>> Try the following patch.
Bennett> That does it -- thanks!
And the second one? I think it is better.
JMarc
On Aug 22, 2006, at 9:37 AM, Jean-Marc Lasgouttes wrote:
"Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> After having been away for a couple weeks, I now find that
Bennett> tex2lyx does not compile for me on Mac OS X. I get:
Bennett> If I add "-liconv" to the LDFLAGS line, ever
> "Jean-Marc" == Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> After having been away for a couple weeks, I now find that
Bennett> tex2lyx does not compile for me on Mac OS X. I get:
Bennett> If I add "-liconv" to the LDF
> "Bennett" == Bennett Helm <[EMAIL PROTECTED]> writes:
Bennett> After having been away for a couple weeks, I now find that
Bennett> tex2lyx does not compile for me on Mac OS X. I get:
Bennett> If I add "-liconv" to the LDFLAGS line, everything works. Do
Bennett> I now need to set LDFLAGS exp
Jean-Marc Lasgouttes wrote:
And does it work?
Yes, I think so.
Joost
> "Joost" == Joost Verburg <[EMAIL PROTECTED]> writes:
Joost> Jean-Marc Lasgouttes wrote:
>> Joost, does the current 1.4.2svn build on windows have iconv
>> support built-in? This is pretty important.
Joost> Yes, iconv support is built-in.
And does it work?
JMarc
Jean-Marc Lasgouttes wrote:
Joost, does the current 1.4.2svn build on windows have iconv support
built-in? This is pretty important.
Yes, iconv support is built-in.
Joost
Peter Kümmel wrote:
> Bo Peng wrote:
>>> Iconv is for when the po file is not in the encoding requested by the
>>> locale. For example pl.po is in latin2, but the right charset for
>>> Polish is CP1251 (?) on windows. With iconv support, the strings will
>>> be transcoded transparently.
>> I will t
Bo Peng wrote:
>> Iconv is for when the po file is not in the encoding requested by the
>> locale. For example pl.po is in latin2, but the right charset for
>> Polish is CP1251 (?) on windows. With iconv support, the strings will
>> be transcoded transparently.
>
> I will try to link lyx/msvc with
Iconv is for when the po file is not in the encoding requested by the
locale. For example pl.po is in latin2, but the right charset for
Polish is CP1251 (?) on windows. With iconv support, the strings will
be transcoded transparently.
I will try to link lyx/msvc with mingw/iconv, and adjust SCon
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> The weird thing is that locale seems to work fine with
Abdelrazak> that. So what is this iconv for?
Iconv is for when the po file is not in the encoding requested by the
locale. For example pl.po is in latin2, but the
Peter Kümmel wrote:
the scons script defines for intl DEPENDS_ON_LIBICONV=1
but defines not HAVE_ICONV, does this mean we don't
link against iconv.
That would explain why I don't need iconvxx.dll to run my scons/mingw
lyx. And I never saw a single -liconv in the final linking.
The weird thin
On 6/8/06, Peter Kümmel <[EMAIL PROTECTED]> wrote:
the scons script defines for intl DEPENDS_ON_LIBICONV=1
but defines not HAVE_ICONV, does this mean we don't
link against iconv.
But what means depends on then?
Peter
I have no idea. I think I copied the flags from the Makefile.
Bo
44 matches
Mail list logo
