You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a long standing issue that Russ reminded me of recently. The fundamental problem is that we need to publish the new TSV notes files but that means that translationStudio loses the GL snippets that are in the previous markdown formatted notes files.
Basically, we need to get the Catalog processor to read alignment data and save the output to JSON for the v2 translationStudio catalog endpoint. Maybe we could wrap the JS that reads the alignment data in a Lambda or Docker container to do this? Or should we port the code to Python to do this?
Alternate option: we keep the GLQuote column in the TSV format and make tC Create write that field properly based on alignment data. Then we make the Catalog pull the data out of that field to create the v2 tS catalog endpoint. This is not my favorite because I don't like the GLQuote column. However, I could be persuaded that keep this field in the TSV spec could be helpful in certain situations, this being one of them.
Hi @jag3773 I'm not exactly following how we are going to re-construct the GLQuote information for the ts api. How will the alignment data help with this?
There is a long standing issue that Russ reminded me of recently. The fundamental problem is that we need to publish the new TSV notes files but that means that translationStudio loses the GL snippets that are in the previous markdown formatted notes files.
Basically, we need to get the Catalog processor to read alignment data and save the output to JSON for the v2 translationStudio catalog endpoint. Maybe we could wrap the JS that reads the alignment data in a Lambda or Docker container to do this? Or should we port the code to Python to do this?
Alternate option: we keep the GLQuote column in the TSV format and make tC Create write that field properly based on alignment data. Then we make the Catalog pull the data out of that field to create the v2 tS catalog endpoint. This is not my favorite because I don't like the GLQuote column. However, I could be persuaded that keep this field in the TSV spec could be helpful in certain situations, this being one of them.
cc @RobH123 @da1nerd
The text was updated successfully, but these errors were encountered: