First, my own files that had been causing troubles contained
characters such as multiple dashes, square brackets, and angle
brackets. When I removed these characters, I was now able to import
them as non-blank files. I strongly recommend that a complete list
of problematic characters be prominently displayed within Help for
the ThinkBook app.
Second, it took me a while to understand the distinction between
"Get text from Dropbox" (accessible by double-tapping on the left
of an entry) and "Read .txt from Dropbox" (accessible from the Gear
icon in the lower left of the menubar). I think much of my
confusion was caused by mixing-and-matching the first method for
sending and receiving text files with the second method. So if a
user double-taps ThinkBook Manual to "Send text to Dropbox" and
then uses the Gear icon to "Read .txt from Dropbox", the result is
a single-line entry with no contents. This is definitely
confusing, because it seems to me the user is expected to remember
forever which of these two methods was used to generate every .txt
files in the ThinkBook folder on Dropbox.
In summary, my problems were resolved by eliminating certain
characters from my file (and it sure would be great to have a
comprehensive and easily accessible list of offending characters),
and by more carefully keeping track of the two methods to send
plaintext files to Dropbox (but there has to be some way to flag
this difference better to the user).
on 09 Nov, 2012 09:59 AM
Additional comment (last for now, I think, honest). These bugs
only seem to occur on files that are being imported as thinkbook
format - the plain text importer doesn't have the problems, so I'm
pretty sure its the parser code.