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.
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.