-
Notifications
You must be signed in to change notification settings - Fork 134
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
HTML and XML files. #646
Comments
Hi there, If you could give us some more details on 1 (eg sample recipe where you are seeing problems), then we can gladly take a look. (I couldn't spot any obvious problems when I exported a trivial recipe, but maybe I didn't have enough ingredients in it.) For 2, I'm afraid the character encoding is part of the BeerXML spec - in other words, switching to UTF-8 would make us less compliant with the standard (albeit that the BeerXML standard is flawed in many ways). We had some longer discussion about this in #624 but the short answer is that we are working on support for BeerJSON, which is a better file format that fully supports UTF-8. |
If I right-click on any recipe and select export to HTML nothing happens, no window pops up, no error message, again nothinghappens. For me, exporting to html is a fictitious feature that does nothing. Probably (100%) it's the fault of my own compilation (linux64,git). I can always choose export to xml, it works. |
Ah, yes, I see what you mean. There is a new way to export to HTML (courtesy of @mattiasmaahl) which means that, instead of "Export to HTML" you go to "Print and preview" and, from there, you have the option to save as HTML. So, we need to get rid of that right-click menu option, which, as you've spotted, doesn't do anything (most probably because it's trying to trigger the old code that got replaced) and, probably, add "Print and preview" as an option on the right-click menu instead. I'll re-open this ticket so we've got something to remind us to make the fix. Thanks for the spot! |
I believe the right-click "export to HTML" has now been removed - at least I didn't see it in a quick look on the 3.0 release. As ever, please reopen if I'm mistaken. |
Hello :)
Regards
The text was updated successfully, but these errors were encountered: