-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal for additional settings/features #9
Comments
Regarding point 1. We use filenames with country codes in them.
could either the filename pattern be somehow deduced from the current filename, or it be made configurable in some way. I would also expect to have to change the default locale to en-GB so it knows which english file to use, so perhaps that's all that it needs to switch to a different pattern? Google doesn't support country codes but the extension now also supports AWS and Azure and they do (e.g. both support fr-CA, but the call fr-FR just "fr" So we will probably need to maintain a list of what languages each service supports (unless there's some way to query for it?) and handle mapping filenames to the most appropriate language code. For en-GB to en-US (or the reverse) it would be nice if it just copies the original file without translating, but if that was the only one I had to do by hand it wouldn't be ok. Just in case anyone else is searching for it. If the extension doesn't understand your filename format you will see this error:
|
|
Hi there,
the plugin is already very helpful, however I would like to propose the following additional features:
1. Allow for input file name customization
Currently the plugin is looking for
en.json
only. It would be great to customize this as my files have aintl_
in front of it.2. Allow for input file extension customization
Currently the plugin is looking for
json
only. It would be great to customize this as my files are ending inarb
, which is essentially a json file.3. Add filter options
Currently the plugin is looking for translating each and every string, but I would like to be able to define filters so that some strings to not get translated. Particularly, some of my strings look like this
"@testString": {...}
. I would like to filter out everything starting with@
.Do you think there is a chance to get this implemented?
The text was updated successfully, but these errors were encountered: