 |
I can see what's going on, but I want to question whether DR should forcefully correct a user who is typing the file extension on purpose. The file entry field itself is generic and can get its input from the File Selector dialog, so I can't restrict it to not allow extensions. You can also freely select a file extension in other apps like Photoshop, without affecting what gets written to the file. (I think I've seen GIMP doing it the other way around: entering the extension determines the format.) I can also see that MS Word has gone a similar route as you suggested and tied the file extension to the format, the entry field itself is not displaying any extension. The .docx extension will always be appended, regardless what the user types. Its file selection dialog is highly customised though, DR is using the native File Selection dialogs of the various operating systems, so it cannot influence what string is returned by that dialog and written to the entry box. What about warning the user about a file extension mismatch, so they have to confirm to proceed exporting to an unusual extension? |
 |
Sure, the main aim is that the exporter shouldn't silently do something else than what the mapper is expecting. It'd be a bonus if it were more difficult to get such a desync (i.e. update Output Format if a valid extension is typed into File Path), but as you point out there are various technical hurdles. What may also make sense is to fix case (B). Output Format usually updates the extension in the File Path, but does nothing if there was no file extension in the File Path. But it's a minor thing. |
- Anonymous
