gDoc support

First; love the app! I've been using premium for years now.
Second; I'd like to request gDoc support. I use @voice in my proofreading process, letting me listen to text while reading it. Normally, I copy text from gDrive while using the 'read copied text' feature.
I decided to optimise my workflow - having to fiddle around for 30 secs between each new chapter/file got annoying - by installing the @Voice gDrive addon. This works great. It reads the *.url files the Chrome plugin makes as well as *.docx files. It does not read native gDoc files, however. Any Google Docs link inside the folder is completely ignored.
I work around this issue by downloading the gDoc files to *.docx and placing them inside the folder, but I'd love native gDoc support, if at all possible.
 
Thanks in advance,
 
Alkaliho

I am manually adding files to my @Voice folder on my google drive. The 'Add from Google Drive' option in the Reading List menu downloads everything I put inside the @Voice folder (docx, url, pdf, etc) except for Google Docs files.
Here is a screenshot to illustrate:


 
The program does not properly parse native Google Doc files (as well as epub's, I found during testing) when pressing 'Add from Google Drive'.
 
I'd love for this to be added, if at all possible.
 
Cheers.

The wonderful and very confusing world of cloud saving is confusing and wonderful indeed. 
Editing a Google Doc file saves it automatically. Note the 'saving...' text on top of the page the moment you change a single character.
Anyway, here is a folder containing a working file as an example. Downloading it gives you a *.doc file. Opening it loads it inside the Google Docs editor, which is my default working environment these days.
 
As for how to solve this issue? My coding skills aren't that great, but I'm guessing that you could use the Google Drive REST API to download something readable once you've got the file ID?

This is the problem I'm having too.
I can't get @Voice to read the pure gDoc (Google Document that is not converted into *.docx) files. I don't think Google saves the Google Doc files as actual files, though.
 
I get the feeling like we are somehow misinterpreting each other, though.
 
Here is my problem, worded as clearly as I can manage: I would appreciate it if your 'Add from Google Drive' functionality inside the @Voice Android app would include any native Google Docs documents. Currently, it does not seem to include native Google Docs files that I place inside the /root/@Voice folder. It does, however, parse *.doc, *.docx and *.pdf files that I have placed inside the /root/@Voice folder. 
 
Here is my use case: I copy Google Docs files to my /root/@Voice folder. These items do NOT get read by the @voice Android app. I would frigging love it if they did get read by my @voice Android app. Please make them be read by my @voice Android app's 'Add from Google Drive' functionality which I select from my Android App menu.
 
Please observe the following example: EXAMPLE.
 
In this example, I have transformed chapter 91 until chapter 100 into *.docx files. Please note that these files read correctly (when I try to view them from the /root/@Voice/ folder seen through my @Voice Android app).
It's the following 20 files (101 until 120) that do not read correctly (when I try to view them from the /root/@Voice/ folder seen through my @Voice Android app)..
 
I can download these files as *.docx files and read them correctly (into the @voice aloud Android app). Please note that this is not the problem I'm reporting here.
 
I'm reporting the problem of the fact that the files 101 - 120 do not load correctly inside my @voice Android app without being first converted into another file type.
 
Please support the reading aloud of these file types without the need to convert them to another file format first (from my perspective).
 
Many thanks in advance,
 
Alkaliho
 
 

It works great, thanks a lot!
I also saw the update that allowed epub's to be downloaded through gDrive, that made me chuckle.