-
-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Property links don't work in de-formal language #5342
Comments
Unfortunately, this does not solve the issue for me. You can see it here: |
@JeroenDeDauw I'm waiting for some feedback, here https://test.knowledge.wiki/index.php?title=Attribut:Objektbezug&action=edit I don't see de-format specified |
That is right. I was not expecting having to set a property description to de-formal, I was expecting it to fall back to de if the wiki is set to de-formal. |
@thomas-topway-it would it be easy to implement a fallback to "de" if the wiki is set to a subset of de (like de-formal) and there are no annotations with de-formal, but only with de? |
@krabina I've checked.
|
Interesting. But in MediaWiki, when you change interface messages, you don't have to put everything in de-formal. de is sufficient. For example, there is an uploadtext https://test.knowledge.wiki/MediaWiki:Uploadtext/de that is working even if the wiki is in de-formal language. I don't have to create a https://test.knowledge.wiki/MediaWiki:Uploadtext/de-formal |
My comment wasn't correct. There is a fallback specified in the file
however for this to work in our case we have to use an inverse map (not a fallback) from de to de-formal specifically for the |
I am not sure I completely understand this. But from a user perspective, I would see it this way.
Edge-Cases (only if the definition does not match)
|
Setup
Issue
The @@@-Syntax to create property links does work when the property Has property description is set so some description:
[[Has property description::Testdescription@de]]
It is working if the user has "de" as their language set. However, If a user sets "de-formal" the mouse-over-effect is not working.
Trying to set
[[Has property description::Testdescription@de-formal]]
fails with the massage that is not a valid language code.So I guess this must be some kind of bug. If I cannot set de-formal as language value in monolinual text properties than somehow de-formal (and de-AT, de-CH) should fallback to de.
See also #1865 and #3562
The text was updated successfully, but these errors were encountered: