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

missing dot in files exported #3576

Closed
ziruizhuang opened this issue Dec 25, 2017 · 6 comments · Fixed by #3578
Closed

missing dot in files exported #3576

ziruizhuang opened this issue Dec 25, 2017 · 6 comments · Fixed by #3578
Assignees
Labels
bug Confirmed bugs or reports that are very likely to be bugs export / save

Comments

@ziruizhuang
Copy link

issues with JabRef version 4.1
however, 4.0 is fine.

Steps to reproduce:

  1. File - Export
  2. Select MS2007 XML format
  3. Save

Expected: a file saved with name "NAME.XML"
Got: a file saved with name "NAMEXML"

@Siedlerchr
Copy link
Member

Probably related to #3565

@tobiasdiez tobiasdiez self-assigned this Dec 25, 2017
@tobiasdiez tobiasdiez added bug Confirmed bugs or reports that are very likely to be bugs export / save labels Dec 25, 2017
tobiasdiez added a commit that referenced this issue Dec 25, 2017
@tgkolda
Copy link

tgkolda commented Dec 27, 2017

I'm having the same problem. Additionally, it's ignoring entirely the file extension for a custom export.

@tobiasdiez
Copy link
Member

@ziruizhuang @tgkolda I think, I fixed the bug. Could you please try out the version from https://builds.jabref.org/fixExport3576/ and report back if these issues are indeed resolved. @tgkolda what do you mean with "custom export"?

@tgkolda
Copy link

tgkolda commented Dec 27, 2017

@tobiasdiez Thanks for your response. The fixExport3576 version didn't run at all for me, so I couldn't check the fix. Sorry. As for custom export, I refer to this capability: https://help.jabref.org/en/CustomExports, of which I am an enthusiastic user.

tobiasdiez added a commit that referenced this issue Jan 2, 2018
* Refactor exports to fix #3576

* Add changelog

* Fix build

* Implement feedback and fix tests

* Include feedback

* Fix checkstyle...again...joy!
@tobiasdiez
Copy link
Member

This should be fixed in the latest development version. Could you please check the build from http://builds.jabref.org/master/. Thanks!

Siedlerchr added a commit that referenced this issue Jan 2, 2018
* upstream/master:
  Add oaDOI fulltext fetcher (#3581)
  Refactor export code to fix #3576 (#3578)
  Fix #3359: Automatically remove colon and apostrophe from key pattern (#3506)
@ziruizhuang
Copy link
Author

ziruizhuang commented Jan 5, 2018

solved this issue, yet introduced another one.
The export format varies, so usually we call a format "Microsoft Word Citation (.XML)" "Open Document Citation (.XML)", etc.
Instead, in the latest snapshot(http://builds.jabref.org/master/JabRef_windows-x64_4_2-dev--snapshot--2018-01-05--master--d6435d56d.exe), there are multiple "XML file (*.XML)". Although they are all en-capsuled using XML, but they are different formats and now we cannot identify one from another.

opened a new issue in #3605

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs export / save
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants