Ulrich Dirr a écrit :
> Hi,
>
> On Wednesday, March 26, 2008 7:34 AM Alexander Wagner wrote:
>
>> > which tex system are you using? You should also use the
>> > most recent packages. I would strongly recommend using
>> > skak with chessfs/chessboard or texmate. There are several
>> > documents which are explaining everything very detailed.
>>
>> I'd actually NOT suggest to use really the latest and
>> greatest. Instead I'd have a look at the TeXLive version
>> delivered with Debian Stable which would be a TeXLive 2005
>> and base it on the package features there. One can safely
>> consider that every other major distribution will offer this
>> standard (at the least). At max I'd take a look at package revisions
>> from TeXlive 2007.
>>
>
> TeXLive 2005 would be definitely the wrong distribution as skak,
> chessfs/chessboard and texmate2 got serious improvements after this
> release. TeXLive 2007 is o.k.
>
>
>> IMHO it would be a failure to require a Scid user to go to
>> CTAN, crawl through the packages, form which he does
>> (probably) not understand a thing, and set up a texmf-local
>> for usage with his chess software. IMHO it would also be a
>> design failure in Scid to have Scid do this setup or deliver
>> the packages with the distribution, as Scis is a chess
>> database, nothing more, just that and for this it is great
>> stuff. I'd even prefer to drop some minor features...
>>
>
> I don't understand this. Why should one export data from SCID to LaTeX
> when you don't know what LaTeX is and how to handle this software?
>
> But never mind. I was just proposing how you can get the best output ...
> Much more important would be how we can configure scid to write the code
> we want. I'm thinking of the way
> mainline/variations/subvariation/comments etc. are output. A config file
> which scid reads in with a key/value syntax would be great, e.g.,
> % latex_output.cfg
> begin mainline = '\n\n\\mainline{'
> end mainline = '}\n\n'
> begin variation = '\\variation{'
> end variation = '}'
> ...
> begin text comment = '...'
> end text comment = '...'
> ...
> $14 = '\\wbetter'
> $15 = '\\bbetter'
> ...
> Then everybody could get what (s)he wants, and it would be easily
> expandable to other output formats like html, xml, etc.
>
> Pascal what do you think about this approach?
>
I have no valuable advice in that field : I never really used LaTeX, and
I have no interest in it even if LaTeX produces great documents.
So, I have no problem in enhancing this part of Scid, but I will not be
of any help. Concerning HTML, the output is ok like that for me, and I
would consider XML as an output format only with a baionet on my back.
Pascal
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Scid-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/scid-users
