phpBB • Free and Open Source Forum Software

Hallo Mark, i think your extension works fine now. I like it. German translation looks good. (or do you know anywhere something to correct it?)
LG Stefan

Praggle is the German translator. He's probably reading this support forum, but you can also leave him a private message or initiate a pull request in his GitHub archive if you have translation suggestions. https://github.com/Praggle/digests/releases

As translators finish their changes for 3.2.12 and 3.2.13 please let me know. I'm waiting to create 3.2.13 until all four translations are up to date. Thanks to our translators and if you want to translate Digests into a different language let me know.

Bug reports, suggestions and wishes to the german translation are always welcome. Best way is to create a commit inside GitHub with the corrected translation, so i just have to acknowledge it or you write an issue inside GitHub. You can report translation errors also in this place. However, GitHub has the advantage that several people can participate well in the development work and that it does not necessarily depend on the motivation and time of a single developer.

German:
Fehlermeldungen, Vorschläge und Wünsche für die deutsche Übersetzung sind stets willkommen. Am, Einfachsten ist es, wenn ihr direkt in GitHub eine Code-Korrektur (commit) macht, dann brauch ich die dort nur zu übernehmen oder ihr formuliert dort ein Thema/Anliegen (Issue). Ihr könnt Übersetzungsfehler aber auch an dieser Stelle melden. GitHub hat jedoch den Vorteil, dass sich mehrere Personen gut an der Entwicklungsarbeit beteiligen können und dass es nicht unbedingt von der Motivation und Zeit eines einzelnen Entwicklers abhängt.

Guys, I am not very familiar with github.

How to merge or don't know how to do it, to just translate the new words?

There is a pencil/edit icon next to any editable file. If you are making little changes this may be a way to go.

How will I know what to add / change in what file?

I would start with a GitHub search. For example, to compare version 3.2.11 to 3.2.12:

https://github.com/MarkDHamill/digests/ ... 1...3.2.12

Once you see the changes to the language files, make the appropriate changes to your version. For example, if there is a change to /language/en/common.php, make it to /language/es/common.php for Spanish for the affected lines of code.

OK, I have created a release, but how do you create a base branch?

On GitHub, navigate to the main page of the repository.

Click the branch selector menu.

Type a unique name for your new branch.

Press Enter.

If you mean how do you create a branch from the master on github.com, I really don't know. Typically you do this on your machine then publish it to github.com. That's the way I do it. There are a lot of GitHub Desktop clients out there. But I think if you do all your editing on github.com on the master, whoever downloads the master will have your most recent version.

What is the difference between branches and releases.

I just hope I won't break the files and versions...

Mark, why you don't have any releases?

And why adm is still version 3.2.11 release when all the other files are version 3.2.12?

Until recently, the extension was not approved so branches were more convenient than releases, since a release implies it is approved. In addition, when you submit an extension for review, you don't know if it will be approved or not. Mine was rejected many times. For my purposes, using branches suffices.

When you make a commit in GitHub, it applies whatever brief note you assign to the commit to all changed files. The adm folder was not changed so its label was not updated.

Addition:

A branch can be changed. A release is a frozen state of a branch.