Skip to content
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

Convert source file to XLIFF should not rely only on file extension #10

Open
cburatto opened this issue Dec 23, 2014 · 1 comment
Open

Comments

@cburatto
Copy link

Currently: If you add a file to he Source folder of a project, you can only use the "Convert to Xliff files" option if the file has a known extension accepted by the tool. For example, an HTML file with name "somefile.mycustomextension" will not even open the conversion dialog -- it will reject the operation right away.

Should be: The tool should give the user the option to select run the "Convert to Xliff files" command and open the dialog, where the user could explicitly select the appropriate format for conversion. Only then the tool could try to convert and issue a message in case of error. In the "somefile.mycustomextension" example, the user could select the "HTML" format and the conversion would run normally.

Right now, I circumvent this by renaming the files to an accepted extension, but that is not the expected behavior.

@oisee
Copy link

oisee commented Feb 4, 2015

Have you figured it out how to compile translationstudio8? =)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants