Re: [NTG-context] git or svn

2013-09-27 Thread Peter Münster
On Thu, Sep 26 2013, Mica Semrick wrote:

 it could have been forked, branched, content added, pull request made.

with svn: wait for access - commit   ;)

-- 
   Peter
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] git or svn

2013-09-27 Thread Peter Münster
On Fri, Sep 27 2013, Aditya Mahajan wrote:

 The last time I tried, merging multiple version in svn is a huge pain. One of
 the advantages of DVCS is that branching and merging are easy.

I understand. Please go ahead if you need git. My preference for svn is
just my personal opinion, coming from my personal experience: people
wanted to change a well running system, using the latest and greatest
tools. In the end, after quite some efforts, there was no benefit, it
was just a bit more complicated.

I'm just lucky doing my 3 svn-commits per year, and with git I would
do git-commits.

-- 
   Peter
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] git or svn

2013-09-27 Thread Taco Hoekwater

On Sep 27, 2013, at 9:01 AM, Peter Münster pmli...@free.fr wrote:

 On Fri, Sep 27 2013, Aditya Mahajan wrote:
 
 The last time I tried, merging multiple version in svn is a huge pain. One of
 the advantages of DVCS is that branching and merging are easy.
 
 I understand. Please go ahead if you need git. My preference for svn is
 just my personal opinion, coming from my personal experience: people
 wanted to change a well running system, using the latest and greatest
 tools. In the end, after quite some efforts, there was no benefit, it
 was just a bit more complicated.

+1 from me: I have exactly the same experience personally.

 I'm just lucky doing my 3 svn-commits per year, and with git I would
 do git-commits.


+1 again.

The manual is on supelec because that is where the metapost and luatex
repositories are, and it is a subversion repo because when the project
was first added, the software system on supelec did not understand git.

The current version of Forge does support git repos, but I never switched 
since (as I wrote above) I have a small personal preference for 
subversion. So it would be possible to have a git on supelec; for that 
reason there is no need to switch to github. There may be a small
advantage to staying with supelec  as then the main project URL does not 
have to change.

OTOH, supelec's email stuff breaks easily and somewhat often.

Best wishes,
Taco

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] ConTeXt Manual Errata

2013-09-27 Thread Marco Patzer
On 2013–09–26 Peter Münster wrote:

 On Thu, Sep 26 2013, Aditya Mahajan wrote:
 
  Wouldn't it be better to move the manuals to github rather than keeping them
  on an svn server?
 
 Why?

In my opinion, for the “3 commits per year” it doesn't really matter
which version control system is being used. No particular git
feature is required for such a simple and low-traffic code base as
the manual.

For me it's more a choice of infrastructure. It is easier to
collaborate on github. It's popular, people know how to use it and
it doesn't require an invitation. Github's GUI is more friendly to
beginners not familiar with revision control systems. The simpler it
is to contribute the more likely it is for people to do so.

But, I agree, there are valid reasons to stay with supelec, the main
one being that it's already there. Still, I would support a change.
More importantly I would like to see people actually contributing.

Marco


signature.asc
Description: Digital signature
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] ConTeXt Manual Errata

2013-09-27 Thread Peter Münster
On Fri, Sep 27 2013, Marco Patzer wrote:

 More importantly I would like to see people actually contributing.

+1

And it would be no problem for me (and for other contextman members) to
apply contributed patches. Whoever wants to contribute without worrying
about the VCS can send a patch here.

-- 
   Peter
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] git or svn

2013-09-27 Thread Lars Huttar
On 9/27/2013 3:38 AM, Taco Hoekwater wrote:
 On Sep 27, 2013, at 9:01 AM, Peter Münster pmli...@free.fr wrote:

 On Fri, Sep 27 2013, Aditya Mahajan wrote:

 The last time I tried, merging multiple version in svn is a huge pain. One 
 of
 the advantages of DVCS is that branching and merging are easy.
 I understand. Please go ahead if you need git. My preference for svn is
 just my personal opinion, coming from my personal experience: people
 wanted to change a well running system, using the latest and greatest
 tools. In the end, after quite some efforts, there was no benefit, it
 was just a bit more complicated.
 +1 from me: I have exactly the same experience personally.


