Edit - Stack Overflow

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4

"Is there a reason that you need to parse this filename at all?" -- yes I want to know the file name ;). "At least the one thing that's consistent is that the filename portion of the header ends with a double quote," The filename and name fields should not come in this specific order, so it is bad idea to suppose that file-name ends with last quotation mark.

Artyom
– Artyom

2010-05-30 12:16:32 +00:00
Commented May 30, 2010 at 12:16
Want != need. ;) Ok, so you're at least guaranteed that it'll end with " or with "; -- with this lack of consistency you have to make some concessions, like relying on the fact that users won't put "; in the middle of their file names :) Alternatively, are you using a web framework that supports a best-effort parsing of this attribute for you?

Christopher Orr
– Christopher Orr

2010-05-30 14:05:06 +00:00
Commented May 30, 2010 at 14:05

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »

Collectives™ on Stack Overflow