Hi @KWallace7,
Yes, currently this would require a separate HubDB table with the translated versions.
Another approach would be to build additional columns into the existing table and use those for the translated content, then have a cloned version of the module that pulls in the translated columns. If there is a lot of infrmation and many languages, it could get quite messy in a single HubDB table, so separate tables may be easier to manage.