Getting document with invalid Windows file name character creates empty file

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a Google Docs document with a title that is not a valid Windows file 
name, e.g. "test:doc"
2. Type something in the document and save it
3. google docs get --title "test:doc"

What is the expected output? What do you see instead?

I hoped for a file with the name tweaked to be valid in Windows. Failing that, 
I expected an error message about an invalid file name. Instead, I got an empty 
file named "test" (the part of the name before the invalid character).

What version of the product are you using? On what operating system?

GoogleCL v0.9.7
Windows XP Professional SP3

Please provide any additional information below.

I know Windows support may not be a priority, so tweaking the file name may be 
too much to ask. But there should at least be a file system error that GoogleCL 
could pass on to the user, right? That would be more useful than an empty file 
with a partial name. Thanks!

Original issue reported on code.google.com by itruett on 21 Jun 2010 at 7:00

[GoogleCodeExporter]

Amazingly, Windows will not raise an error in this situation. This is probably 
a feature/bug request for Python, especially since there are quite a few 
invalid filenames and characters on Windows.

I've patched the trunk to let you specify a new name (google docs get --title 
"test:doc" valid_name_for_test_doc), but this issue will need a bit of work 
still.

Original comment by tom.h.mi...@gmail.com on 23 Jul 2010 at 10:48

• Changed state: Accepted

[GoogleCodeExporter]

This issue was closed by revision r539.

Original comment by tom.h.mi...@gmail.com on 9 Feb 2011 at 5:50

• Changed state: Fixed