-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
e-maxx-eng-img #224
Comments
+1 (it's probably beneficial to have these tools available to other people who might want to modify them if you're not available, though I don't think it will be a frequent scenario) For how exactly to do this best, summoning @RodionGork to the thread :-) |
@RodionGork It should be enough if you simply create a new repository. |
Sorry for delay! Won't you, Friends, mind if it would be called e-maxx-eng-aux so that not only sources for images could be placed here, but also any additional stuff which later could be found useful. E.g. anything related to tests or some sources for demos (we haven't them now, but I'm still anticipating we can come up with some idea later). If it's ok, just feel free to create images folder inside and put everything related to images there. If not, let's rename the repo :) |
@RodionGork image folder inside e-maxx-eng-aux is fine. |
Oh, sorry. I thought we have equal rights, but it seems I'm mistaken. I tried hastily to fix it now (please check if it works) and will study the github teams/rights features deeper bit later. Sorry for inconvenience! |
Now it works. |
UPD, I've changed rights again. I've found here is "Admins" group and added you here. Probably you should have "more equal" rights now, but feel free to report if there is anything wrong (and sorry beforehand). |
I always try to generate nice images for the translated articles. E.g. I just generated some for MST with Kruskal.
I make these images with Latex/Tikz + one small script to resize/compress them. For this purpose I made a repo jakobkogler/e-maxx-eng-img, just so that I have the ability to modify them later without having to regenerate them from scratch.
Currently this is only a personal repo of mine. But we could integrate it in the e-maxx-eng project. I mean having it as fourth repo beside e-maxx-eng, e-maxx-eng-img and e-maxx-eng.github.io.
What do you think?
The text was updated successfully, but these errors were encountered: