ArrnyWei / google-api-objectivec-client

Automatically exported from code.google.com/p/google-api-objectivec-client
0 stars 0 forks source link

Newline caractere replaced with space when update google doc file #43

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.create a google doc txt file on google drive
2.update it via api (GTLUploadParameters uploadParametersWithData)
3.all newline are replaced with space

What is the expected output? What do you see instead?
newline must appears well after doc being updated

What version of the product are you using? On what operating system?
google drive api r350, ios 6.1, xcode 4.6

Please provide any additional information below.
Update is done with NSData like @"Hi\nGoogle"
Tried with \n, \r, \r\n
Tried to set file convert YES or NO
The download part work well, newline on google doc appears well on IOS.

Original issue reported on code.google.com by robin.sz...@gmail.com on 9 Aug 2013 at 11:28

GoogleCodeExporter commented 9 years ago
Are you seeing the same problem when uploading to a new document rather than 
updating an existing document?

Original comment by grobb...@google.com on 12 Aug 2013 at 8:23

GoogleCodeExporter commented 9 years ago
After trying many ways, I change the type of document I use. Before I used a 
simple text file on google drive, downloaded it in rtf format and updated it 
but that way newlines disappears (with or without convert, mimetype = text/csv 
or text/plain).

Then, I switch to spreadsheet file on google drive, download it as csv and 
update it as csv with conversion enable, that way is the right way. (csv for 
storing array data)

No problem when inserting new files.

Original comment by robin.sz...@gmail.com on 12 Aug 2013 at 8:34

GoogleCodeExporter commented 9 years ago
I have not seen any problem when uploading a plain text file containing 
newlines using DriveSample on a Mac.

Unless there is indication that the Objective-C library is modifying the data 
being sent to the server, this is likely just a server API issue for specific 
document types, not a client library issue.

Original comment by grobb...@google.com on 12 Aug 2013 at 10:04