search

twilsonco / latexdiffcite

latexdiffcite is a wrapper around latexdiff to make citations diff properly
BSD 2-Clause "Simplified" License
26 stars 9 forks source link

Feature request: add command to just expand citations in one file #4

Open ftilmann opened 7 years ago

ftilmann commented 7 years ago

It would be great if latexdiffcite could also be run purely for expanding the citations, i.e. introduce another command in addition to git and file, e.g. expand, which takes as its one non-optional argument the filename of a .tex file. in which the citations should be expanded. Output should be the new .tex file; latexdiff should not be invoked. Background: The latexdiffcite functionality is really nice, so I am toying with the idea of introducing an option to run latexdiffcite into latexdiff-vc, the 'native' wrapper of latexdiff, as part of the workflow . Compared to the status quo, this would allow the use of git or mercurial as repository type, and also enable usage of the other options of latexdiff-vc.. (A workaround is to use identical old and new files, but this is computationally wasteful and introduces unwanted latexdiff preamble commands)

cmeeren commented 7 years ago

Thanks for the suggestion, but I'm sad to say that I made this project to scratch my own itch at the time, and I have neither the time or the interest to develop it further now. You can, of course, fork this project and do whatever you want :)

ftilmann commented 7 years ago

OK it's a pity but of course I understand. I cannot really commit to maintaining a forked version, and in any case having different versions around would be confusing. Also, you did fix slayoo's bug a couple of days ago, so seem to be willing to spend at least a limited time on maintenance. So could I ask you to clarify the level of (minor) support you are still willing to give to latexdiffcite?

  1. Is there still a point in making bug reports (rather than feature requests) (currently I have issues with authors with accent or umlaut commands in them, which lead to errors - I will make a proper bug report, but only if you are not categorically excluding looking at that)?
  2. Would you merge a pull request if I implemented the feature suggested in this issue (it seems a pretty straightforward task, maybe easier than the bug fix)? (I would have PMed these question but there does not seem to be any obvious way in github to do this)
cmeeren commented 7 years ago

  1. Bug reports are always welcome. Whether I'll be able to fix them or how soon I can do it will depend on the specifics of the bug and the scale of the required fix.

  2. Pull requests are always welcome! :) They should be fully covered by unit tests though, which might be quite a bit more work.