I'm with Taco and Peter on this one. SVN is part of my everyday
workflow; Git requires a lot more reading and fumbling. However I know
the need to be fluent with Git is becoming more and more prevalent, and
for many people it's already the easiest thing. So I wouldn't argue
against moving to Git. I'm just reporting my preference.

BTW I committed several changes to the manual yesterday, and plan to do
a fair bit more in the coming week or two. I would appreciate if someone
knowledgeable could check and make sure that I haven't said things that
are misleading or incorrect.

Lars

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] git or svn

2013-09-27 Thread Lars Huttar
On 9/26/2013 9:10 PM, Aditya Mahajan wrote:
 Github seems to be the most popular DVCS hosting site at the moment.
 For manuals, I think that Github is particularly useful because you
 can click on edit and make the change. Github automatically creates a
 fork, a new branch, and pull request for you. So the technical barrier
 to participation is low.

I would question the perception that the technical barrier to
participation on Github is low. Not long ago I tried to submit a patch
to a project on Github, improving documentation and adding features. It
took several hours (distributed over a couple of weeks) to learn how to
do all that was required. It was *not* automatic. It strongly
discouraged me from making more contributions to that project.

Maybe some major things have changed on Github since then. In any case,
I have no doubt that once you know the system, and have the
infrastructure set up, it's easy to participate. And I'm not saying that
SVN makes it easy for non-SVN users to participate. All I'm saying is
that for non-Git users, the technical barrier to participation was
substantial, last time I tried it.

Again, I'm not arguing against a move to Git. I would just like to
contribute my recent experience toward a well-informed decision process.

Lars

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] git or svn

2013-09-27 Thread Marcin Borkowski
Dnia 2013-09-27, o godz. 09:10:04
Lars Huttar lars_hut...@sil.org napisał(a):

 On 9/26/2013 9:10 PM, Aditya Mahajan wrote:
  Github seems to be the most popular DVCS hosting site at the moment.
  For manuals, I think that Github is particularly useful because you
  can click on edit and make the change. Github automatically creates
  a fork, a new branch, and pull request for you. So the technical
  barrier to participation is low.
 
 I would question the perception that the technical barrier to
 participation on Github is low. Not long ago I tried to submit a patch
 to a project on Github, improving documentation and adding features.
 It took several hours (distributed over a couple of weeks) to learn
 how to do all that was required. It was *not* automatic. It strongly
 discouraged me from making more contributions to that project.
 
 Maybe some major things have changed on Github since then. In any
 case, I have no doubt that once you know the system, and have the
 infrastructure set up, it's easy to participate. And I'm not saying
 that SVN makes it easy for non-SVN users to participate. All I'm
 saying is that for non-Git users, the technical barrier to
 participation was substantial, last time I tried it.
 
 Again, I'm not arguing against a move to Git. I would just like to
 contribute my recent experience toward a well-informed decision
 process.

Just my 3 cents.

I am not a heavy Git user (though I am quite accustomed to Mercurial
instead), and I agree that the entry point for Git is not very low.
However, it seems that nowadays, for a *new* user, learning to use SVN
is pointless (unless he joins a project where SVN is used etc.):
distributed VCSs seem to be just much better (and I heard that SVN has
its own problems, too).  So I would perceive this question as touching
a demography issue: younger people are more likely to know/use Git (and
not know SVN), older folk might know/use SVN.

Also, if this matters, Git has an excellent Emacs front-end, Magit.  I
don't know whether SVN has something similar.

 Lars

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] git or svn

2013-09-27 Thread Peter Münster
On Fri, Sep 27 2013, Marcin Borkowski wrote:

 However, it seems that nowadays, for a *new* user, learning to use SVN
 is pointless

For our use case (enhancing the documentation) that's a nonissue:
git or svn, there is nothing to learn, just pull, edit, commit.
3 lines on the project web page will show you what to do.

Of course, if you choose a complicated workflow (maintaining several
branches, test and validation cycles, commit signatures, and so on),
then git would be a good choice, and yes, then you'll have to learn it.
But please don't spend more time with the DVCS than with the improvement
of the manual... ;)

-- 
   Peter
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] git or svn

