headers
Joris van der Hoeven | 1 Sep 2011 11:02

Re: Question about Licenses

On Wed, Aug 31, 2011 at 10:55:52PM +0200, Sascha Manns wrote:
> Hello Mates,
> 
> i'm one of your Packager for openSUSE.
> 
> I've noticed that the following files has special licenses:
> 
> TeXmacs-1.0.7.10-src/TeXmacs/langs/natural/hyphen/hyphen.dutch
> TeXmacs-1.0.7.10-src/TeXmacs/langs/natural/hyphen/hyphen.german
> TeXmacs-1.0.7.10-src/TeXmacs/langs/natural/hyphen/hyphen.sloven
> 
> It says:
> | % General permission for non-profit usage is granted.
> | % For commercial usage contact CELEX at the above address.
> | % Copying of this file is only permitted with inclusion of
> | % this copyright notice and with these same restrictions.
> 
> So the Question is, can we use it in our Packages, or not? Otherwise we must 
> remove that files for providing a package.

Thanks for noticing this problem to us.
I replaced the files by newer versions under
the LaTeX Project Public License.

Best, --Joris
Permalink | Reply | 0 comments |
headers
Joris van der Hoeven | 1 Sep 2011 12:15

Dressing a list of working plug-ins and add documentation

Hi all,

In the upcoming version of TeXmacs, I added the possibility to
include documentation in the doc subdirectory of plug-ins
(I also reorganized the SVN file structure, so that you get
the standard documentation as a part of the src directory).

This would be a good time for a general review of the existing plug-ins,
some of which do not really seem to work anymore. I would greatly
appreciate any help on this issue. For those plug-ins which DO work,
it would be nice to include some minimal documentation with

  * A short description of the purpose of the plug-in, its authors,
    maintainers, where to get it, and how to install it
    (this info will also be published on the web site).

  * At least one example on how to use the plug-in
    (please keep the files sizes reasonably small;
    not too many images).

Notice that plug-ins which provide this information will be
mentioned in the Help -> Plug-ins menu.

Best, --Joris
Permalink | Reply | 9 comments |
headers
Joris van der Hoeven | 1 Sep 2011 13:00

Pdf marks and Re: adding pdf hyperlink support

Dear Sam,

On Tue, Jun 28, 2011 at 06:15:17PM +0100, Sam Liddicott wrote:
> I'm determined to add PDF hyperlink support to texmacs.

Thanks for your work on this issue. I was indeed surprised to
discover that various links were added to a Pdf export.

There are a few quirks though: the locus_boxes are only used
for "inactive non line-breakable markup". For instance,
hyperlinks do not work with the current implementation.

If you have some time, then this whould be the way around this:
instead of (or in addition to?) using the locus_boxes in order to
determine what should be linked to what, you should scan all subtrees
of the document tree, and determine whether there are links attached
to them. For instance, look at the 'link-active-upwards' scheme
routine (even though scanning should be fast and written in C++).
From the subtrees to which we attached links, you should next
determine the corresponding bounding boxes (or regions);
see edit_interface_rep::update_active_loci for how this works.

Another related question concerns alpha-trasparency;
I tried to add this to the last version 1.0.7.11
(enable using Debug -> Experimental -> Alpha transparency,
after which you may try to draw a graphics using alpha
transparency, or try Insert -> Presentation tag -> Greyed,
on top of some non uniform background).

However, contrary to linking info, it seems that ghostscript
(Continue reading)

Permalink | Reply | 13 comments |
headers
Sam Liddicott | 2 Sep 2011 08:56

Re: Pdf marks and Re: adding pdf hyperlink support

On 01/09/11 12:00, Joris van der Hoeven wrote:
> Dear Sam,
>
> On Tue, Jun 28, 2011 at 06:15:17PM +0100, Sam Liddicott wrote:
>> I'm determined to add PDF hyperlink support to texmacs.
> Thanks for your work on this issue. I was indeed surprised to
> discover that various links were added to a Pdf export.
>
> There are a few quirks though: the locus_boxes are only used
> for "inactive non line-breakable markup". For instance,
> hyperlinks do not work with the current implementation.
>
> If you have some time, then this whould be the way around this:
> instead of (or in addition to?) using the locus_boxes in order to
> determine what should be linked to what, you should scan all subtrees
> of the document tree, and determine whether there are links attached
> to them. For instance, look at the 'link-active-upwards' scheme
> routine (even though scanning should be fast and written in C++).
>  From the subtrees to which we attached links, you should next
> determine the corresponding bounding boxes (or regions);
> see edit_interface_rep::update_active_loci for how this works.

The way I was planning to implement this is the same way in which 
hlink's are coloured. I found the rendering which changes the 
environment to set the link colour while rendering the link and then 
restoring it. In a similar manner and location in the code I planned to 
set the link destination in the environment. This might open the way 
more generally to annotate any part of the document with PDF attributes 
or renderer attributes. I think this rendering links this way might be 
done sooner as it requires me to become acquainted with less of the code
(Continue reading)

Permalink | Reply | 5 comments |
headers
Sam Liddicott | 2 Sep 2011 09:06

Re: Dressing a list of working plug-ins and add documentation

It would be easier to participate if you use git, but this is merely a 
request not a requirement.

Right now I'm using a combination of git-svn and someone elses git tree.

I've just updated to your latest and will give things a try.

Sam

