Change Details

**Feature summary** (what you would like to be able to do and where): Scributno should provide an interface to fetch the language of the current page. **Use case(s)**: I am writing a Lua module for the Community Wishlist Survey, which has translatable pages on Meta. When viewing these translatable pages directly, I do not want some things to appear. One naive solution is to compare the subpage name with the value of the page language. If they are the same, we can assume (99% of the time) that we're on a translatable page. Currently I cannot get the page language through Scribunto. Instead I must pass in `{{PAGELANGUAGE}}` when the module is invoked. **Benefits**: This would allow module programmers to easily fetch the page language from Lua code, allowing [[ https://meta.wikimedia.org/w/index.php?search=insource%3A%2FPAGELANGUAGE%2F&title=Special:Search&profile=advanced&fulltext=1&ns10=1 | various templates on Meta ]], Commons, and other multilingual wikis could be re-implemented in Lua. We are able to fetch many properties about the current page, such as the content model, and even the content itself. I think being able to fetch the page language would be a natural fit for the already somewhat rich [[ https://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#Language_library | language library ]] that Scribunto offers. I am tempted to suspect it only wasn't added because `{{PAGELANGUAGE}}` wasn't introduced (~2017) until after Scribunto was deployed.

**Feature summary**: Scributno should provide an interface to fetch the language of the current page. **Use case(s)**: I am writing a Lua module for the Community Wishlist Survey, which has translatable pages on Meta. When viewing these translatable pages directly, I do not want some things to appear. One naive solution is to compare the subpage name with the value of the page language. If they are the same, we can assume (99% of the time) that we're on a translatable page. Currently I cannot get the page language through Scribunto. Instead I must pass in `{{PAGELANGUAGE}}` when the module is invoked. **Benefits**: This would allow module programmers to easily fetch the page language from Lua code, allowing [[ https://meta.wikimedia.org/w/index.php?search=insource%3A%2FPAGELANGUAGE%2F&title=Special:Search&profile=advanced&fulltext=1&ns10=1 | various templates on Meta ]], Commons, and other multilingual wikis could be re-implemented in Lua. We are able to fetch many properties about the current page, such as the content model, and even the content itself. I think being able to fetch the page language would be a natural fit for the already somewhat rich [[ https://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#Language_library | language library ]] that Scribunto offers. I am tempted to suspect it only wasn't added because `{{PAGELANGUAGE}}` wasn't introduced (~2017) until after Scribunto was deployed.

**Feature summary** (what you would like to be able to do and where): Scributno should provide an interface to fetch the language of the current page. **Use case(s)**: I am writing a Lua module for the Community Wishlist Survey, which has translatable pages on Meta. When viewing these translatable pages directly, I do not want some things to appear. One naive solution is to compare the subpage name with the value of the page language. If they are the same, we can assume (99% of the time) that we're on a translatable page. Currently I cannot get the page language through Scribunto. Instead I must pass in `{{PAGELANGUAGE}}` when the module is invoked. **Benefits**: This would allow module programmers to easily fetch the page language from Lua code, allowing [[ https://meta.wikimedia.org/w/index.php?search=insource%3A%2FPAGELANGUAGE%2F&title=Special:Search&profile=advanced&fulltext=1&ns10=1 | various templates on Meta ]], Commons, and other multilingual wikis could be re-implemented in Lua. We are able to fetch many properties about the current page, such as the content model, and even the content itself. I think being able to fetch the page language would be a natural fit for the already somewhat rich [[ https://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#Language_library | language library ]] that Scribunto offers. I am tempted to suspect it only wasn't added because `{{PAGELANGUAGE}}` wasn't introduced (~2017) until after Scribunto was deployed.