Search results

{{shortcut|FP:LANG}} <nowiki>{{</nowiki>lang|en|page=''బేస్ పేజీ పేరు''<nowiki>}}</nowiki>

{{shortcut|FP:LANG}} <nowiki>{{</nowiki>lang|en|page=''Base page name''<nowiki>}}</nowiki>

- add arabic, greek, hebrew, latin2, turkish lang support

lang en_US

{{lang|pt-br|page=Punknova_pt-br}}

{{lang|en|zh-cn|page=Architectures/ARM/CrossToolchain}}

lang en_US

* idea of extending system-config-language to lang support and langpack configuration

{{shortcut|FP:LANG}} <nowiki>{{</nowiki>lang|en|page=''Base page name''<nowiki>}}</nowiki>

...d installed fonts that fontconfig thinks support a language, try "fc-list :lang=''xx_YY''" where ''xx_YY'' is replaced by the language locale codes. ...a's lang-table file in tabbed format. Once a language name is added in the lang-table file and new package is built, we can use anaconda in that language.

# Proceed with an @everything all-lang installation

== file-not-in-%lang == %files -f foo.lang

{{shortcut|FP:LANG}} <nowiki>{{</nowiki>lang|en|page=''Base page name''<nowiki>}}</nowiki>

=== Lang packs ===

<!--{{shortcut|FP:LANG}} --> <nowiki>{{</nowiki>lang|en|page=''Основное имя странцы''<nowiki>}}</nowiki>

...tscripts; this seemed like a bad idea. When considering that, I thought of lang-table, and wondered 'how could we get rid of that'. * lang-table (a custom anaconda file)

{{lang|en|zh-cn|page=Zh}}

{{lang|pt-br|page=Myanmar3_fonts_pt-br}}

{{lang|en|zh-cn|page=Autotest}}

...d installed fonts that fontconfig thinks support a language, try "fc-list :lang=''xx_YY''" where ''xx_YY'' is replaced by the language locale codes. ...a's lang-table file in tabbed format. Once a language name is added in the lang-table file and new package is built, we can use anaconda in that language.