Make data displayed on your sitemap more visual by adding unicode symbols to it. They can be used in all visible strings, be it in labels, rules, transformations,…
The only limitation is, that your UI font needs to support the symbol. With BasicUI and the Android or iPhone font that’s mostly the case but you’ll need to give it a try.
@Oli , habe gerade deine Übersetzung gefunden, finde ich super!
Ich spiele gerade mit api.ai Plattform und yahooWeatherForecast herum.
Habe dazu wie in einem Tutorial beschrieben ein webhook über heroku erstellt.
Die Antworten funktionieren, nur sind die eben alle auf English, deine Übersetzung wäre die Lösung!
Wie binde ich das ganze ein, kannst du mir helfen?
Could you please tell me how you’ve integrated weather forecast in api.ai? I was using their Weather Domain, but it stopped working (it was working in the chat bot, but it also worked using their Python API call). All other domains (both free and paid) are still working using Python API. Is there an easy way to query Weather info, or I should create Regular Intents?
habe gerade deine Übersetzung gefunden, finde ich super!
Ich spiele gerade mit api.ai Plattform und yahooWeatherForecast herum.
Habe dazu wie in einem Tutorial beschrieben ein webhook über heroku erstellt.
Die Antworten funktionieren, nur sind die eben alle auf English, deine Übersetzung wäre die Lösung!
Wie binde ich das ganze ein, kannst du mir helfen?
you’ll need to copy the text over into a map file and use the map transformation while defining your sitemap. Please have a look at the very similar Astro example here:
I think you misunderstood me, I wanted to know how I did the api yahooWeatherForecast(from github) to adjust with the german translation.
Or am just wrong here ;D
Looks like others have already chipped in
Uh…webhook? heroku? I only know Captain Hook and maybe i can write a haiku
Sorry, clueless…but of course feel free to use the data as is if it helps.
HTH,
Peace out,
-OLI
Sorry to revive this old thread but i think there is something wrong with the moon symbols and how they eventually get transferred to the generated web page with for example basicui
i followed the astro example and most of the unicode symbols works just fine except the moon symbols (i use chrome on windows)
each moon symbol just ends up as two diamond shaped symbols just like the picture in this thread: Astro Items+Sitemap+Map+♈ Binding Example
but i did an experiment, in chrome i did an inspect and edited the html and replaced the bad moon symbols with the symbols i copied from the astro.map file.
result was working moon symbols in page.
obviously this wont stick and was just a test if browser can display them or not and it can.
so i suspect that some of the unicode symbols gets mangled when page is generated.
maybe a bug in openhab 2.2?
there is definitely something odd going on with the moon symbols.
leaving page (basic ui) as is until it updates makes the unicode symbols work but reloading page breaks it.
is there any browser specific checks that makes unicode symbols handled differently depending on browser?
can someone point me in the right direction where to report this as a bug?
i have again confirmed that unicode symbols that get auto updated AFTER apage loads, for example due to changes works but not initial symbols on page refresh.
I noticed the same behavior, but not only for the moon symbols. It seems to apply to several unicode symbols, and also I noticed the behavior for both Chrome (Win64 and Android) and Edge (Win64). Interestingly, in the OpenHAB app the unicode symbols are correctly displayed right away, also if I copy-paste the symbols the pasted symbols are initially displayed using the &#…; notation and, after initiating a search on this string, as correct unicode symbols (tested in Chrome (Win64).
When I inspect the OpenHAB basicui page then I find that initially the symbols are only displayed as diamonds with question marks, yet after a data update they are replaced by, for example,
Here I note that I used the instructions here to complete the unicode character set in Chrome (yet this did not have an effect on the initial display of the symbols, I still have the same behavior of unicode symbols only being shown after a data update).
So it indeed seems that browsers do only interpret the unicode symbols after a data update took place. Any suggestions on how this could be fixed would be much appreciated.
i would not be surprised if there is some clever code in the web server trying to figure out what browser it is and then adjust unicode characters accordingly or something similar.
probably based on the user-agent string.
would be interesting to see if behavior changes if you fake the user agent with something else.
since browser clearly can display the unicode symbols propperly the fault must lie with openhab and its web server.