If the English version looks fine then it means that German pack doesn't have the latest keys. You need to compare both packages with the tools like Araxis meger and add / change what missing in the German variant. Or ask the vendor about it.
When you say "keys" do you mean translation keys? Because I translated all of them. I see now that German module version is 12.0.1, and my UNA installation is v14. I am not sure that matters at all tho...
Hi Haris, betreffend eines GERMAN Sprachfiles/App für UNA. Meines Wissens gibt es keine aktuelle deutsche Sprachdatei. Die letzte umfassende war die von Michel Freya, free für UNA 12.1
Dazu gibt es noch eine kommerzielle 'Bausatzvariante' von Excel, also ein Basisfile, das installiert sein muss und dann ergänzende files zu einzelnen Modulen. Diese Variante hatte ich bisher nicht getestet und kann daher nicht sagen, welche Core oder Custom Module enthalten und vor allem laufend aktualisiert werden.
Hallo Peter, danke für deine Nachricht. Ja, das ist die deutsche App, die ich verwende. Auch wenn ich alles übersetzt habe, sieht sie immer noch schrecklich aus.
Den zweiten Teil deiner Nachricht kenne ich nicht. Ich teste UNA erst seit einer Woche.
Ich gehe davon aus, dass du eine aktuelle UNA 14 'B2' Version verwendest oder zumindest 13.1. stable. Das Sprachfile von Freya ist für UNA Version 12. Inwieweit Freyas Sprachdatei den 'Calendar' beeinflusst, kann ich nicht sagen. Aber teste einfach mit der englischen Sprachvariante. Wenn damit alles OK ist, war es die Sprachdatei von Freya
Wenn also ein Modul nicht auf eine neuere Version aktualisiert wird, kann dies Auswirkungen auf andere Module haben, auch wenn es nicht direkt mit z. B. der Event-App verbunden ist.
Exact. Das kann Auswirkungen haben. Insbesondere auch bei der Verwendung von 3rd Party Modulen. Gelegentlich 'hinken' die Entwickler beim update ihrer Module auf die aktuellen UNA Versionen etwas hinterher.
Solange du im UNA CORE und UNA POWERAPP Universum bleibst und immer alles updatest., bist Du save.
Leider baue ich dies für eine kleine Gruppe deutschsprachiger Freunde. Sie sprechen natürlich auch Englisch, aber es wäre schön, wenn sie die Plattform in ihrer Muttersprache nutzen könnten.
@haris I'll better reply in English, because I had the same problem about 2 years ago with the same German language module. And other users will have them, too when using this German language module.
The good message is: the language module is working with all versions of the UNA framework, even with those later than version 11, which it was originally built for. The not so good message is, it needs some work to correct it. @Anton L from the dev team helped me to find the issue and solve it at that time when I went through that nightmare of completely destroyed grids in German, whereas in English everything looked perfect. Thanks to Anton L, again.
The problem is, that there a bad html tags everywhere in this German language mod. Here's a screenshot for explanation.
Those bad tags are in the language keys and you have to find them and correct them manually in Polyglot. Anton gave me the good advice to use the source code function in developer tools of the browser and search for those faulty tags, like </ i>, </ b> and other markup tags, which should of corse be like </i>, </b>. After the correction the German language version will look exactly the same as the default English version.
Here's a screenshot of my test server, running latest framework version 14.0.0-B2 with the corrected German language module (Protean template modified).
Thank you for the advice. Just to make sure I have done it correctly. In the folder "/modules/noichl/german/data/langs" there are a bunch of subfolders with the "de.xml" files.
I used Notepadd++ to find and replace the following:
</ i> to </i>, <br /> to <br/>, </ b> to </b> and "class = " to "class=" (without "")
After uploading them back to the server, and emptying the cache, ... I still have the same problem. Have I missed anything?
Well, the <br /> should not be corrected, because it's the only markup that can stand alone without closing tag and will therefore be parsed correctly with the space before the slash. To make the problem clear, the html parser cannot identifiy closing markup tags with the space in between and this will demage the grid layout in your German layout. You can easily check if you didn't miss any faulty closing markup by opening the source code page of pages which do not look the same as in the English version of a page.
Make sure to clear caches in Studio as well as in your browser after you've done the corrections.
I see. As I understand <br /> or <br/> makes no difference in parsing. Browsers would read it the same way. I don't think that is a problem. I think biggest problem lies in i and b tags.
But can you please answer if I have edited the correct files? Those are the de.xml files in the german/data/lang folder? Or I need to check some other files as well?
If you changed the markups in the XML language files you have to compile them anew in Studio Developer module (am I correct, @LeonidS ?). I chose to correct the faulty tags in Polyglot, as explained above, because that way I could directly check the changes in the frontend.
@thomlin I found where was the problem. It was <i> tag in these specific instances. I used search to find all the errors in all the modules in Polyglot. btw, I used same method to find all the instances of <b> tag and correct them. I also corrected class = "" to class="", but I am not sure if that plays any role.
Hello @haris !
If the English version looks fine then it means that German pack doesn't have the latest keys. You need to compare both packages with the tools like Araxis meger and add / change what missing in the German variant. Or ask the vendor about it.
H
When you say "keys" do you mean translation keys? Because I translated all of them. I see now that German module version is 12.0.1, and my UNA installation is v14. I am not sure that matters at all tho...
Hi Haris, betreffend eines GERMAN Sprachfiles/App für UNA. Meines Wissens gibt es keine aktuelle deutsche Sprachdatei. Die letzte umfassende war die von Michel Freya, free für UNA 12.1
Dazu gibt es noch eine kommerzielle 'Bausatzvariante' von Excel, also ein Basisfile, das installiert sein muss und dann ergänzende files zu einzelnen Modulen. Diese Variante hatte ich bisher nicht getestet und kann daher nicht sagen, welche Core oder Custom Module enthalten und vor allem laufend aktualisiert werden.
lg peter
H
Hallo Peter, danke für deine Nachricht. Ja, das ist die deutsche App, die ich verwende. Auch wenn ich alles übersetzt habe, sieht sie immer noch schrecklich aus.
Den zweiten Teil deiner Nachricht kenne ich nicht. Ich teste UNA erst seit einer Woche.
lg
Ich gehe davon aus, dass du eine aktuelle UNA 14 'B2' Version verwendest oder zumindest 13.1. stable. Das Sprachfile von Freya ist für UNA Version 12. Inwieweit Freyas Sprachdatei den 'Calendar' beeinflusst, kann ich nicht sagen. Aber teste einfach mit der englischen Sprachvariante. Wenn damit alles OK ist, war es die Sprachdatei von Freya
H
Ah, ich verstehe. Ja, UNA-Version ist 14.
Wenn also ein Modul nicht auf eine neuere Version aktualisiert wird, kann dies Auswirkungen auf andere Module haben, auch wenn es nicht direkt mit z. B. der Event-App verbunden ist.
Das ist schade …
Exact. Das kann Auswirkungen haben. Insbesondere auch bei der Verwendung von 3rd Party Modulen. Gelegentlich 'hinken' die Entwickler beim update ihrer Module auf die aktuellen UNA Versionen etwas hinterher.
Solange du im UNA CORE und UNA POWERAPP Universum bleibst und immer alles updatest., bist Du save.
H
Leider baue ich dies für eine kleine Gruppe deutschsprachiger Freunde. Sie sprechen natürlich auch Englisch, aber es wäre schön, wenn sie die Plattform in ihrer Muttersprache nutzen könnten.
Das Problem kenne ich. Es gibt dafür derzeit leider nur 2 suboptimale Lösungen:
Yes, certainly. This package contains not all keys which exist in 14 and some of them have been modified.
T
@haris I'll better reply in English, because I had the same problem about 2 years ago with the same German language module. And other users will have them, too when using this German language module.
The good message is: the language module is working with all versions of the UNA framework, even with those later than version 11, which it was originally built for. The not so good message is, it needs some work to correct it. @Anton L from the dev team helped me to find the issue and solve it at that time when I went through that nightmare of completely destroyed grids in German, whereas in English everything looked perfect. Thanks to Anton L, again.
The problem is, that there a bad html tags everywhere in this German language mod. Here's a screenshot for explanation.
Those bad tags are in the language keys and you have to find them and correct them manually in Polyglot. Anton gave me the good advice to use the source code function in developer tools of the browser and search for those faulty tags, like </ i>, </ b> and other markup tags, which should of corse be like </i>, </b>. After the correction the German language version will look exactly the same as the default English version.
T
Here's a screenshot of my test server, running latest framework version 14.0.0-B2 with the corrected German language module (Protean template modified).
H
Hi @thomlin
Thank you for the advice. Just to make sure I have done it correctly. In the folder "/modules/noichl/german/data/langs" there are a bunch of subfolders with the "de.xml" files.
I used Notepadd++ to find and replace the following:
</ i> to </i>, <br /> to <br/>, </ b> to </b> and "class = " to "class=" (without "")
After uploading them back to the server, and emptying the cache, ... I still have the same problem. Have I missed anything?
T
Well, the <br /> should not be corrected, because it's the only markup that can stand alone without closing tag and will therefore be parsed correctly with the space before the slash. To make the problem clear, the html parser cannot identifiy closing markup tags with the space in between and this will demage the grid layout in your German layout. You can easily check if you didn't miss any faulty closing markup by opening the source code page of pages which do not look the same as in the English version of a page.
Make sure to clear caches in Studio as well as in your browser after you've done the corrections.
H
I see. As I understand <br /> or <br/> makes no difference in parsing. Browsers would read it the same way. I don't think that is a problem. I think biggest problem lies in i and b tags.
But can you please answer if I have edited the correct files? Those are the de.xml files in the german/data/lang folder? Or I need to check some other files as well?
T
I left the linebrakes untouched.
If you changed the markups in the XML language files you have to compile them anew in Studio Developer module (am I correct, @LeonidS ?). I chose to correct the faulty tags in Polyglot, as explained above, because that way I could directly check the changes in the frontend.
H
@thomlin I found where was the problem. It was <i> tag in these specific instances. I used search to find all the errors in all the modules in Polyglot. btw, I used same method to find all the instances of <b> tag and correct them. I also corrected class = "" to class="", but I am not sure if that plays any role.
T
That means your German layout is OK now?
H
yes 😊
T
Sehr gut! Viel Erfolg mit deiner deutschsprachigen Seite!