2009-11-26 18:43:34, Benoit St-Pierre:
> A white move number indication is formed from the integer giving the
> fullmove number with a single period character appended.
>
> A black move number indication is formed from the integer giving the
> fullmove number with three period characters appended.
This part of the sentence is even more interesting :
> "zero or more period characters following the digit sequence that gives the
> move number"
>
>
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
A white move number indication is formed from the integer giving the
fullmove number with a single period character appended.
A black move number indication is formed from the integer giving the
fullmove number with three period characters appended.
>
This paragraph is interesting :
"PGN import format move number indications may have zero or more period
characters following the digit sequence that gives the move number; one or
more white space characters may appear between the digit sequence and the
period(s)."
Pascal
2009/11/26 John Wordswort
2009/11/26 Michal Rudolf
> 2009-11-26 13:34:34, Pascal Georges:
>
> > What I see in PGN standard is this example :
> > "And then after 1. ... c5"
> > which Scid conforms to. Could you quote the PGN standard extract that
> > makes you think the opposite ?
>
> 8.2.2
> There are two export format mo
In relation to the question of dots after the move number, perhaps
this is relevant:
http://www.saremba.de/chessgml/standards/pgn/pgn-complete.htm
Section 8.2.2.2: Export format move number indications
However, I do not know if that site is the officially recognised
standard for PGN - or even i
2009-11-26 13:34:34, Pascal Georges:
> 2009/11/26, Michal Rudolf :
> > 2009-11-26 11:29:50, Pascal Georges:
> >> Options -> moves -> Add spaces after moves number.
> >
> > I wasn't talking about spaces, but about spurious dot.
> >
> > Scid uses: 37[dot][space][dot][dot][dot][space]Qc7
> >
> > Inste
2009-11-26 13:34:34, Pascal Georges:
> What I see in PGN standard is this example :
> "And then after 1. ... c5"
> which Scid conforms to. Could you quote the PGN standard extract that
> makes you think the opposite ?
8.2.2
There are two export format move number indication formats, one for use
2009/11/26, Michal Rudolf :
> 2009-11-26 11:29:50, Pascal Georges:
>> Options -> moves -> Add spaces after moves number.
> I wasn't talking about spaces, but about spurious dot.
>
> Scid uses: 37[dot][space][dot][dot][dot][space]Qc7
>
> Instead, PGN standard, if I understand it correctly, recommend
2009-11-26 11:29:50, Pascal Georges:
> Options -> moves -> Add spaces after moves number.
I wasn't talking about spaces, but about spurious dot.
Scid uses: 37[dot][space][dot][dot][dot][space]Qc7
Instead, PGN standard, if I understand it correctly, recommends:
37[dot][dot][dot][space]Qc7
So, it
Options -> moves -> Add spaces after moves number.
Pascal
2009/11/26, Michal Rudolf :
> I noticed that Scid saves starting black move in the variation in PGN as:
> 17. ... Qc7
>
> Isn't
> 17... Qc7
> a standard?
>
> --
> Michal Rudolf
>
> --
I noticed that Scid saves starting black move in the variation in PGN as:
17. ... Qc7
Isn't
17... Qc7
a standard?
--
Michal Rudolf
--
Let Crystal Reports handle the reporting - Free Crystal Reports 200
12 matches
Mail list logo
