because while its acceptible that we have multiple ifdefs which
fixes changing
behaviour of Qt in UI it would be really nightmare if we read/
write .lyx file
wrongly because the shiny new qt version contains some unfortunate
bug. this
kind of stability seems to me as critical enough to
Steve Litt wrote:
> How does one tell what version of Qt is on his computer?
package manager of the distribution you use will tell.
pavel
Pavel Sanda writes:
> Steve Litt wrote:
>> How does one tell what version of Qt is on his computer?
>
> package manager of the distribution you use will tell.
Or the command "lyx -version".
JMarc
On 01/14/2010 05:18 AM, Pavel Sanda wrote:
Steve Litt wrote:
How does one tell what version of Qt is on his computer?
package manager of the distribution you use will tell.
Or launch qtconfig-qt4 and go to Help>About Qt.
rh
rgheck wrote:
On 01/14/2010 05:18 AM, Pavel Sanda wrote:
Steve Litt wrote:
How does one tell what version of Qt is on his computer?
package manager of the distribution you use will tell.
Or launch qtconfig-qt4 and go to Help>About Qt.
Or "qmake -v"
Abdel.
there is a pressing need to change the
way math is represented, a need that is part of what is driving the
change to XML.
And perhaps another thing to say here is that any XML-like
representation of math will definitely make sed-like script processing
of LyX files harder.
Richard
One other thought about the format.
In thinking about this, it occurred to me that there might be reasons to
have different tags for different sorts of insets. E.g.:
This would save the need to do some long switch on the "type" before we
can figure out where to go next. All the command
On 01/14/2010 03:05 AM, Guenter Milde wrote:
On 2010-01-13, Andre Poenitz wrote:
Try to use the 'layout oriented' bits of MathML and invent our own for
the few cases where there is no clean match.
I suggest keeping math in LaTeX format (inside a
tag). (This can be changed later, if
rgheck wrote:
Anyway, for now, it seems to me, we should leave math alone and just
do the boring thing I suggested earlier:
a+b=2^x
That's the best option indeed.
Abdel.
rgheck wrote:
On 01/13/2010 01:36 PM, José Matos wrote:
- how to proceed in the mean time?
+ using an iterative approach we will have a file that will be
xml-ized by
parts
I think the incremental approach will actually be much less intrusive
than it might at first seem, and some
On Thursday 14 January 2010 09:13:04 Abdelrazak Younes wrote:
> rgheck wrote:
> > On 01/13/2010 01:36 PM, José Matos wrote:
> >>- how to proceed in the mean time?
> >> + using an iterative approach we will have a file that will be
> >> xm
Steve Litt wrote:
On Thursday 14 January 2010 09:13:04 Abdelrazak Younes wrote:
rgheck wrote:
On 01/13/2010 01:36 PM, José Matos wrote:
- how to proceed in the mean time?
+ using an iterative approach we will have a file that will be
xml-ized by
parts
I think
On 2010-01-14, rgheck wrote:
> On 01/14/2010 03:05 AM, Guenter Milde wrote:
>> We could consider using Unicode characters for LaTeX macros which are
>> supported by our 'unicodesymbols' file, e.g. β for \beta and ∫ for \int.
> Here again, unless we're proposing to write \beta as β and then read
On 01/14/2010 05:28 PM, Guenter Milde wrote:
On 2010-01-14, rgheck wrote:
On 01/14/2010 03:05 AM, Guenter Milde wrote:
We could consider using Unicode characters for LaTeX macros which are
supported by our 'unicodesymbols' file, e.g. β for \beta and ∫ for \int.
Here
Hi all,
I would like to start working on the goal of having lyx with an xml file
format.
Some of the issues we will have to tackle:
- what parser library to use?
+ libxml2
+ boost variant
- how to proceed in the mean time?
+ using an iterative approach we will have a file
Hi all,
I would like to start working on the goal of having lyx
with an xml file format.
Some of the issues we will have to tackle:
- what parser library to use?
+ libxml2
+ boost variant
Qt ? http://qt.nokia.com/doc/4.6/xml-processing.html
Vincent
José Matos wrote:
Any other points that I had forget?
i didnt get one thing - you intend to push this into the current trunk or
after next lyx release?
pavel
On Wed, Jan 13, 2010 at 06:36:09PM +, José Matos wrote:
Hi all,
I would like to start working on the goal of having lyx with an xml file
format.
Some of the issues we will have to tackle:
- what parser library to use?
+ libxml2
+ boost variant
Any reason not to use
On 01/13/2010 01:41 PM, Pavel Sanda wrote:
José Matos wrote:
Any other points that I had forget?
i didnt get one thing - you intend to push this into the current trunk or
after next lyx release?
Speaking of the next release, I think we should also think about that.
We have a
On 01/13/2010 01:36 PM, José Matos wrote:
- how to proceed in the mean time?
+ using an iterative approach we will have a file that will be xml-ized by
parts
I think the incremental approach will actually be much less intrusive
than it might at first seem, and some
+ the code that I already have in lyx2lyx deals easily with all the other
stuff (the patch I was working follows attached, this is only an hint we could
use a different implementation but I think that this server as a good first
step to boost the discussion on the topic).
FYI, I
one that they are just
dying to get it, we might consider a formal feature freeze fairly soon.
major features freeze and release of alpha was my thought behind.
all advertised (big) features are basically in trunk plus minus some
finishing.
with pusing xml in i expect again next year without
On Wednesday 13 January 2010 13:36:09 José Matos wrote:
Hi all,
I would like to start working on the goal of having lyx with an xml file
format.
Once again I'd like to say that if not done exactly right, XMLizing LyX native
format will disenfranchise the significant minority of users who
On 01/13/2010 04:13 PM, Steve Litt wrote:
On Wednesday 13 January 2010 13:36:09 José Matos wrote:
Hi all,
I would like to start working on the goal of having lyx with an xml file
format.
Once again I'd like to say that if not done exactly right, XMLizing LyX native
format
people like the 80 character limit, precisely
to be able to view things nicely in vim, etc.
AFAICR from relatively short xml experience, new lines are likely to
begin with whitespaces and the closing tag of the previous line (this
allows for indenting xml code and keep whitespaces away from
On Wednesday 13 January 2010 18:40:59 Vincent van Ravesteijn - TNW wrote:
Hi all,
I would like to start working on the goal of having lyx
with an xml file format.
Some of the issues we will have to tackle:
- what parser library to use?
+ libxml2
+ boost variant
Qt
On Wednesday 13 January 2010 19:12:12 Pavel Sanda wrote:
major features freeze and release of alpha was my thought behind.
all advertised (big) features are basically in trunk plus minus some
finishing.
with pusing xml in i expect again next year without release.
XML file format is well
On Wednesday 13 January 2010 18:51:19 Andre Poenitz wrote:
Any reason not to use QXmlStreamReader?
None other, as I said before to Vincent, as to understand how Qt 4.2 of it
behaves.
- what to do with math?
Try to use the 'layout oriented' bits of MathML and invent our own for
the few
José Matos schreef:
On Wednesday 13 January 2010 18:40:59 Vincent van Ravesteijn - TNW wrote:
Hi all,
I would like to start working on the goal of having lyx
with an xml file format.
Some of the issues we will have to tackle:
- what parser library to use?
+ libxml2
+ boost
On Wednesday 13 January 2010 19:08:30 rgheck wrote:
FYI, I think one write_xml() routine is enough. ;-)
:-)
I can change the name if you insist. :-)
rh
--
José Abílio
José Matos wrote:
But sure I am open for the next release to be made without XML.
considering rather finishing status of work on bigger features i think
this is the reasonable way. even before few months people asked about
intermediate release which raises few questions on our release maintainer
am saying this before checking as remember vaguely to see in the release
notes of the previous Qt releases references to how improved the XML handling
was made. So treat this as if I was thinking aloud and you all heard. ;-)
Vincent
--
José Abílio
José Matos wrote:
+ libxml2
+ boost variant
Qt ? http://qt.nokia.com/doc/4.6/xml-processing.html
are there some differences as far as 'stability' is concerned?
because while its acceptible that we have multiple ifdefs which fixes changing
behaviour of Qt in UI it would be really
On Wednesday 13 January 2010 19:39:40 José Matos wrote:
OK, that would imply to bump Qt requirement to 4.3 (not too bad) but before
doing that are we sure that this version works for our needs?
How does one tell what version of Qt is on his computer?
SteveT
Steve Litt
Recession Relief
Hi all,
I would like to start working on the goal of having lyx with an xml file
format.
Some of the issues we will have to tackle:
- what parser library to use?
+ libxml2
+ boost variant
- how to proceed in the mean time?
+ using an iterative approach we will have a file
>Hi all,
>
>I would like to start working on the goal of having lyx
>with an xml file format.
>
>Some of the issues we will have to tackle:
> - what parser library to use?
>+ libxml2
>+ boost variant
>
Qt ? http://qt.nokia.com/doc/4.6/xml-processing.html
Vincent
José Matos wrote:
> Any other points that I had forget?
i didnt get one thing - you intend to push this into the current trunk or
after next lyx release?
pavel
On Wed, Jan 13, 2010 at 06:36:09PM +, José Matos wrote:
> Hi all,
>
> I would like to start working on the goal of having lyx with an xml file
> format.
>
> Some of the issues we will have to tackle:
> - what parser library to use?
> + libxml2
>
On 01/13/2010 01:41 PM, Pavel Sanda wrote:
José Matos wrote:
Any other points that I had forget?
i didnt get one thing - you intend to push this into the current trunk or
after next lyx release?
Speaking of the next release, I think we should also think about that.
We have a
On 01/13/2010 01:36 PM, José Matos wrote:
- how to proceed in the mean time?
+ using an iterative approach we will have a file that will be xml-ized by
parts
I think the incremental approach will actually be much less intrusive
than it might at first seem, and some
+ the code that I already have in lyx2lyx deals easily with all the other
stuff (the patch I was working follows attached, this is only an hint we could
use a different implementation but I think that this server as a good first
step to boost the discussion on the topic).
FYI, I
ut that. We
> have a LOT of new features, so unless someone has one that they are just
> dying to get it, we might consider a formal feature freeze fairly soon.
major features freeze and release of alpha was my thought behind.
all advertised (big) features are basically in trunk plus minus some
On Wednesday 13 January 2010 13:36:09 José Matos wrote:
> Hi all,
>
> I would like to start working on the goal of having lyx with an xml file
> format.
Once again I'd like to say that if not done exactly right, XMLizing LyX native
format will disenfranchise the significant minor
On 01/13/2010 04:13 PM, Steve Litt wrote:
On Wednesday 13 January 2010 13:36:09 José Matos wrote:
Hi all,
I would like to start working on the goal of having lyx with an xml file
format.
Once again I'd like to say that if not done exactly right, XMLizing LyX native
format
e people like the 80 character limit, precisely
to be able to view things nicely in vim, etc.
AFAICR from relatively short xml experience, new lines are likely to
begin with whitespaces and the closing tag of the previous line (this
allows for indenting xml code and keep whitespaces away from th
On Wednesday 13 January 2010 18:40:59 Vincent van Ravesteijn - TNW wrote:
> >Hi all,
> >
> >I would like to start working on the goal of having lyx
> >with an xml file format.
> >
> >Some of the issues we will have to tackle:
> > - what parser library to
On Wednesday 13 January 2010 19:12:12 Pavel Sanda wrote:
> major features freeze and release of alpha was my thought behind.
> all advertised (big) features are basically in trunk plus minus some
> finishing.
>
> with pusing xml in i expect again next year without release.
On Wednesday 13 January 2010 18:51:19 Andre Poenitz wrote:
> Any reason not to use QXmlStreamReader?
None other, as I said before to Vincent, as to understand how Qt 4.2 of it
behaves.
> > - what to do with math?
>
> Try to use the 'layout oriented' bits of MathML and invent our own for
>
José Matos schreef:
On Wednesday 13 January 2010 18:40:59 Vincent van Ravesteijn - TNW wrote:
Hi all,
I would like to start working on the goal of having lyx
with an xml file format.
Some of the issues we will have to tackle:
- what parser library to use?
+ libxml2
+ boost
On Wednesday 13 January 2010 19:08:30 rgheck wrote:
> FYI, I think one write_xml() routine is enough. ;-)
:-)
I can change the name if you insist. :-)
> rh
--
José Abílio
José Matos wrote:
> But sure I am open for the next release to be made without XML.
considering rather finishing status of work on bigger features i think
this is the reasonable way. even before few months people asked about
intermediate release which raises few questions on our rele
ds?
I am saying this before checking as remember vaguely to see in the release
notes of the previous Qt releases references to how improved the XML handling
was made. So treat this as if I was thinking aloud and you all heard. ;-)
> Vincent
--
José Abílio
José Matos wrote:
> > >+ libxml2
> > >+ boost variant
> >
> > Qt ? http://qt.nokia.com/doc/4.6/xml-processing.html
are there some differences as far as 'stability' is concerned?
because while its acceptible that we have multiple ifdefs which fixes changing
On Wednesday 13 January 2010 19:39:40 José Matos wrote:
> OK, that would imply to bump Qt requirement to 4.3 (not too bad) but before
> doing that are we sure that this version works for our needs?
How does one tell what version of Qt is on his computer?
SteveT
Steve Litt
Recession Relief
the least).
Have you succeeded in taking that output?
There are two solutions that are possible:
- either to post-process the generated xml file with an external script
- or to change the generation code to take into account the new syntax. The
inline text styles could be expand to support
I am sorry for taking so long to answer. I was on vacation the previous 2
weeks and the end of the semester here was really busy (to say the least).
Have you succeeded in taking that output?
There are two solutions that are possible:
- either to post-process the generated xml file
eeks and the end of the semester here was really busy (to say the least).
Have you succeeded in taking that output?
There are two solutions that are possible:
- either to post-process the generated xml file with an external script
- or to change the generation code to take into account the new
I am sorry for taking so long to answer. I was on vacation the previous 2
weeks and the end of the semester here was really busy (to say the least).
Have you succeeded in taking that output?
There are two solutions that are possible:
- either to post-process the generated xml file
Hello,
I am currently trying to customize the docbook layout so as to produce
some scilab documentation (which is based ona subset of docbook).
I need to pass some options to xml tags.
Is it possible to:
- add a non modifiable option to a tag like
refentry version=5.0-subset Scilab xml:id=optim
On Wednesday 08 July 2009 07:18:20 ycol...@freesurf.fr wrote:
Hello,
I am currently trying to customize the docbook layout so as to produce
some scilab documentation (which is based ona subset of docbook).
I need to pass some options to xml tags.
Is it possible to:
- add a non modifiable
- Without looking further into the code I would say that this is not
possible now but it should be possible with some simple changes to the
generalized text styles. Take a look into the Edit-Text Styles.
- It should be easy to extend the code to what you intend to. I can give
more details if you
Hello,
I am currently trying to customize the docbook layout so as to produce
some scilab documentation (which is based ona subset of docbook).
I need to pass some options to xml tags.
Is it possible to:
- add a non modifiable option to a tag like
http://docbook.org/ns/docbook
On Wednesday 08 July 2009 07:18:20 ycol...@freesurf.fr wrote:
> Hello,
>
> I am currently trying to customize the docbook layout so as to produce
> some scilab documentation (which is based ona subset of docbook).
> I need to pass some options to xml tags.
> Is it possible
- Without looking further into the code I would say that this is not
possible now but it should be possible with some simple changes to the
generalized text styles. Take a look into the Edit->Text Styles.
- It should be easy to extend the code to what you intend to. I can give
more details if you
On Monday 06 July 2009 21:37:14 Pavel Sanda wrote:
what you are talking about is 2. and was never planned for 2.0
in particular. the problem is that we dont have any active
developer who understands this area, so while we can agree
that having working Docbook 4.4 XML output would be nice
On Monday 06 July 2009 21:37:14 Pavel Sanda wrote:
> what you are talking about is 2. and was never planned for 2.0
> in particular. the problem is that we dont have any active
> developer who understands this area, so while we can agree
> that having working Docbook 4.4 XML output w
Douglas Ray wrote:
XML was an aim for LyX 2.x, but the devel wiki only
mentions it briefly. I didn't find any follow-up.
there are two things not to be confused here:
1. internal LyX format.
2. output format of LyX document.
what you are talking about is 2. and was never planned for 2.0
Douglas Ray wrote:
> XML was an aim for LyX 2.x, but the devel wiki only
> mentions it briefly. I didn't find any follow-up.
there are two things not to be confused here:
1. internal LyX format.
2. output format of LyX document.
what you are talking about is 2. and was never planned f
XML was an aim for LyX 2.x, but the devel wiki only
mentions it briefly. I didn't find any follow-up.
I offer Docbook 4.4 XML as a more specific target, in
case there are no better suggestions.
Why?
O'Reilly publishers now recommend Docbook 4.4 XML to
their authors (cf
http://oreilly.com
Douglas Ray wrote:
XML was an aim for LyX 2.x, but the devel wiki only
mentions it briefly. I didn't find any follow-up.
I offer Docbook 4.4 XML as a more specific target, in
case there are no better suggestions.
As you probably know, LyX already has a DocBook backend, but it currently
Jürgen Spitzmüller wrote:
Douglas Ray wrote:
XML was an aim for LyX 2.x, but the devel wiki only
mentions it briefly. I didn't find any follow-up.
I offer Docbook 4.4 XML as a more specific target, in
case there are no better suggestions.
As you probably know, LyX already has
Douglas Ray wrote:
Do you refer to an undocumented feature? Other ref's
only mention LyX produces SGML Docbook, not XML.
My statement is just based on the fact that LyX 1.6.x has an XML flavour and
that Buffer.cpp::writeDocBookSource outputs, amongst others, the following
header
XML was an aim for LyX 2.x, but the devel wiki only
mentions it briefly. I didn't find any follow-up.
I offer "Docbook 4.4 XML" as a more specific target, in
case there are no better suggestions.
Why?
O'Reilly publishers now recommend Docbook 4.4 XML to
their authors (cf
Douglas Ray wrote:
> XML was an aim for LyX 2.x, but the devel wiki only
> mentions it briefly. I didn't find any follow-up.
>
> I offer "Docbook 4.4 XML" as a more specific target, in
> case there are no better suggestions.
As you probably know, LyX alre
Jürgen Spitzmüller wrote:
Douglas Ray wrote:
XML was an aim for LyX 2.x, but the devel wiki only
mentions it briefly. I didn't find any follow-up.
I offer "Docbook 4.4 XML" as a more specific target, in
case there are no better suggestions.
As you probably know, LyX a
Douglas Ray wrote:
> Do you refer to an undocumented feature? Other ref's
> only mention LyX produces SGML Docbook, not XML.
My statement is just based on the fact that LyX 1.6.x has an XML flavour and
that Buffer.cpp::writeDocBookSource outputs, amongst others, the following
On Wednesday 29 April 2009 11:03:47 am rgheck wrote:
is maintainability. The LyX file format sometimes undergoes big changes,
and if we weren't moving (slowly, and maybe) to an XML-based format, I'd
be about to make some more such changes, just to simplify parsing. Not
to mention
Steve Litt wrote:
On Wednesday 29 April 2009 11:03:47 am rgheck wrote:
is maintainability. The LyX file format sometimes undergoes big changes,
and if we weren't moving (slowly, and maybe) to an XML-based format, I'd
be about to make some more such changes, just to simplify parsing
On Wed, Apr 29, 2009 at 01:14:21PM -0400, rgheck wrote:
Please remember, if and when you go XML, please make it simple to parse
without a full blown XML parser, so we DIYers can continue to tweak our
docs with Vim scripts and the like.
The plan is to use a validating parser, for reasons
in my terminology here. I don't know if he just
wants to use an XML parser, so that we know we're working with a
well-formed document, or a validating one. I know Lars had something
like a DTD at one point.
rh
On Wednesday 29 April 2009 02:14:41 pm Andre Poenitz wrote:
On Wed, Apr 29, 2009 at 01:14:21PM -0400, rgheck wrote:
Please remember, if and when you go XML, please make it simple to parse
without a full blown XML parser, so we DIYers can continue to tweak our
docs with Vim scripts
On Wednesday 29 April 2009 11:03:47 am rgheck wrote:
> is maintainability. The LyX file format sometimes undergoes big changes,
> and if we weren't moving (slowly, and maybe) to an XML-based format, I'd
> be about to make some more such changes, just to simplify parsing. Not
>
Steve Litt wrote:
On Wednesday 29 April 2009 11:03:47 am rgheck wrote:
is maintainability. The LyX file format sometimes undergoes big changes,
and if we weren't moving (slowly, and maybe) to an XML-based format, I'd
be about to make some more such changes, just to simplify parsing
On Wed, Apr 29, 2009 at 01:14:21PM -0400, rgheck wrote:
>> Please remember, if and when you go XML, please make it simple to parse
>> without a full blown XML parser, so we DIYers can continue to tweak our
>> docs with Vim scripts and the like.
>
> The plan is to
way, I may be wrong in my terminology here. I don't know if he just
wants to use an XML parser, so that we know we're working with a
well-formed document, or a validating one. I know Lars had something
like a DTD at one point.
rh
On Wednesday 29 April 2009 02:14:41 pm Andre Poenitz wrote:
> On Wed, Apr 29, 2009 at 01:14:21PM -0400, rgheck wrote:
> >> Please remember, if and when you go XML, please make it simple to parse
> >> without a full blown XML parser, so we DIYers can continue to tweak our
>
a brainstorming for that page and after a fixed period of
time to sort out. At the same time that would allows us to involve all
contributors in the discussion.
FWIW with the transition to xml it becomes quite easy to compare if two lyx
documents are equal or not.
PS: The only reason why I am
On Tuesday 18 November 2008 21:21:15 rgheck wrote:
I'm perfectly happy for you to co-ordinate it. I think you're obviously
the right choice, in fact. Mostly, the question was whether we have a
roadmap and what I can do to help. So I'll wait for the other message on
that.
OK.
+def
Richard Heck wrote:
Pavel Sanda wrote:
José Matos wrote:
The next step is to guarantee that the conversion is correct and that
there are no data loss in the process.
it would be good to synchronize on this point once you start to work on
it.
currently i'm aware of two other
erlin?
It would nice to do a brainstorming for that page and after a fixed period of
time to sort out. At the same time that would allows us to involve all
contributors in the discussion.
FWIW with the transition to xml it becomes quite easy to compare if two lyx
documents are equal or not.
PS:
On Tuesday 18 November 2008 21:21:15 rgheck wrote:
> I'm perfectly happy for you to co-ordinate it. I think you're obviously
> the right choice, in fact. Mostly, the question was whether we have a
> roadmap and what I can do to help. So I'll wait for the other message on
> that.
OK.
> >>> +def
Richard Heck wrote:
> Pavel Sanda wrote:
>> José Matos wrote:
>>
>>> The next step is to guarantee that the conversion is correct and that
>>> there are no data loss in the process.
>>>
>>
>> it would be good to synchronize on this point once you start to work on
>> it.
>> currently i'm
Hi,
I send attached a patch that allows lyx2lyx to generate xml.
With this patch I am able to produce valid xml for all the lyx files that we
carry in lyx.
There are several things missing:
1) lyx2lyx does to read those files.
2) lyx does not write neither reads those files.
3
José Matos wrote:
Hi,
I send attached a patch that allows lyx2lyx to generate xml.
With this patch I am able to produce valid xml for all the lyx files that we
carry in lyx.
There are several things missing:
1) lyx2lyx does to read those files.
So how do you want to approach
On Tuesday 18 November 2008 19:04:50 rgheck wrote:
José Matos wrote:
Hi,
I send attached a patch that allows lyx2lyx to generate xml.
With this patch I am able to produce valid xml for all the lyx files that
we carry in lyx.
There are several things missing:
1) lyx2lyx does
José Matos wrote:
On Tuesday 18 November 2008 19:04:50 rgheck wrote:
OK, well, I take it that this effort needs co-ordination and that you
are the man to co-ordinate it. So if you want at some point to give me
some particular tasks to do here, let me know.
The purpose of this code was
José Matos wrote:
The next step is to guarantee that the conversion is correct and that there
are no data loss in the process.
it would be good to synchronize on this point once you start to work on it.
currently i'm aware of two other relatedr tasks running which coordination would
be good to
be easily
installed
and it works for all versions of python that we support.
Code that illustrates the simplicity of the library will follow
tomorrow.
Note that among other advantages the conversion between xml will become
faster than what happens now.
Any problem
lxml.etree import parse
tree = parse('ug.lyx')
document = tree.getroot()
document.attrib['format']
for part in document:
print part.tag
Results in:
346
header
body
Note that among other advantages the conversion between xml will become
faster than what happens now.
Any problem
Pavel Sanda wrote:
José Matos wrote:
The next step is to guarantee that the conversion is correct and that there
are no data loss in the process.
it would be good to synchronize on this point once you start to work on it.
currently i'm aware of two other relatedr tasks running which
301 - 400 of 1040 matches
Mail list logo