On 04/05/2013 05:50 AM, Steve A wrote:
> Hi Alan,
>
> Sorry, but i'm not too interested in Scid's LaTex features.
> I know it's a nice format with a lot of  history, but it's an absolute
> devil to work with.
> If anyone makes reasonable patches, i'll be glad to include them.
>
> PS - i'm still cleaning up the docking system. It seems mostly finished :)
> As soon as i debug it on OS X, i might ready Scid vs PC 4.9, but I'm still
> fairly busy. Recent other tweaks include the ability to hide the
> gamelist buttons via right-clicking the gamelist, not starting engines
> at Docking start-up , and binding 'Space-Bar' to engine stop/start.
>
> Carlsen vs. Anand. Bring it on !
>
> S.
>
> On Fri, Apr 5, 2013 at 11:41 AM, Alan Whiteman <a.c.white...@gmail.com> wrote:
>> Hi Steveand community,
>>
>> I've been printing individual games and game collections by exporting
>> them to Latex. However, there seems to be two essential components
>> missing that I believewould enhance the printouts: For game collections,
>> away to number each game; and for each ply of moves, thechess engine's
>> evaluation.
>>
>> When evaluating one's own games with Stockfish (or some other engine,)
>> this excellent feature wouldhelpto evaluate the estimated positional
>> value of the move. And it would be even more helpful when combined
>> withinserted variations.
>>
>> Example:
>>
>> *Game 1*
>> Myaskov I
>> Alekhine, Alexander
>>
>> 19031 - 0  D43
>>
>> 1 . d4 d5 [0.00]
>> 2. c4  e6          [+0.15]
>> 3. Nc3  Nf6     [+0.18]
>> 4. Nf3  c6        [+0.25]
>> 5. Bg5  Be7    [+0.20]
>> 6. e3dxc4     [-0.12]
>> 7. e4 h6         [-0.18]
>> 8 Bxf6  Bxf6 [-0.25]
>>    ...
>>
>> I'm not a programmer or a LaTeX practitioner, but I've tried using the
>> following code to enumerate the games. The problem is that each game
>> will need to be wrapped with the'enumerate' environment.
>>
>> \begin{enumerate}
>> \item
>>
>> {\bf
>> $\circ$ Myaskov, I\\
>> $\bullet$ Alekhine, Alexander\\
>>     \\
>> 1903  \hfill 1-0 \hfill D43\\
>> }
>> \begin{chess}{\bf
>> 1.d4 d5 2.c4 e6 3.Nc3 Nf6 4.Nf3 c6 5.Bg5 Be7 6.e3 dxc4 7.e4 h6 8.Bxf6 Bxf6
>> 9.e5 Be7 10.Bxc4 Nd7 11.O-O Nb6 12.Bd3 c5 13.dxc5 Bxc5 14.Ne4 Be7 15.Rc1
>> Bd7 16.Qe2 Bc6 17.Rfd1 Nd5 18.Bb1 Qb6 19.b3 Nf4 20.Qb2 Bxe4 21.Bxe4 Rd8
>> }\end{chess}
>> {\bf 1-0}
>>
>> \end{enumerate}
>>
>> Hopefully I was clear enough, your help is greatly appreciated.
>>
>> ------------------------------------------------------------------------------
>> Minimize network downtime and maximize team effectiveness.
>> Reduce network management and security costs.Learn how to hire
>> the most talented Cisco Certified professionals. Visit the
>> Employer Resources Portal
>> http://www.cisco.com/web/learning/employer_resources/index.html
>> _______________________________________________
>> Scidvspc-users mailing list
>> scidvspc-us...@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/scidvspc-users


Hi Steve,

I understand that LaTex is not a priority right now since you are 
getting this whole docking issue squared out. Let's just leave it as a 
nice-to-have feature request for future reference.

I hope you don't mind if I post this to the other sicd list- in case 
there are Latex enthusiasts there as well.



------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users

Reply via email to