On Tue, Jul 22 2014, Alan BRASLAU wrote:
> Which gives "acceptable" alternative-spellings, and says that the
> circumflex is not mandatory. It does not suggest that août is
> incorrect. Furthermore, août remains the reference.
All right, thanks for the informations.
>> (if "aout" is wrong, then
On Tue, Jul 22 2014, Alan BRASLAU wrote:
> Please maintain "août" and do not cede to any pseudo-reforms,
Hi Alan,
Why "pseudo-reform"?
> or use wikipedia as an authoritative reference...
Sorry, this is probably more authoritative:
http://www.academie-francaise.fr/sites/academie-francaise.fr/
Because of
http://fr.wikipedia.org/wiki/Rectifications_orthographiques_du_français_en_1990
:
--- lang-txt.lua~ 2014-06-04 22:39:45.0 +0200
+++ lang-txt.lua2014-07-22 16:44:02.190189134 +0200
@@ -607,7 +607,7 @@
en="August",
es="agosto",
fi="elokuu",
-fr="a
On Sun, Apr 07 2013, Aditya Mahajan wrote:
> If the typescripts are needed for MkII, they can still be part of the
> typescript module by Wolfgang.
Of course. But I don't have URW Garamond installed on my system, so I
can't test if it still works with latest mkii.
(Now I use GaramondPremrPro (OTF
On Sun, Apr 07 2013, Aditya Mahajan wrote:
> - URW Garamond support (by Peter Münster; is this still needed?
Hi Aditya,
I don't think so. It's very old and only for mkii.
--
Peter
___
dev-context mailing list
dev-contex
On Sat, Jan 05 2013, Hans Hagen wrote:
> I don't like that figures.current reference there;
I don't know any other method...
> also, the image isn't always scanned yet so the original dimensions
> are not known.
Doesn't matter for this use-case: I just want to make sure, that a new
conversion
Hi Hans,
Could you please add the following little patch (or something similar)
to grph-inc.lua:
--- grph-inc.lua~ 2013-01-03 23:32:37.297732874 +0100
+++ grph-inc.lua 2013-01-03 23:42:18.237157620 +0100
@@ -571,6 +571,9 @@
if resolution and resolution ~= "" then -- the order
Hi,
Does the value 65436 have a special meaning, or is it a type?
-*- mode: grep; default-directory:
"/opt/context/tex/texmf-context/tex/context/base/" -*-
Grep started at Thu Jan 3 23:59:25
grep -nH -e 65436 *
font-age.lua:3268:["wakatakanahalfwidth"]=65436,
m-chart.lua:39:width
Hello Hans,
What do you think about these patches?
--
Peter
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context
On Fri, Sep 14 2012, Aditya Mahajan wrote:
> Hans already added a generic function \setemeasure to syst-aux, that can be
> used here.
I've tried, but without success... :(
TIA for any further help,
--
Peter
___
dev-context mailing list
dev-
On Fri, Sep 14 2012, Aditya Mahajan wrote:
> Hans already added a generic function \setemeasure to syst-aux, that can be
> used here.
Thanks, I'll take a look.
> Note that a simple \doifnotemptyvalue is not enough. I can pass values
> like 'fit', 'max', etc to height and width keys, so you must
On Fri, Sep 07 2012, Aditya Mahajan wrote:
>> + \edef\current_width{\externalfigureparameter\c!width}%
>> + \edef\current_height{\externalfigureparameter\c!height}%
>> + \def\nocrap##1{\doifnotemptyvalue{##1}{%
>> + \the\dimexpr\csname##1\endcsname\relax}}%
>
> It is better to use a mo
Hi Hans,
Could you please add these 2 patches (or something similar), because the
grph-downsample module¹ would work much better then:
1.) To get the width and the height into the name of the file,
because when the figure dimensions change, there must be a new
conversion:
--8<---
Hello,
The upload seems to be broken:
Upload warning
The upload directory (public) is not writable by the webserver.
--
Peter
___
If your question is of interest to others as well, please
On Sun, Sep 12 2010, Sietse Brouwer wrote:
> Ah, thank you. I've made a checkout and searched the project for
> instances of '\inmarge'; there's only one, and that one would end up
> in the index. Here's the patch:
Oh, I'd supposed, that you would rather check the pdf... ;)
Cheers, Peter
--
Co
On Thu, Sep 09 2010, Sietse Brouwer wrote:
> The English-language versions of
> "ConTeXt, the manual"
> (http://www.pragma-ade.com/general/manuals/cont-eni.pdf)
Hello Sietse,
This file won't be updated (to be confirmed by Hans perhaps...).
Corrections will go directly to the new revision of the
On Sun, Jul 18 2010, Hans Hagen wrote:
>> then they could easily all be merged into a single command table
>> during loading or even via 'cat'.
>
> I'd rather go for this (see lfg file for examples):
>
> return {
> name = "placefloat",
> version = "1.00",
> comment = "Insert a floating
On Sun, Jul 18 2010, Taco Hoekwater wrote:
> variants = { -- just an example
> { "filename_arg" },
> { "label_arg", "filename_arg" },
> { "label_arg", "filename_arg", "settings_arg" },
> { "filename_arg", "parent_arg" },
Now I see the big benefit!
In
On Sun, Jul 18 2010, Mojca Miklavec wrote:
> I didn't understand the last paragraph, but while it's not a problem
> for a human to determine where to inherit from, it might be a problem
> for a computer if you want to print the complete command.
There is no problem for a computer, it's just jumpi
On Sun, Jul 18 2010, Peter Münster wrote:
> > - If all the three arguments are optional, it's a bit difficult to
> > tell what combination of arguments is allowed, so it might make sense
> > to be a bit more verbose in that (to tell somehow that for example
> > onl
On Sun, Jul 18 2010, Taco Hoekwater wrote:
> arguments = {
> ["label_arg"] = {
> type = label,
> },
> ["filename_arg"] = {
> type = file,
> },
> ["settings_arg"] = {
> type = settings,
>
On Sat, Jul 17 2010, Mojca Miklavec wrote:
> A few random comments from externalfigure:
> - Despite the fact that the command name is known from filename,
> wouldn't it be nice to have externalfigure string defined somewhere?
Ok, see response to Taco.
> - It is not really needed, but it helps w
On Sun, Jul 18 2010, Taco Hoekwater wrote:
> If you start your files like this:
>
> command = command or {}
> command['placefloat'] = {
> comment = "Insert a floating element.",
> ...
> }
>
> then they could easily all be merged into a single command table
> during loading or even vi
On Sat, Jul 17 2010, Hans Hagen wrote:
> - props -> properties (or whatever, but no shortcuts)
No more needed.
> - args -> arguments
Done.
> - [=[ looks rather bad but anyhow, examples should probably not be done
> this way (examples can be go into tex files)
Ok, why not!
Peter
--
Conta
On Sat, Jul 17 2010, luigi scarso wrote:
> Why don't put them into a table as is in
> http://www.lua.org/pil/10.1.html
Ok, now one file defines exactly one "command" table.
I added also other minor enhancements.
Cheers, Peter
--
Contact information: http://pmrb.free.fr/contact/
_
On Sat, Jul 17 2010, luigi scarso wrote:
> Why don't put them into a table as is in
> http://www.lua.org/pil/10.1.html
> For exampl e placefloat.lua should be
> placefloat ={
> props = {
> [...]
Because I like to avoid redundancy.
It's easy to do things like this automatically:
local placefloat
Hello,
Here some new ideas:
http://pmrb.free.fr/tmp/context-commands/
All feedback is welcome!
Cheers, Peter
--
Contact information: http://pmrb.free.fr/contact/
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/de
On Fri, Jul 02 2010, Taco Hoekwater wrote:
> I think this will be a wasted effort. I predict that any future
> version of context that will be able to do syntax checking is going
> to be based on lua for the verification process, not tex macros.
That's even better, because I'm more comfortable w
On Fri, Jul 02 2010, Wolfgang Schuster wrote:
> The idea is not bad but who is going to do this? Hans implemented
> in mkiv the function to check assignments list of valid keys but
> this function isn't used because nobody writes the necessary lists
> which contexts requires to do these checks and
On Wed, Jun 16 2010, Wolfgang Schuster wrote:
>
> i plan to update cont-en.xml with changes in mkiv (new keys and commands)
Hello Wolfgang,
Since Hans said "documentation about tex can best be done in tex", I've put
my ideas into some files here:
http://pmrb.free.fr/tmp/context-commands/
What
On Tue, May 11 2010, Taco Hoekwater wrote:
>> It also makes editing the wiki much easier (using also wiki tables
>> instead of HTML tables etc.)
>
> This is definitely true, but for the export there is a simple solution:
> export as xml, feed the output through Tidy, then process with mkiv's
> nat
On Mon, May 10 2010, Taco Hoekwater wrote:
> I would much prefer working on the wiki, then export to .tex with
> a script. Having two sources for what is essentially the same
> information is asking for trouble, imo.
Hello Taco,
There is not enough structure on the wiki. I imagine a script that
On Sun, May 09 2010, Hans Hagen wrote:
> So, how about more extensive info. As each command has a unique reference,
> the best approach is to have a separate file for each such entry. I suppose
> that this can be generated from the wiki.
Hello Hans,
Yes, I also like one file per command, it's
On Thu, May 06 2010, Idris Samawi Hamid ادريس سماوي حامد wrote:
> I'm interested in an audit of all current mid-to-high-level mkiv commands,
> including experimental or undocumented ones. I'm trying to come up with, as
> much as possible, a set of context commands which is
>
> mutually exclusiv
34 matches
Mail list logo