On 01/09/11 11:15, Joris van der Hoeven wrote:
> Hi all,
>
> In the upcoming version of TeXmacs, I added the possibility to
> include documentation in the doc subdirectory of plug-ins
> (I also reorganized the SVN file structure, so that you get
> the standard documentation as a part of the src directory).
>
> This would be a good time for a general review of the existing plug-ins,
> some of which do not really seem to work anymore. I would greatly
> appreciate any help on this issue. For those plug-ins which DO work,
> it would be nice to include some minimal documentation with
>
>    * A short description of the purpose of the plug-in, its authors,
>      maintainers, where to get it, and how to install it
>      (this info will also be published on the web site).
>
>    * At least one example on how to use the plug-in
>      (please keep the files sizes reasonably small;
>      not too many images).
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Sam Liddicott | 2 Sep 2011 09:13

Re: Pdf marks and Re: adding pdf hyperlink support

Questions on transparency in the pdfwrite target were recently asked. 
The response was:  "Firstly try using a more recent version of 
Ghostscript, the current version is 9.04 (recently released) and 
addresses both colour and transparency issues over older versions."

The complainant (!) tried using 9.04 and still gad some doubts over the 
colours generated, but the gs guys are open to hear of any issues and 
Ken Sharp said: "If you still think the output is 'wrong' then I suggest 
opening a bug at www.bugs.ghostscript.com. Please attach the files there 
and describe the problem as carefully as possible, including command 
lines and platform being used."

So I guess a sample postscript that demonstrates the problem would be 
welcome.

Sam

On 02/09/11 07:56, Sam Liddicott wrote:
> On 01/09/11 12:00, Joris van der Hoeven wrote:
>> Dear Sam,
>>
>> On Tue, Jun 28, 2011 at 06:15:17PM +0100, Sam Liddicott wrote:
>>> I'm determined to add PDF hyperlink support to texmacs.
>> Thanks for your work on this issue. I was indeed surprised to
>> discover that various links were added to a Pdf export.
>>
>> There are a few quirks though: the locus_boxes are only used
>> for "inactive non line-breakable markup". For instance,
>> hyperlinks do not work with the current implementation.
>>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Joris van der Hoeven | 2 Sep 2011 09:15

Re: [TeXmacs] Literate Programming Preview

I move the discussion to TeXmacs-dev.

On Fri, Sep 02, 2011 at 08:01:47AM +0100, Sam Liddicott wrote:
> I will do a plugin to add nf-chunk o the enumerate tags, and do some
> keyboard shortcuts.

Cool.

> I would like to make rendering line numbers as part of mode=prog
> rendering, with|prog-counter|... to tell it which counter to use.
> I also want to have the syntax highlighting of mode=prog to traverse
> the named chunk and any inclusions.

I guess that we really should improve the TeXmacs typesetter for this,
instead of violating the macro language. One feature which is still
missing is marginal notes. In addition, we might use two environment
variables for triggering a marginal note on every new paragraph resp.
line in a paragraph.

Best, --Joris
Permalink | Reply | 2 comments |
headers
Sam Liddicott | 2 Sep 2011 09:19

Re: [TeXmacs] Literate Programming Preview

On 02/09/11 08:15, Joris van der Hoeven wrote:
> I move the discussion to TeXmacs-dev.
>
> On Fri, Sep 02, 2011 at 08:01:47AM +0100, Sam Liddicott wrote:
>> I will do a plugin to add nf-chunk o the enumerate tags, and do some
>> keyboard shortcuts.
> Cool.
>
>> I would like to make rendering line numbers as part of mode=prog
>> rendering, with|prog-counter|... to tell it which counter to use.
>> I also want to have the syntax highlighting of mode=prog to traverse
>> the named chunk and any inclusions.
> I guess that we really should improve the TeXmacs typesetter for this,
> instead of violating the macro language.

This is true... I find it easier to beat up a simple system that learn a 
complex one... and yet I have so much trouble with list/scheme/guile 
which is a paradox.

> One feature which is still
> missing is marginal notes. In addition, we might use two environment
> variables for triggering a marginal note on every new paragraph resp.
> line in a paragraph.

Are you thinking that line numbers should be a marginal note? I would 
find this to be a waste of marginal notes, maybe the programmer wants to 
add marginal notes about the listing. What is "resp." as in "paragraph 
resp. line"?

Sam
(Continue reading)

Permalink | Reply | 1 comment |
headers
Joris van der Hoeven | 2 Sep 2011 09:25

Re: [TeXmacs] Literate Programming Preview

On Fri, Sep 02, 2011 at 08:08:40AM +0100, Sam Liddicott wrote:
> Currently the macros are very slow on long documents, and each
> keystroke can take seconds to process on documents of 100 pages.

For fast typesetting, your macros should be relatively simple and
mainly 'with' and/or 'surround' a 'document' body.
Currently, only large 'document' tags are accelerated in Typeset/Bridge.

Notice also that, even though the production of line boxes is accelerated,
the vertical superposition of all line boxes may take some time for
large documents (rather tenths of seconds though for 100 pages),
especially if you also do page breaking. Nevertheless, this part
is accelerated in the case of structured documents (e.g. 10 chunks
of code of 10 pages each).

Best, --Joris
Permalink | Reply | 0 comments |
headers
Joris van der Hoeven | 2 Sep 2011 09:28

Re: [TeXmacs] Literate Programming Preview

On Fri, Sep 02, 2011 at 08:19:04AM +0100, Sam Liddicott wrote:
> Are you thinking that line numbers should be a marginal note? I
> would find this to be a waste of marginal notes, maybe the
> programmer wants to add marginal notes about the listing.

One might specify an optional margin space for each note.

> What is "resp." as in "paragraph resp. line"?

You both want

  Line numbers for programs (paragraph based)
  Line numbers for papers (line based, as used by editors)

Best, --Joris
Permalink | Reply | 0 comments |

Gmane