El Tue, 30 Mar 2010 09:54:51 -0400
rgheck escribió:
Thanks for sending the license statement. I've added you to the credits.
I've also committed part of this patch
I have decided that future versions of LyXBlogger will run as a python module
instead of as an executable script. Here is a patch
>>
> >> I have decided that future versions of LyXBlogger will run as a python
> >> module instead of as an executable script. Here is a patch that changes
> >> lib/configure.py to look only for the modular installation.
> >>
> > Richard,
> >
> > LyXBlogger 0.35 has been released, which mu
On 04/16/2010 01:13 PM, Jack Desert wrote:
El Fri, 9 Apr 2010 20:16:38 -0500
Jack Desert escribió:
El Tue, 30 Mar 2010 09:54:51 -0400
rgheck escribió:
Thanks for sending the license statement. I've added you to the credits.
I've also committed part of this patch
I have dec
El Fri, 9 Apr 2010 20:16:38 -0500
Jack Desert escribió:
> El Tue, 30 Mar 2010 09:54:51 -0400
> rgheck escribió:
> > Thanks for sending the license statement. I've added you to the credits.
> > I've also committed part of this patch
>
>
> I have decided that future versions of LyXBlogger will r
El Tue, 30 Mar 2010 09:54:51 -0400
rgheck escribió:
> Thanks for sending the license statement. I've added you to the credits.
> I've also committed part of this patch
I have decided that future versions of LyXBlogger will run as a python module
instead of as an executable script. Here is a pa
On 04/05/2010 06:37 PM, Jack Desert wrote:
Good idea. It'll output something like:
where the content is determined by the PACKAGE_STRING macro in config.h
and so can change. I assume it will always begin "LyX", though.
rh
Sounds good. Let me know when it's finalized and I'll add it
> Good idea. It'll output something like:
>
> where the content is determined by the PACKAGE_STRING macro in config.h
> and so can change. I assume it will always begin "LyX", though.
>
> rh
>
Sounds good. Let me know when it's finalized and I'll add it to LyXBlogger.
-Jack
--
On 04/05/2010 05:14 PM, Jack Desert wrote:
Would you consider adding a META tag to the LyXHTML output? That will make it
more predictable to tell which xhtml format is being used. Some examples from
other converters:
Good idea. It'll output something like:
where the content is determ
El Sat, 27 Mar 2010 18:07:04 -0500
Jack Desert escribió:
> El Sat, 27 Mar 2010 18:03:45 -0400
> rgheck escribió:
> > On 03/27/2010 03:46 PM, Jack Desert wrote:
> > >
> > > If eLyXer is installed, it also adds:
> > > \converter html blog "lyxblogger $$i" ""
> > >
> > >
>
On 04/02/2010 04:51 AM, Jürgen Spitzmüller wrote:
rgheck wrote:
On 03/30/2010 04:15 PM, Jack Desert wrote:
Actually, the first issue is that, especially since 2.0 will (hopefully)
let the user choose conversion paths, etc, we can go ahead and install
both the xhtml->blog and html->blo
rgheck wrote:
> On 03/30/2010 04:15 PM, Jack Desert wrote:
> >> Actually, the first issue is that, especially since 2.0 will (hopefully)
> >> let the user choose conversion paths, etc, we can go ahead and install
> >> both the xhtml->blog and html->blog converters. This is particularly
> >> importa
On 03/30/2010 04:15 PM, Jack Desert wrote:
Actually, the first issue is that, especially since 2.0 will (hopefully)
let the user choose conversion paths, etc, we can go ahead and install
both the xhtml->blog and html->blog converters. This is particularly
important in 2.0, it seems to me, since
> Thanks for sending the license statement. I've added you to the credits.
Excellent.
> Actually, the first issue is that, especially since 2.0 will (hopefully)
> let the user choose conversion paths, etc, we can go ahead and install
> both the xhtml->blog and html->blog converters. This is p
Thanks for sending the license statement. I've added you to the credits.
I've also committed part of this patch, but as I was about to commit the
whole thing another issue occurred to me. Sorry!
Actually, the first issue is that, especially since 2.0 will (hopefully)
let the user choose conv
On 03/28/2010 08:52 PM, Jack Desert wrote:
LyxBlogger is specifically set up to parse the LyXHTML and eLyXer formats. Some
features may turn out strange using TtH, Hevea, or latex2html, simply because
the regular expressions may not find what they're looking for.
So yes, let's leave the ht
> LyxBlogger is specifically set up to parse the LyXHTML and eLyXer formats.
> Some features may turn out strange using TtH, Hevea, or latex2html, simply
> because the regular expressions may not find what they're looking for.
>
> So yes, let's leave the html -> blog converter inside the "if" b
El Sat, 27 Mar 2010 18:03:45 -0400
rgheck escribió:
> On 03/27/2010 03:46 PM, Jack Desert wrote:
> >
> > If eLyXer is installed, it also adds:
> > \converter html blog "lyxblogger $$i" ""
> >
> >
> You can allow it to add this even if elyxer isn't installed. Or is there
On 03/27/2010 03:46 PM, Jack Desert wrote:
If eLyXer is installed, it also adds:
\converter html blog "lyxblogger $$i" ""
You can allow it to add this even if elyxer isn't installed. Or is there
some reason we want to make sure that lyxblogger only runs on elyxer's
> So what I'd suggest is adding the LyX blogger format and the two
> converters. By default, the LyXHTML one would be chosen, since that will
> be a shorter path. But, as I said, both may be available, if we can
> finish the patch to which I alluded.
>
> rh
>
Sounds reasonable. Here is a new
On 03/25/2010 05:59 PM, Jack Desert wrote:
I have created a patch that automatically sets up
LyxBlogger file formats and converter definitions for
both of the supported input types: LyXHTML and eLyXer.
For the LyXHTML format, it adds:
\converter xhtml xblog "lyxblogger $$i"
I have created a patch that automatically sets up
LyxBlogger file formats and converter definitions for
both of the supported input types: LyXHTML and eLyXer.
For the LyXHTML format, it adds:
\converter xhtml xblog "lyxblogger $$i" ""
\Formatxblog blog "Ly
21 matches
Mail list logo
