On Mon, Feb 22, 2010 at 02:33:34AM +0100, Uwe Stöhr wrote:
Am 21.02.2010 19:41, schrieb Enrico Forestieri:
This breaks the compilation. I now get this error:
Creating library release\lyx.lib and object release\lyx.exp
support.lib(os.obj) : error LNK2019: unresolved external symbol
On 02/20/2010 09:08 PM, Manoj Rajagopalan wrote:
Hi lyx developers,
Has someone suggested this feature for future inclusion yet? If not, how
should one go about implementing it?
One way would be to write a copier in python (so as to be cross
platform). Create a new format, say ltx2,
No.
The above error message states that
QString::fromWCharArray(wchar_t const *,int) is the problem.
I don't understand the error message but it seems that fromWCharArray
needs to be linked via a header file.
That header file is QString, which is already included. There, you
can
find the
I see the same, and I don't know what the problem is either. The
QString header can be found, Qstring can be used, just not this static
function. Maybe it is not exported or something..
Glad to hear that I'm not the only one having this problem. I'm using Qt
4.5.3. Vincent, Enrico, what Qt
I see the same, and I don't know what the problem is either. The
QString header can be found, Qstring can be used, just not this static
function. Maybe it is not exported or something..
Glad to hear that I'm not the only one having this problem. I'm using
Qt 4.5.3. Vincent, Enrico, what Qt
Is there any existing python code that does something similar? I could learn
from it. I see ext_copy.py in libs/scripts/. Is there any other file I could
look at?
-- Manoj
On Monday 22 February 2010 07:36:36 am Richard Heck wrote:
On 02/20/2010 09:08 PM, Manoj Rajagopalan wrote:
Hi lyx
On Mon, Feb 22, 2010 at 01:50:09PM +0100, Vincent van Ravesteijn - TNW wrote:
No.
The above error message states that
QString::fromWCharArray(wchar_t const *,int) is the problem.
I don't understand the error message but it seems that fromWCharArray
needs to be linked via a header
class Q_CORE_EXPORT QString
{
...
static QString fromWCharArray(const wchar_t *, int size = -1);
...
}
so, I really don't understand why you get the error. Are you sure
you
are
linking the QtCore library?
I see the same, and I don't know what the problem is either. The
On Mon, Feb 22, 2010 at 03:58:26PM +0100, Vincent van Ravesteijn - TNW wrote:
class Q_CORE_EXPORT QString
{
...
static QString fromWCharArray(const wchar_t *, int size = -1);
...
}
so, I really don't understand why you get the error. Are you sure
you
are
linking
Vincent van Ravesteijn - TNW schrieb:
Vincent, Enrico, what Qt version are you using?
(I can try to switch to Qt 4.6.2 and try again.)
4.7.
The development version of Qt? OK, then upgrading to 4.6.2 wouldn't fix
this issue.
Perhaps the problem is a bug in the Qt sources - André, can you
On Mon, Feb 22, 2010 at 04:35:00PM +0100, Uwe Stöhr wrote:
Vincent van Ravesteijn - TNW schrieb:
Vincent, Enrico, what Qt version are you using?
(I can try to switch to Qt 4.6.2 and try again.)
4.7.
The development version of Qt? OK, then upgrading to 4.6.2 wouldn't fix
this issue.
I
Guenter Milde wrote:
LyX's unicodesymbols file is more complete than inputenc's utf8
definitions, so this is just misleading.
Probably yes.
For now, your best bet is to open View Source, search for the
character (it is marked in red in the source), and remove it.
This is by far a more
On Mon, Feb 22, 2010 at 01:50:09PM +0100, Vincent van Ravesteijn - TNW wrote:
No.
The above error message states that
QString::fromWCharArray(wchar_t const *,int) is the problem.
I don't understand the error message but it seems that fromWCharArray
needs to be linked via a header
class Q_CORE_EXPORT QString
{
...
static QString fromWCharArray(const wchar_t *, int size = -1);
...
}
The function is new in 4.2, so one possibility is that you compile
against
4.2 headers but link against 4.1 libraries.
No, that's not the problem.
Export might be an issue,
On Mon, Feb 22, 2010 at 08:07:56PM +0100, Vincent van Ravesteijn - TNW wrote:
Depends.exe says:
class QString QString::fromWCharArray(unsigned short const *,int)
So, qt defines/typedefs wchar_t as unsigned short ??
No, that's not Qt, but Windows, in msvcrt.h if memory serves right.
A
On 2010-02-22, Jürgen Spitzmüller wrote:
Guenter Milde wrote:
LyX's unicodesymbols file is more complete than inputenc's utf8
definitions, so this is just misleading.
Probably yes.
For now, your best bet is to open View Source, search for the
character (it is marked in red in the
Compiling with: /Zc:wchar_t- solves it for me.
In MSVC this is called Treat wchar_t as Built-in Type : No. This is by
default set to Yes.
Can this be changed in the Scons and CMake scripts ?
Vincent
Am 22.02.2010 20:55, schrieb Andre Poenitz:
class QString QString::fromWCharArray(unsigned short const *,int)
So, qt defines/typedefs wchar_t as unsigned short ??
No, that's not Qt, but Windows, in msvcrt.h if memory serves right.
But Qt has only a short one defined ?
No, Qt uses the
No, Qt uses the wchar_t of the platform for the to/fromWChar functions
to communicate with wchar_t based functions of the host system. On
Windows that's a 16 bit type, on *nix traditionally 32 bit.
QString is internally UTF-16 on all platforms.
So what do you propose? LyX is currently
Author: sanda
Date: Mon Feb 22 03:01:04 2010
New Revision: 33533
URL: http://www.lyx.org/trac/changeset/33533
+ Compare * compare = new Compare(loadIfNeeded(FileName(f1)),
loadIfNeeded(FileName(f2)), dest, options);
+ compare-start(QThread::LowPriority);
+
sa...@lyx.org schreef:
Author: sanda
Date: Mon Feb 22 03:00:40 2010
New Revision: 33528
URL: http://www.lyx.org/trac/changeset/33528
Modified: lyx-devel/trunk/lib/ui/stdtoolbars.inc
==
---
sa...@lyx.org schreef:
Author: sanda
Date: Mon Feb 15 08:10:59 2010
New Revision: 33474
URL: http://www.lyx.org/trac/changeset/33474
-bool SVN::prepareFileRevision(int rev, string f)
+bool SVN::prepareFileRevision(string const revis, string f)
{
+ if (!isStrInt(revis))
+
On Mon, Feb 22, 2010 at 11:17:02PM +0100, Vincent van Ravesteijn wrote:
Compiling with: /Zc:wchar_t- solves it for me.
In MSVC this is called Treat wchar_t as Built-in Type : No. This is by
default set to Yes.
D'oh! And does it work without that option if you replace wchar_t *
with LPCWSTR
Enrico Forestieri schreef:
On Mon, Feb 22, 2010 at 11:17:02PM +0100, Vincent van Ravesteijn wrote:
Compiling with: /Zc:wchar_t- solves it for me.
In MSVC this is called Treat wchar_t as Built-in Type : No. This is by
default set to Yes.
D'oh! And does it work without that option if
On Tue, Feb 23, 2010 at 12:59:41AM +0100, Vincent van Ravesteijn wrote:
Enrico Forestieri schreef:
On Mon, Feb 22, 2010 at 11:17:02PM +0100, Vincent van Ravesteijn wrote:
Compiling with: /Zc:wchar_t- solves it for me.
In MSVC this is called Treat wchar_t as Built-in Type : No. This is
Enrico Forestieri schreef:
On Tue, Feb 23, 2010 at 12:59:41AM +0100, Vincent van Ravesteijn wrote:
Enrico Forestieri schreef:
On Mon, Feb 22, 2010 at 11:17:02PM +0100, Vincent van Ravesteijn wrote:
Compiling with: /Zc:wchar_t- solves it for me.
In MSVC this is called Treat
On Tue, Feb 23, 2010 at 01:28:44AM +0100, Vincent van Ravesteijn wrote:
Enrico Forestieri schreef:
On Tue, Feb 23, 2010 at 12:59:41AM +0100, Vincent van Ravesteijn wrote:
Enrico Forestieri schreef:
On Mon, Feb 22, 2010 at 11:17:02PM +0100, Vincent van Ravesteijn wrote:
Vincent van Ravesteijn wrote:
Why do you need the revision number for revision 0 ?
the idea was that user would be able to address revisions not only by absolute
revision number but also in relative manner, ie to let him address revisions
like -5 for five revisions back. naturally 0 happens to
Vincent van Ravesteijn wrote:
Why does the toolbar icon for vc-compare 0 has a -1 in it ?
i wanted to indicate backward time arrow :) maybe its just confusing,
feel free to prose something different or commit your own.
pavel
Vincent van Ravesteijn wrote:
Author: sanda
Date: Mon Feb 22 03:01:04 2010
New Revision: 33533
URL: http://www.lyx.org/trac/changeset/33533
+Compare * compare = new Compare(loadIfNeeded(FileName(f1)),
loadIfNeeded(FileName(f2)), dest, options);
+
1. What exactly is a copier supposed to do? Looking at the python scripts, it
seems like they are fancy copy operations which need an input file to start
with, and perform some basic operations like search-and-replace while
copying.
2. How and when is a copier invoked? For exporting latex
On Mon, Feb 22, 2010 at 02:33:34AM +0100, Uwe Stöhr wrote:
> Am 21.02.2010 19:41, schrieb Enrico Forestieri:
>
This breaks the compilation. I now get this error:
Creating library release\lyx.lib and object release\lyx.exp
support.lib(os.obj) : error LNK2019: unresolved external
On 02/20/2010 09:08 PM, Manoj Rajagopalan wrote:
Hi lyx developers,
Has someone suggested this feature for future inclusion yet? If not, how
should one go about implementing it?
One way would be to write a "copier" in python (so as to be cross
platform). Create a new format, say ltx2,
>> No.
>> The above error message states that
>> QString::fromWCharArray(wchar_t const *,int) is the problem.
>> I don't understand the error message but it seems that fromWCharArray
>> needs to be linked via a header file.
>
>That header file is , which is already included. There, you
can
>find
> I see the same, and I don't know what the problem is either. The
> QString header can be found, Qstring can be used, just not this static
> function. Maybe it is not exported or something..
Glad to hear that I'm not the only one having this problem. I'm using Qt
4.5.3. Vincent, Enrico, what
>> I see the same, and I don't know what the problem is either. The >
QString header can be found, Qstring can be used, just not this static
> function. Maybe it is not exported or something..
>Glad to hear that I'm not the only one having this problem. I'm using
Qt 4.5.3. Vincent, Enrico, what
Is there any existing python code that does something similar? I could learn
from it. I see ext_copy.py in libs/scripts/. Is there any other file I could
look at?
-- Manoj
On Monday 22 February 2010 07:36:36 am Richard Heck wrote:
> On 02/20/2010 09:08 PM, Manoj Rajagopalan wrote:
> > Hi
On Mon, Feb 22, 2010 at 01:50:09PM +0100, Vincent van Ravesteijn - TNW wrote:
>
> >> No.
> >> The above error message states that
> >> QString::fromWCharArray(wchar_t const *,int) is the problem.
> >> I don't understand the error message but it seems that fromWCharArray
>
> >> needs to be linked
>> >class Q_CORE_EXPORT QString
>> >{
>> >...
>> >static QString fromWCharArray(const wchar_t *, int size = -1);
>> >...
>> >}
>> >
>> >so, I really don't understand why you get the error. Are you sure
you
>> are
>> >linking the QtCore library?
>> >
>>
>> I see the same, and I don't
On Mon, Feb 22, 2010 at 03:58:26PM +0100, Vincent van Ravesteijn - TNW wrote:
>
> >> >class Q_CORE_EXPORT QString
> >> >{
> >> >...
> >> >static QString fromWCharArray(const wchar_t *, int size = -1);
> >> >...
> >> >}
> >> >
> >> >so, I really don't understand why you get the error.
Vincent van Ravesteijn - TNW schrieb:
Vincent, Enrico, what Qt version are you using?
(I can try to switch to Qt 4.6.2 and try again.)
4.7.
The development version of Qt? OK, then upgrading to 4.6.2 wouldn't fix
this issue.
Perhaps the problem is a bug in the Qt sources - André, can you
On Mon, Feb 22, 2010 at 04:35:00PM +0100, Uwe Stöhr wrote:
> Vincent van Ravesteijn - TNW schrieb:
>
>>> Vincent, Enrico, what Qt version are you using?
>>> (I can try to switch to Qt 4.6.2 and try again.)
>>
>> 4.7.
>
> The development version of Qt? OK, then upgrading to 4.6.2 wouldn't fix
>
Guenter Milde wrote:
> LyX's unicodesymbols file is more complete than inputenc's utf8
> definitions, so this is just misleading.
Probably yes.
> > For now, your best bet is to open View > Source, search for the
> > character (it is marked in red in the source), and remove it.
>
> This is by
On Mon, Feb 22, 2010 at 01:50:09PM +0100, Vincent van Ravesteijn - TNW wrote:
>
> >> No.
> >> The above error message states that
> >> QString::fromWCharArray(wchar_t const *,int) is the problem.
> >> I don't understand the error message but it seems that fromWCharArray
>
> >> needs to be linked
> >class Q_CORE_EXPORT QString
> >{
> >...
> >static QString fromWCharArray(const wchar_t *, int size = -1);
> >...
> >}
> >
>The function is new in 4.2, so one possibility is that you compile
against
>4.2 headers but link against 4.1 libraries.
No, that's not the problem.
>Export
On Mon, Feb 22, 2010 at 08:07:56PM +0100, Vincent van Ravesteijn - TNW wrote:
> Depends.exe says:
>
> "class QString QString::fromWCharArray(unsigned short const *,int)"
>
> So, qt defines/typedefs wchar_t as unsigned short ??
No, that's not Qt, but Windows, in msvcrt.h if memory serves right.
On 2010-02-22, Jürgen Spitzmüller wrote:
> Guenter Milde wrote:
>> LyX's unicodesymbols file is more complete than inputenc's utf8
>> definitions, so this is just misleading.
> Probably yes.
>> > For now, your best bet is to open View > Source, search for the
>> > character (it is marked in red
Compiling with: "/Zc:wchar_t-" solves it for me.
In MSVC this is called "Treat wchar_t as Built-in Type : No". This is by
default set to Yes.
Can this be changed in the Scons and CMake scripts ?
Vincent
Am 22.02.2010 20:55, schrieb Andre Poenitz:
"class QString QString::fromWCharArray(unsigned short const *,int)"
So, qt defines/typedefs wchar_t as unsigned short ??
No, that's not Qt, but Windows, in msvcrt.h if memory serves right.
But Qt has only a short one defined ?
No, Qt uses the
No, Qt uses the wchar_t of the platform for the to/fromWChar functions
to communicate with wchar_t based functions of the host system. On
Windows that's a 16 bit type, on *nix traditionally 32 bit.
QString is internally UTF-16 on all platforms.
So what do you propose? LyX is currently
Author: sanda
Date: Mon Feb 22 03:01:04 2010
New Revision: 33533
URL: http://www.lyx.org/trac/changeset/33533
+ Compare * compare = new Compare(loadIfNeeded(FileName(f1)),
loadIfNeeded(FileName(f2)), dest, options);
+ compare->start(QThread::LowPriority);
+
sa...@lyx.org schreef:
Author: sanda
Date: Mon Feb 22 03:00:40 2010
New Revision: 33528
URL: http://www.lyx.org/trac/changeset/33528
Modified: lyx-devel/trunk/lib/ui/stdtoolbars.inc
==
---
sa...@lyx.org schreef:
Author: sanda
Date: Mon Feb 15 08:10:59 2010
New Revision: 33474
URL: http://www.lyx.org/trac/changeset/33474
-bool SVN::prepareFileRevision(int rev, string & f)
+bool SVN::prepareFileRevision(string const & revis, string & f)
{
+ if (!isStrInt(revis))
+
On Mon, Feb 22, 2010 at 11:17:02PM +0100, Vincent van Ravesteijn wrote:
> Compiling with: "/Zc:wchar_t-" solves it for me.
>
> In MSVC this is called "Treat wchar_t as Built-in Type : No". This is by
> default set to Yes.
D'oh! And does it work without that option if you replace "wchar_t *"
Enrico Forestieri schreef:
On Mon, Feb 22, 2010 at 11:17:02PM +0100, Vincent van Ravesteijn wrote:
Compiling with: "/Zc:wchar_t-" solves it for me.
In MSVC this is called "Treat wchar_t as Built-in Type : No". This is by
default set to Yes.
D'oh! And does it work without that
On Tue, Feb 23, 2010 at 12:59:41AM +0100, Vincent van Ravesteijn wrote:
> Enrico Forestieri schreef:
>> On Mon, Feb 22, 2010 at 11:17:02PM +0100, Vincent van Ravesteijn wrote:
>>
>>> Compiling with: "/Zc:wchar_t-" solves it for me.
>>>
>>> In MSVC this is called "Treat wchar_t as Built-in Type
Enrico Forestieri schreef:
On Tue, Feb 23, 2010 at 12:59:41AM +0100, Vincent van Ravesteijn wrote:
Enrico Forestieri schreef:
On Mon, Feb 22, 2010 at 11:17:02PM +0100, Vincent van Ravesteijn wrote:
Compiling with: "/Zc:wchar_t-" solves it for me.
In MSVC this is called
On Tue, Feb 23, 2010 at 01:28:44AM +0100, Vincent van Ravesteijn wrote:
> Enrico Forestieri schreef:
>> On Tue, Feb 23, 2010 at 12:59:41AM +0100, Vincent van Ravesteijn wrote:
>>
>>> Enrico Forestieri schreef:
>>>
On Mon, Feb 22, 2010 at 11:17:02PM +0100, Vincent van Ravesteijn wrote:
Vincent van Ravesteijn wrote:
> Why do you need the revision number for revision 0 ?
the idea was that user would be able to address revisions not only by absolute
revision number but also in relative manner, ie to let him address revisions
like -5 for five revisions back. naturally 0 happens to
Vincent van Ravesteijn wrote:
> Why does the toolbar icon for "vc-compare 0" has a "-1" in it ?
i wanted to indicate backward time arrow :) maybe its just confusing,
feel free to prose something different or commit your own.
pavel
Vincent van Ravesteijn wrote:
>>
>> Author: sanda
>> Date: Mon Feb 22 03:01:04 2010
>> New Revision: 33533
>> URL: http://www.lyx.org/trac/changeset/33533
>>
>> +Compare * compare = new Compare(loadIfNeeded(FileName(f1)),
>> loadIfNeeded(FileName(f2)), dest, options);
>> +
1. What exactly is a copier supposed to do? Looking at the python scripts, it
seems like they are fancy copy operations which need an input file to start
with, and perform some basic operations like search-and-replace while
copying.
2. How and when is a copier invoked? For exporting latex
62 matches
Mail list logo