2013-09-27 Thread Hans Hagen

On 9/27/2013 3:26 PM, Marcin Borkowski wrote:


Also, if this matters, Git has an excellent Emacs front-end, Magit.  I
don't know whether SVN has something similar.


github has a nice windows backend but (as with more open source 
developments) the real nice stuff is closed ... i tried several times 
but never could install easily some git server infrastructure similar to 
github on a (linux) server so at our company we stay with svn (but i 
keep copies of the context-on-github on my machine, but only for viewing)


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] question about linespace adjustment

2013-09-27 Thread Lars Huttar
On 9/26/2013 3:47 PM, Wolfgang Schuster wrote:
 Am 25.09.2013 um 23:45 schrieb Lars Huttar lars_hut...@sil.org:

 Wolfgang, thanks for your response.

 On 9/25/2013 5:02 PM, Wolfgang Schuster wrote:
 You can’t expect from \tfa etc. to change the interlinespace because these
 commands can be used in your paragraphs to change the size of certain
 words only and in this case you don’t want a forced change of the 
 interlinespace.
 Well... \switchtobodyfont[20pt] can also be used in paragraphs to change
 the size of just a few words.
 But the above suggests that \switchtobodyfont shouldn't be used for that
 purpose, and commands like \tfc should?
 You can use \switchtobodyfont to change the size for certain parts of a text
 but it’s best to keep this to a minimum because \tfa etc. are a  lot faster.

 The reason why you don’t need \setupinterlinespace when you use
 \switchtobodyfont is that \setupinterlinespace is already called by
 \switchtobodyfont.

OK, good to know.

 Another thing which shouldn’t be forgotten is that \switchtobodyfont
 controls and changes the sizes for \tfa etc.

Can you elaborate on that?
A few days ago, Luigi wrote,

 \tfc augment the fontsize of a factor of 1.728
 It's relative to the default font size not to the current fontsize

So when he says relative to the default font size, does that mean the
same thing as relative to the current body font size? I think so. The
following example shows that the function of \tfc is relative to the
size set by \switchtobodyfont:

{\tfc tfc \tfc tfc}


{\switchtobodyfont[20pt] 20pt \tfc tfc}


{\switchtobodyfont[6pt] 6pt \tfc tfc}


Here the text after \tfc appears in three different sizes, proportional
to (and larger than) the \switchtobodyfont setting in effect. However,
the first line shows us that \tfc is *not* affected by previous effects
of \tfc. So as Luigi said, there is a distinction between the current
font size (which is affected by \tfc), and the default font size -- or
maybe it should be described as the current body font size -- which is
not affected by \tfc.
Is that correct?

So does \tfc mean set the current font size to be three steps up from
the current body font size?

Thanks. I'm contributing clarifications into the manual as I come to
understand how things are designed to work.

Lars

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] git or svn

2013-09-27 Thread Mica Semrick
Maybe we can have the best of both: https://gist.github.com/ticean/1556967 ?


