Enrico Forestieri wrote:
> On Tue, Nov 28, 2006 at 09:21:01AM +0100, Georg Baum wrote:
>> Michael Gerz wrote:
>>
>> > I don't know what cause the problem - the colon, the backslash, the
>> > space, or the German Umlaut. Do you have any idea?
>>
>> Yes. Non-ascii filenames do not work at all. See
On Tue, Nov 28, 2006 at 09:21:01AM +0100, Georg Baum wrote:
> Michael Gerz wrote:
>
> > I don't know what cause the problem - the colon, the backslash, the
> > space, or the German Umlaut. Do you have any idea?
>
> Yes. Non-ascii filenames do not work at all. See the thread "unicode and
> filenam
Michael Gerz wrote:
> I don't know what cause the problem - the colon, the backslash, the
> space, or the German Umlaut. Do you have any idea?
Yes. Non-ascii filenames do not work at all. See the thread "unicode and
filenames" for details.
Georg
Georg Baum schrieb:
Am Montag, 27. November 2006 16:46 schrieb Michael Gerz:
Hi,
when loading a perfectly valid LyX 1.3 document with a freshly built
LyX/Win, I get lots of error messages:
Error returned from iconv
EILSEQ An invalid multibyte sequence has been encountered in the input.
Wh
Am Montag, 27. November 2006 16:46 schrieb Michael Gerz:
> Hi,
>
> when loading a perfectly valid LyX 1.3 document with a freshly built
> LyX/Win, I get lots of error messages:
>
> Error returned from iconv
> EILSEQ An invalid multibyte sequence has been encountered in the input.
> When converti
Hi,
when loading a perfectly valid LyX 1.3 document with a freshly built
LyX/Win, I get lots of error messages:
Error returned from iconv
EILSEQ An invalid multibyte sequence has been encountered in the input.
When converting from UTF-8 to UCS-4LE.
Input: 0x63 0x3a 0x2f 0x44 0x6f 0x6b 0x75 0x6
Hossein Noorikhah wrote:
Hi.
Has anyone applied the patch on SVN? I'm still having this problem
with the latest SVN version(revision 14809) of the Lars Gullik
Bjønnes's unicode branch, using Debian Sarge with gcc version 3.3.5.
Hello Hossein,
The unicode branch has been merged in trunk. I thin
Hi.
Has anyone applied the patch on SVN? I'm still having this problem
with the latest SVN version(revision 14809) of the Lars Gullik
Bjønnes's unicode branch, using Debian Sarge with gcc version 3.3.5.
Hossein
Lars Gullik Bjønnes wrote:
> Georg Baum <[EMAIL PROTECTED]>
> writes:
>
> | Could we not simply put the template solution in? Even if you'd like the
> | other one better, this is code for an older compiler that will go away
> | some day. I just don't think that we should drop support for gcc 3.3
Georg Baum <[EMAIL PROTECTED]> writes:
| Could we not simply put the template solution in? Even if you'd like the
| other one better, this is code for an older compiler that will go away some
| day. I just don't think that we should drop support for gcc 3.3 now.
Yes. Put that in for now. I'll hav
Lars Gullik Bjønnes wrote:
> You are saying that we cannot have a
>
> template<> char_traits in the header file?
At least it does not work for some of the functions. I tried that, and the
result was multiple definitions of at least
char_traits::eof()eof() at the linking stage. There were
more, b
Georg Baum <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
|
| > Georg Baum <[EMAIL PROTECTED]>
| > writes:
| >
| > | Am Montag, 14. August 2006 20:11 schrieb Lars Gullik Bjønnes:
| > | > Ahh... that is what you have done.
| > | > But we should not add the templates ourself I think. O
Lars Gullik Bjønnes wrote:
> Georg Baum <[EMAIL PROTECTED]>
> writes:
>
> | Am Montag, 14. August 2006 20:11 schrieb Lars Gullik Bjønnes:
> | > Ahh... that is what you have done.
> | > But we should not add the templates ourself I think. Only the explit
> | > specialization of the functions.
> |
Georg Baum <[EMAIL PROTECTED]> writes:
| Am Montag, 14. August 2006 20:11 schrieb Lars Gullik Bjønnes:
| > Ahh... that is what you have done.
| > But we should not add the templates ourself I think. Only the explit
| > specialization of the functions.
| >
| > And we should make it be complete. (g
Am Montag, 14. August 2006 20:11 schrieb Lars Gullik Bjønnes:
> Ahh... that is what you have done.
> But we should not add the templates ourself I think. Only the explit
> specialization of the functions.
>
> And we should make it be complete. (gut feeling...)
OK, I can do both, but you did not a
Georg Baum <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
|
| > Georg Baum <[EMAIL PROTECTED]>
| > writes:
| >
| > | Lars,
| > |
| > | I get several undefined references like this one with current trunk (gcc
| > | 3.3.5, 32 bit):
| >
| > Your gcc is too old, and to fix it we must pr
Lars Gullik Bjønnes wrote:
> Georg Baum <[EMAIL PROTECTED]>
> writes:
>
> | Lars,
> |
> | I get several undefined references like this one with current trunk (gcc
> | 3.3.5, 32 bit):
>
> Your gcc is too old, and to fix it we must provide the specialization
> fo char_traits ourselves. Gcc4 has b
Georg Baum <[EMAIL PROTECTED]> writes:
| Lars,
|
| I get several undefined references like this one with current trunk (gcc
| 3.3.5, 32 bit):
Your gcc is too old, and to fix it we must provide the specialization
fo char_traits ourselves. Gcc4 has better QoI and
does the work for us.
| frontends
Lars,
I get several undefined references like this one with current trunk (gcc
3.3.5, 32 bit):
frontends/qt3/.libs/libqt3.a(qfont_metrics.o
(.gnu.linkonce.t._ZNSbIjSt11char_traitsIjESaIjEE13_S_copy_charsEPjS3_S3_+0x1c):
In function `std::basic_string,
std::allocator >::_S_copy_chars(unsigned*, un
19 matches
Mail list logo
