Open lukeeey opened 6 years ago
We should also stop using escape codes and instead use the section symbol § or ampersand & followed by the specific integer for the desired colour
@lukeeey using escape codes is more safer
@DefinitlyEvil How? All we do is make a function in DP to replace the § or & (the latter being a sater option) with \u00a7
.
This allows for cleaner translation strings which makes it easier for other people to read, edit and contribute.
We could litterally do it with this code:
// *some function to read the text from the file*
text = text.replace("&" , "\u00a7");
So &3
would become \u00a73
and so on.
@lukeeey using &
is better because unicode encoding can sometimes be faqued up
@DefinitlyEvil Yeah ik i will make an example of a possible change in the new-translation-system
branch.
For DragonProxy related APIs, do you think the URL could be dp.dragonet.org
or proxy.dragonet.org
?.
For example lang.dp.dragonet.org/languages.json
Why not make it api.dragonet.org/proxy/lang/languages.json
(or api.dragonet.org/dragonproxy/lang/languages.json
)
@ApocalypsjeNL I was planning on adding a CNAME to this repository, but i dont mind writing an entire API for DragonProxy
@lukeeey hosting on Github is better, in case of our server going down.
We can do some stuff on our server but languages can be on github at least. And we are gonna need the language repository online constantly since i will add a way to download languages from DragonProxy by doing something like
java -jar dragonproxy.jar install-language de_DE
I think we should move to YAML for language files. This allows for a few things:
Syntax Highlighting This can greatly improve readability in both an IDE and on Github itself.
Nested Keys This also helps readability, and can reduce key name length. We could also iterate through each nested key if we wanted but im not sure where we would use that.
e.g.
error_cls_login_failed
could be changed toNow i think back on what i wrote and im pretty sure im contradicting myself but oh well lets decide together