Answers.Body: <p>You seem to want the notation to be as efficient as possible, disregarding ease of use. Let's take this to extremes:</p>
  <ul>
  <li>If White only has a single move or capture that ends on c4, then instead of Bc4 or Bxc4 should we just write c4?</li>
  <li>If White only has a single legal Rook move, then instead of Re5 should we just write R?</li>
  <li>If White only has a single legal move, then...what? Just notate it as &quot;&quot; ?</li>
  </ul>
  <p>The conventions in use are a compromise between efficiency and ease of use. And they work very well.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-14T08:10:49.390Z
Answers.Text: It seems to me more that OP is looking for consistency than efficiency. The normal situation is that you indicate the type of piece moved (by omission, if it's a pawn), whether or not there is a capture, and the destination square, with information about the starting square if necessary to disambiguate. Except for pawn captures.
Answers.UserDisplayName: Especially Lime
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-14T08:23:22.640Z
Answers.Text: The difference between your examples and the situation of pawn capture is that `xd5` contains more or less the same information as `exd5`, except that you may have to look at the board to see where the pawn was. But even without looking at the board, you kinda know what's going on. In your other examples, you don't. We notate captures, checks, mates, en passants, etc. because this is all helpful for getting an overview of the game using only the notation. But with `xe5`, you wouldn't really lose much of this information.
Answers.UserDisplayName: Gaussler
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-15T21:13:27.333Z
Answers.Text: @Gaussler: Situations where two pawns would both be capable of performing a capture are pretty common.  Indeed, if Black moves a pawn from d7 to d5 when White has pawns on c5, c6, e5, and e6, there could be *four* white pawns poised to capture the black pawn on the next move (two of them capturing directly on d5, and two capturing in passing on d6),
Answers.UserDisplayName: supercat
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-15T22:45:23.693Z
Answers.Text: Some friends and I actually at some point had fun in trying to write down games in this kind of notation. Mathematically you could define it as something like "a shortest substring of the move's algebraic notation that isn't a substring of any other legal move's algebraic notation". Not useful but was certainly a fun exercise. The best part of it was being able to often write the game-ending move as just a #.
Answers.UserDisplayName: JiK
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-15T22:47:28.343Z
Answers.Text: Although now that I think of it, my definition must be off because 1.c3 would not be possible to write down with that rule. Perhaps we had another definition.
Answers.UserDisplayName: JiK
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-16T12:08:50.297Z
Answers.Text: @JiK Fool’s mate looks good in this notation: 1. 2. 3. 4. #
Answers.UserDisplayName: Peter LeFanu Lumsdaine
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-13T21:57:38.767Z
Answers.LastActivityDate: 2022-12-13T21:57:38.767Z
Answers.UserDisplayName: TonyK
Answers.Body: <p>Imagine a situation where there is also a white pawn on <code>c4</code>, for example <code>1. e4 d5 2. c4 e6 3.xd5</code>. You would have no way of knowing which pawn took on <code>d5</code>, was it the one on <code>e4</code> or the one on <code>c4</code>.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-13T11:05:26.970Z
Answers.Text: True, but that same issue occurs when any other pair of pieces of the same kind can capture the same piece. In that case, and only then, we notate the file, or rank, or both. But with pawns, we do it no matter what. Why?
Answers.UserDisplayName: Gaussler
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-14T10:14:27.897Z
Answers.Text: @Gaussler Your comment here should be part of the question to clarify things for other people! :D
Answers.UserDisplayName: justhalf
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-13T11:01:22.387Z
Answers.LastActivityDate: 2022-12-13T11:01:22.387Z
Answers.UserDisplayName: dzi
Answers.Body: <p>I'd suggest a different reason: to make it sound natural.</p>
  <p>How would you pronounce <code>Nxe5</code>? I would say &quot;knight takes e5&quot;. In that case, the putative pawn move &quot;takes d5&quot; would not sound natural, because it has a verb with no subject.</p>
  <p>Once you decide to add a &quot;subject&quot;, you may as well do so in a way that gives extra information, since this may be useful. So rather than &quot;pawn takes d5&quot;, it makes sense to say e.g. &quot;e takes d5&quot;.</p>
  <p>There is no grammatical reason to add this information to other captures (which already have a subject) or normal moves (which have no verb).</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-14T08:51:30.510Z
Answers.LastActivityDate: 2022-12-14T08:56:42.017Z
Answers.LastEditDate: 2022-12-14T08:56:42.017Z
Answers.UserDisplayName: Especially Lime
Answers.Body: <blockquote>
  <p>Why not just <code>2. xd5</code>?</p>
  </blockquote>
  <p>Because we always indicate the piece being moved. The notation <code>2. xd5</code> doesn't tell us which piece is doing the capturing. We have to work that out for ourselves. We don't need to write <code>1. e2-e4</code>, although we can, because <code>1. e4</code> tells us the e pawn is the one being moved.</p>
  <p>For instance, in Petrov's Defence we don't write <code>1. e4 e5 2. Nf3 Nf6 3. xe5</code>. Instead we indicate the piece being moved by <code>3. Nxe5</code>.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-13T11:17:38.723Z
Answers.Text: True, but the usual convention is that “nothing” means “pawn”. If I move the knight to `d5`, I write `Nd5`. But if I move a pawn there, I write simply `d5`. Applying the same logic to capturing, `Nxe4` would mean that the knight captures whatever piece is at `e4`, whereas `xe4` would mean that a pawn does the job.
Answers.UserDisplayName: Gaussler
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-13T20:24:57.433Z
Answers.Text: @Gaussler: There is never more than one pawn that can move to a particular location without capturing.  If one knew nothing about what was on the board, the notation "e4" could mean either "move a pawn directly from e2 to e4", "move the first pawn in rank e from e3 to e4", or "move the second pawn in rank e (which had previously been in rank d or f) to e4", but the board position would make it obvious.
Answers.UserDisplayName: supercat
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-14T11:39:02.470Z
Answers.Text: This answer does make sense. The notation always contains a letter which describes _something_ about the piece being moved—either the piece type or the file, sometimes both. For a simple pawn move like "e4," the "e" effectively specifies both the starting file and the ending file, since pawns stay on the same file when they're not capturing.
Answers.UserDisplayName: Sophie Swett
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-14T22:43:24.267Z
Answers.Text: What happens is that there are many pawns but only a pair of the other pieces.  So, other pieces can be named by their type, which is usually enough to identify them, but the pawns are better named by their file.  "d5" means "pawn d moves to row 5".  "exd5" says "pawn e captures d5".
Answers.UserDisplayName: Florian F
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-13T11:13:14.507Z
Answers.LastActivityDate: 2022-12-13T11:54:13.173Z
Answers.LastEditDate: 2022-12-13T11:54:13.173Z
Answers.UserDisplayName: Brian Towers
Answers.Body: <p>Just realized one other good reason: When using this notation, it’s easier to get an overview of the pawn skeleton of the field solely from looking at the algebraic notation. For instance, to find out where the <code>e</code>-pawn is, you can look for the move starting with an <code>e</code>. That would be <code>e4</code> in this case. Next, you find the next one, which is <code>exd5</code>. Then you make a mental note that the <code>e</code>-pawn has moved to the <code>f</code>-file. Now you can keep following it as it advances along this file, until it maybe changes file again. And so on.</p>
  <p>It doesn’t offer much help in figuring out which pawns have been captured, but at least it helps.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-14T12:28:57.577Z
Answers.LastActivityDate: 2022-12-14T12:28:57.577Z
Answers.UserDisplayName: Gaussler
Answers.Body: <p>There is no real reason, it's not technically necessary.</p>
  <p>Equally, you don't generally have to write the 'x'. Knowing where the piece is going is enough to know that it's a capture.</p>
  <p>People must have thought this notation hit the sweet spot between maximum terseness and readability.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-13T11:52:59.020Z
Answers.Text: You’re right. Technically, you don’t have to play chess either. It’s not the most cost-beneficial way to satisfy your need for nutrition and survive. But we do it anyway.
Answers.UserDisplayName: Gaussler
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-14T00:54:29.730Z
Answers.Text: It seems common to just say "e-d" or "e takes".  Just not to write it.
Answers.UserDisplayName: Edward
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-14T15:14:24.907Z
Answers.Text: It might also help people check to see if they are still synced correctly with the game they are trying to read from the record.  I know nothing about chess notation, however.
Answers.UserDisplayName: Mark Rogers
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-12-13T11:48:52.053Z
Answers.LastActivityDate: 2022-12-13T11:48:52.053Z
Answers.UserDisplayName: RemcoGerlich
Body: <p>As we all know, in algebraic notation, we usually suppress the notation for pawns. That is, unless they are capturing something. Then, for some reason, we must notate the file of that pawn. For all other moves, you only need to notate the file (or rank, or both) if multiple pieces of the same kind could move to the field in question, so that this extra information is necessary to avoid ambiguities.</p>
  <p>For instance, the Scandinavian defense usually goes something like <code>1. e4 d5 2. exd5</code>. Why not just <code>2. xd5</code>?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-12-14T13:25:39.877Z
Comments.Text: These are already shortcuts for `1. e2-e4 d7-d5 2. e4xd5` It is just a matter of convention or taste how much *redundance* you are willing to live with
Comments.UserDisplayName: Hagen von Eitzen
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-12-14T13:40:53.370Z
Comments.Text: There is already a well-established abbreviation for that move: `ed`. And it's shorter than `xd5`!
Comments.UserDisplayName: TonyK
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-12-16T02:24:45.147Z
Comments.Text: Technically, you could describe that particular move as `2. x` and it's still unambiguous... but most shorthands have limitations. In this case if there were any capture in the position for White besides e4xd5, this would not work. `2. ed` works so long as no other White pawn on the e-file may capture into the d-file. '2. xd5' works only so long as no White c-pawn can take on d5. '2. exd5`, however, is always sufficient to describe e4xd5.
Comments.UserDisplayName: user45266
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-12-16T02:24:59.177Z
Comments.Text: Some of the current chess notation seems to be truly redundant, though - chess could be transcribed just fine without the x for captures, the + symbol for checks, 0-0 and 0-0-0 for castling, any of the various en passant notations, or even the # for checkmates (agreed draws, timeouts and resignations still need to be recorded though).
Comments.UserDisplayName: user45266
Tags: <pawns><notation>
Title: Why do I need to notate the file when capturing with a pawn?
ThreadText: # Why do I need to notate the file when capturing with a pawn?
  
  (Asked by: username_0 on 2022-12-13)
  
  As we all know, in algebraic notation, we usually suppress the notation for pawns. That is, unless they are capturing something. Then, for some reason, we must notate the file of that pawn. For all other moves, you only need to notate the file (or rank, or both) if multiple pieces of the same kind could move to the field in question, so that this extra information is necessary to avoid ambiguities.
  
  For instance, the Scandinavian defense usually goes something like `1. e4 d5 2. exd5`. Why not just `2. xd5`?
  
  **Tags:** pawns, notation
  
  > **Comments:**
  > **username_1**: These are already shortcuts for `1. e2-e4 d7-d5 2. e4xd5` It is just a matter of convention or taste how much *redundance* you are willing to live with  
  > **username_2**: There is already a well-established abbreviation for that move: `ed`. And it's shorter than `xd5`!  
  > **username_3**: Technically, you could describe that particular move as `2. x` and it's still unambiguous... but most shorthands have limitations. In this case if there were any capture in the position for White besides e4xd5, this would not work. `2. ed` works so long as no other White pawn on the e-file may capture into the d-file. '2. xd5' works only so long as no White c-pawn can take on d5. '2. exd5`, however, is always sufficient to describe e4xd5.  
  > **username_3**: Some of the current chess notation seems to be truly redundant, though - chess could be transcribed just fine without the x for captures, the + symbol for checks, 0-0 and 0-0-0 for castling, any of the various en passant notations, or even the # for checkmates (agreed draws, timeouts and resignations still need to be recorded though).  
  
  ---
  
  ## 6 answers
  
  ### Answer by username_13 on 2022-12-13. Score: 17 | Accepted answer
  
  There is no real reason, it's not technically necessary.
  
  Equally, you don't generally have to write the 'x'. Knowing where the piece is going is enough to know that it's a capture.
  
  People must have thought this notation hit the sweet spot between maximum terseness and readability.
  
  > **Comments:**
  > **username_0**: You’re right. Technically, you don’t have to play chess either. It’s not the most cost-beneficial way to satisfy your need for nutrition and survive. But we do it anyway.  
  > **username_14**: It seems common to just say "e-d" or "e takes".  Just not to write it.  
  > **username_15**: It might also help people check to see if they are still synced correctly with the game they are trying to read from the record.  I know nothing about chess notation, however.  
  
  ---
  
  ### Answer by username_2 on 2022-12-13. Score: 20
  
  You seem to want the notation to be as efficient as possible, disregarding ease of use. Let's take this to extremes:
  
  * If White only has a single move or capture that ends on c4, then instead of Bc4 or Bxc4 should we just write c4?
  * If White only has a single legal Rook move, then instead of Re5 should we just write R?
  * If White only has a single legal move, then...what? Just notate it as "" ?
  
  The conventions in use are a compromise between efficiency and ease of use. And they work very well.
  
  > **Comments:**
  > **username_4**: It seems to me more that OP is looking for consistency than efficiency. The normal situation is that you indicate the type of piece moved (by omission, if it's a pawn), whether or not there is a capture, and the destination square, with information about the starting square if necessary to disambiguate. Except for pawn captures.  
  > **username_0**: The difference between your examples and the situation of pawn capture is that `xd5` contains more or less the same information as `exd5`, except that you may have to look at the board to see where the pawn was. But even without looking at the board, you kinda know what's going on. In your other examples, you don't. We notate captures, checks, mates, en passants, etc. because this is all helpful for getting an overview of the game using only the notation. But with `xe5`, you wouldn't really lose much of this information.  
  > **username_5**: @username_0: Situations where two pawns would both be capable of performing a capture are pretty common.  Indeed, if Black moves a pawn from d7 to d5 when White has pawns on c5, c6, e5, and e6, there could be *four* white pawns poised to capture the black pawn on the next move (two of them capturing directly on d5, and two capturing in passing on d6),  
  > **username_6**: Some friends and I actually at some point had fun in trying to write down games in this kind of notation. Mathematically you could define it as something like "a shortest substring of the move's algebraic notation that isn't a substring of any other legal move's algebraic notation". Not useful but was certainly a fun exercise. The best part of it was being able to often write the game-ending move as just a #.  
  > **username_6**: Although now that I think of it, my definition must be off because 1.c3 would not be possible to write down with that rule. Perhaps we had another definition.  
  > **username_7**: @username_6 Fool’s mate looks good in this notation: 1. 2. 3. 4. #  
  
  ---
  
  ### Answer by username_8 on 2022-12-13. Score: 8
  
  Imagine a situation where there is also a white pawn on `c4`, for example `1. e4 d5 2. c4 e6 3.xd5`. You would have no way of knowing which pawn took on `d5`, was it the one on `e4` or the one on `c4`.
  
  > **Comments:**
  > **username_0**: True, but that same issue occurs when any other pair of pieces of the same kind can capture the same piece. In that case, and only then, we notate the file, or rank, or both. But with pawns, we do it no matter what. Why?  
  > **username_9**: @username_0 Your comment here should be part of the question to clarify things for other people! :D  
  
  ---
  
  ### Answer by username_4 on 2022-12-14. Score: 8
  
  I'd suggest a different reason: to make it sound natural.
  
  How would you pronounce `Nxe5`? I would say "knight takes e5". In that case, the putative pawn move "takes d5" would not sound natural, because it has a verb with no subject.
  
  Once you decide to add a "subject", you may as well do so in a way that gives extra information, since this may be useful. So rather than "pawn takes d5", it makes sense to say e.g. "e takes d5".
  
  There is no grammatical reason to add this information to other captures (which already have a subject) or normal moves (which have no verb).
  
  
  ---
  
  ### Answer by username_10 on 2022-12-13. Score: 3
  
  > Why not just `2. xd5`?
  
  Because we always indicate the piece being moved. The notation `2. xd5` doesn't tell us which piece is doing the capturing. We have to work that out for ourselves. We don't need to write `1. e2-e4`, although we can, because `1. e4` tells us the e pawn is the one being moved.
  
  For instance, in Petrov's Defence we don't write `1. e4 e5 2. Nf3 Nf6 3. xe5`. Instead we indicate the piece being moved by `3. Nxe5`.
  
  > **Comments:**
  > **username_0**: True, but the usual convention is that “nothing” means “pawn”. If I move the knight to `d5`, I write `Nd5`. But if I move a pawn there, I write simply `d5`. Applying the same logic to capturing, `Nxe4` would mean that the knight captures whatever piece is at `e4`, whereas `xe4` would mean that a pawn does the job.  
  > **username_5**: @username_0: There is never more than one pawn that can move to a particular location without capturing.  If one knew nothing about what was on the board, the notation "e4" could mean either "move a pawn directly from e2 to e4", "move the first pawn in rank e from e3 to e4", or "move the second pawn in rank e (which had previously been in rank d or f) to e4", but the board position would make it obvious.  
  > **username_11**: This answer does make sense. The notation always contains a letter which describes _something_ about the piece being moved—either the piece type or the file, sometimes both. For a simple pawn move like "e4," the "e" effectively specifies both the starting file and the ending file, since pawns stay on the same file when they're not capturing.  
  > **username_12**: What happens is that there are many pawns but only a pair of the other pieces.  So, other pieces can be named by their type, which is usually enough to identify them, but the pawns are better named by their file.  "d5" means "pawn d moves to row 5".  "exd5" says "pawn e captures d5".  
  
  ---
  
  ### Answer by username_0 on 2022-12-14. Score: 2
  
  Just realized one other good reason: When using this notation, it’s easier to get an overview of the pawn skeleton of the field solely from looking at the algebraic notation. For instance, to find out where the `e`-pawn is, you can look for the move starting with an `e`. That would be `e4` in this case. Next, you find the next one, which is `exd5`. Then you make a mental note that the `e`-pawn has moved to the `f`-file. Now you can keep following it as it advances along this file, until it maybe changes file again. And so on.
  
  It doesn’t offer much help in figuring out which pawns have been captured, but at least it helps.
  
  
  ---
  
  