On Fri, Sep 27, 2013 at 7:27 AM, Hans Hagen pra...@wxs.nl wrote:

 On 9/27/2013 3:26 PM, Marcin Borkowski wrote:

  Also, if this matters, Git has an excellent Emacs front-end, Magit.  I
 don't know whether SVN has something similar.


 github has a nice windows backend but (as with more open source
 developments) the real nice stuff is closed ... i tried several times but
 never could install easily some git server infrastructure similar to github
 on a (linux) server so at our company we stay with svn (but i keep copies
 of the context-on-github on my machine, but only for viewing)

 Hans

 --**--**-
   Hans Hagen | PRAGMA ADE
   Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
  | www.pragma-pod.nl
 --**--**-

 __**__**
 ___
 If your question is of interest to others as well, please add an entry to
 the Wiki!

 maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/**
 listinfo/ntg-context http://www.ntg.nl/mailman/listinfo/ntg-context
 webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
 archive  : 
 http://foundry.supelec.fr/**projects/contextrev/http://foundry.supelec.fr/projects/contextrev/
 wiki : http://contextgarden.net
 __**__**
 ___

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Repeat second-level registers within index

2013-09-27 Thread Hans Hagen

On 9/26/2013 12:16 PM, Philipp Gesang wrote:

···date: 2013-09-24, Tuesday···from: Thangalin···


Hi,

How do you prevent ConTeXt from hiding (collapsing?) duplicate level 2
index items?

For example:

   \startitem
 5 array \index{hedgehog+SECTION A}hedgehog
   \stopitem
   \startitem
 7 army \index{herring+SECTION A}herring
   \stopitem
   \startitem
 100 bloat \index{hippopotamuses+SECTION A}hippopotamuses
   \stopitem

The text SECTION A will only appear once in the index, right after
hedgehog. I would like it to appear once per index term, always.


Confirmed. The subentries aren’t shown if:

   - entries that share a subentry (level 2) are indexed
 consecutively, and

   - these entries are different but belong in the same register
 section (same initial letter)

Example:

 \starttext
   \placeindex

   \page

   \index{a+foo}whatever %% shows up
   \index{aa+foo}   whatever %% doesn’t
   \index{aaa+foo}  whatever %% doesn’t
   \index{+bar} whatever %% shows up
   \index{a+foo}whatever %% shows up
   \index{aa+foo}   whatever %% doesn’t

 \stoptext

If you s/bar/foo/ in the fourth invocation of \index, only the
first entry (“a”) of the register will have the subentry “foo”.
Change the initial letters of each entry and all subentries are
printed.


can you run tests with (line 695 in strc-reg):

for i=1,4 do -- max 4
if list[i] then
e[i] = list[i][1]
end
if e[i] ~= done[i] then
if e[i] and e[i] ~=  then
done[i] = e[i]
for j=i+1,4 do done[j] = false end
if n == i then
context.stopregisterentries()
context.startregisterentries(n)
else
while n  i do
n = n - 1
context.stopregisterentries()
end
while n  i do
n = n + 1
context.startregisterentries(n)
end
end
local internal  = entry.references.internal or 0
local seeparent = entry.references.seeparent or 
local processor = entry.processors and 
entry.processors[1] or 

if metadata then

context.registerentry(processor,internal,seeparent,function() 
helpers.title(e[i],metadata) end)

else -- ?

context.registerentry(processor,internal,seeindex,e[i])
end
else
done[i] = false
for j=i,4 do done[j] = false end
end
end
end

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] Repeat second-level registers within index

2013-09-27 Thread Thangalin
Hi,

I changed lines 695 in
bin/context/tex/texmf-context/tex/context/base/strc-reg.lua to the above. I
re-ran context against my test case and Philipp's example.

Actual results:

a
foo 2
*aa 2
aaa 2

*bar 2
a
foo 2
aa 2

Expected results:

a
foo 2
aa
*foo 2
*aaa
*foo 2
*
bar 2
a
foo 2
aa 2

Kindest regards.

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Repeat second-level registers within index

2013-09-27 Thread Thangalin
Thank you, Hans.

The error still seems to be present.

Out of curiosity, what does max 4 mean? Does it limit the index nesting
levels?

For my project, I require 5 nesting levels -- is that possible?

Kind regards.


strc-reg.lua
Description: Binary data
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Repeat second-level registers within index

2013-09-27 Thread Aditya Mahajan

On Fri, 27 Sep 2013, Thangalin wrote:


Hi,

I changed lines 695 in
bin/context/tex/texmf-context/tex/context/base/strc-reg.lua to the above.


Did you regenerate the format: context --make

Aditya
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


[NTG-context] Module documentation broken

2013-09-27 Thread Marco Patzer
Hi,

the module documentation is broken when it contains certain macros,
e.g. \METAPOST.

  mtxrun --script modules --process auto:meta-pag.mkiv

yields

pagesflushing realpage 1, userpage 1
pagesflushing realpage 2, userpage 1
error: .../context/tex/texmf-context/tex/context/base/node-fnt.lua:129: attempt 
to index field '?' (a boolean value)

system   tex  error on line 20 in file ../meta-pag-mkiv.ted: ? ...

Marco


signature.asc
Description: Digital signature
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] Repeat second-level registers within index

2013-09-27 Thread Thangalin
Hi,

I did not. I have since run *context --make* and the second-level registers
are working.

Thank you.
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___