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

Allow different localization styles to use the same bibtex database on different pages #89

Open
i2000s opened this issue May 3, 2018 · 3 comments

Comments

@i2000s
Copy link
Contributor

i2000s commented May 3, 2018

Hi Martin,

It's me again! I haven't made any improvements to the package for a while, but I received a request from my people recently. They want to show some attractive images for publication entries on one page but no associated images on another page with the same bibtex file. I am thinking it might be necessary to call the localization files defined in two different files, say, bibtexbrowser.local.php and bibtexbrowser.local2.php for the two pages, respectively. Then within these two localization files, I can call different CSS files to display or not to display a new bibentry_image field, which includes an html code block to display images.

When I looked into the bibtexbrowser.php code, on lines 49 and 50, the bibtexbrowser.local.php file is hard-coded into the function. Since I am not sure how to make it flexible to accept customized *.local.php files and don't know if there is an easier way to implement the requested feature, I am resorting to you to give some pointers. I guess it's trivial to you to redefine the localization file calls in a couple of lines.

Let me know if you have time to implement this feature or just give me some guidelines.

Thanks!

Qi

@monperrus
Copy link
Owner

monperrus commented May 3, 2018 via email

@i2000s
Copy link
Contributor Author

i2000s commented May 3, 2018

Could you give me some pointer? How would you like to solve it? I can give a try, but I haven't PHP code for a while.

@monperrus
Copy link
Owner

monperrus commented May 3, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants