Is your feature request related to a problem? Please describe.
in other translation platforms you need to import only template file, after that you can translate all strings from it to other languages. But in traduora i can't do that. Do you plan to add this feature, or how to do workflow? Template file create automatic via extracting strings from source code.
When i'm use zanata i'm upload

when extracting configurations, it would be useful to users if we included a comment with a link to the related resource's documentation on the wiki page for each resource.

EX:

For information on how to use this resource, refer to https://

TeamsChannel 12345-12345-12345-12345-12345
{
[...]
}

I noticed when making requests for Player information some of the NFL kickers seem to have a different format for their URI. A lot of current kickers follow the standard 8 character 'LlllFfNN' format. But some have a 10 character string.

In this example Mason Crosby this works fine and returns 'Field Goals - 30':

thisplayer = Player('CrosMa20') 
theyear = '2018'
print('Fie

It would be convenient (and intuitive) to include stories, rules as well as answers (aka i18n) in application dump.
In order to export/import stories along with config intents and sentences.

Hello,

I have a small suggestion to make, I would like to know if you can add an option that allows to put the uhc in another card than the main one. Because I have a waiting lobby on the main map on the server and I would like the uhc on another map via Multiverse Core but you do not add the option.

thank you in advance

We really should have a Sphinx doc site that explains all the great features in Source Optics and how to use them (+ incorporate install instructions) to get users more excited about the feature set without installing it first.

The README file currently shows how commands are run, but, first, this does give a prompt symbol, $, to indicate that they are commands for execution. Also, the README does not give any output of these commands. This should be added to the README, along with the discussion of the trade-offs inherent in the different teams.

Apologies if it's me being clueless, but it looks like either Slack has changed the way authorisation works for their API rendering this helper useless, or I'm having difficulty working out where to get the appropriate tokens.

Some documentation on this might help.

Should say

• Glad you all met! Thanks for letting me know.
• Happy to hear some of you could meet. Thanks for letting me know.
• Sorry you couldn't meet. Thanks for letting me know.