Comments (4)
An easier algorithm would be to simply compare file timestamps: If a file of any language has been changed after the English pendant, this is a strong indicator that the file is up to date, whereas if any file has been changed and the English pendant is more recent, that there are changes that still need to be incorporated?
I'm heavily in favor of automation that makes use of GitHub actions, but I'm pretty much against some shell-script magic (less because it doesn't work, but rather because it keeps everything maintainable…)
from zettlr-docs.
An easier algorithm would be to simply compare file timestamps: If a file of any language has been changed after the English pendant, this is a strong indicator that the file is up to date
Yes, this is the simpler of the two scenarios and timestamps provide enough data to say "translation file is most likely up-to-date" (we cannot really know the state of the translation unless we look at the contents, anyway).
whereas if any file has been changed and the English pendant is more recent, that there are changes that still need to be incorporated?
Yeah, things get complicated here. Timestamp will only indicate that there is a change. But to be able to know if it was fixing of a typo, a complete rewrite of the file, or something in between, one needs to look at the diffs. I don't see any other way around it (unless we expect the translators to compare the whole translation file to the English version sentence by sentence). And Git is quite handy here. It provides all the information needed. One can see exactly what has changed in the English version and easily estimate the amount of work that needs to be done.
I'm heavily in favor of automation that makes use of GitHub actions, but I'm pretty much against some shell-script magic (less because it doesn't work, but rather because it keeps everything maintainable…)
There is nothing "magical" about this. The script is very simple and just calls Git to gather the data and present in a human-readable format. As I said, unless the translator is willing to compare whole files after the English version is changed, I don't see a way to keep the translations up-to-date where Git is not involved. And I think, it would have been easier if there was a place where there was an always up-to-date state of all translations (like in the case of UI translations).
But... I don't contribute to any of the translations. So, all that said, it's up to the people doing the translations if they want to use this or not. The script is there. You can close this issue if you don't see the value.
from zettlr-docs.
And I think, it would have been easier if there was a place where there was an always up-to-date state of all translations (like in the case of UI translations).
Absolutely, I even thought about that, but translations are coherent pages of a lot of text, and thus it's easier to maintain them through git …
I mean, very basically, after each release the translators only need to go through the Changelog of the app — I document absolutely every new and changed behaviour in there, it's the most complete and most comprehensive information for what has changed, and what has stayed the same. Maybe we could do it this way, that I'll just paste the changelog in here for others to refer to and apply the changes …?
from zettlr-docs.
Absolutely, I even thought about that, but translations are coherent pages of a lot of text, and thus it's easier to maintain them through git …
I don't really understand this argument because what the script does is use Git in an automated way to prevent manual mistakes. The whole point of the script is to construct the correct Git command to show the diffs. That's literally the only thing i does.
Anyway... As I stated in my previous comment, I don't contribute to any translations, so I don't think it makes sense for me to drag this discussion on. I'm bowing out.
from zettlr-docs.
Related Issues (20)
- Add additional programming language highlighting HOT 1
- Cmd/Ctrl-Clicking tags not working HOT 1
- Add information on migrating Zettlr notes to a new computer or OS-install. HOT 5
- old documentation links are still active. HOT 2
- Allow more precise searching when clicking links HOT 1
- Change in how the documentation is structured for Exporting, Defaults, and Academic Tools
- Win11 Export Error HOT 1
- Create page from an internal link HOT 1
- Working with multiple cursors in Linux HOT 1
- Link to a file with round brackets in its name is falsely resolved HOT 1
- zettlr's performance need to improve HOT 1
- Outdated documentation HOT 1
- "Save" silently fails!! HOT 1
- Why insisting on US spelling? HOT 1
- Disable cursor blinking HOT 1
- Active Search avoids saving Files HOT 1
- Flatpak related things
- How to have headings numbered using custom CSS HOT 3
- Add a guide for changing export templates HOT 2
- Zettlr hangs on opening [Windows] HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from zettlr-docs.