Jump to content

ထႅမ်းပလဵတ်ႉ:prefixusex/documentation

လုၵ်ႉတီႈ ဝိၵ်ႇသျိၼ်ႇၼရီႇ မႃး
ၽိုၼ်လိၵ်ႈၵူႈမိုဝ်း တွၼ်ႈတႃႇထႅမ်းပလဵတ်ႉ:prefixusex[မႄးထတ်း]
တီႈၼႃႈလိၵ်ႈၼႆႉ ၶဝ်ႈပႃးဝႆႉ ၶေႃႈမုၼ်း လၢႆးၸႂ်ႉတိုဝ်းပိူင်ထၢၼ်ႈလွင်ႈၵွင်ႉသိုပ်ႇ ဢိၼ်ႇတႃႇဝီႇၶီႇ လႄႈ ၸိူဝ်းပဵၼ် လွင်ႈၼႄပၼ် ထႅမ်းပလဵၵ်ႉ ၼၼ်ႉယဝ်ႉ။

This template creates usage examples for prefix entries in the format prefix- + wordprefixed word. More complex entries are also possible, e.g.:

prefix- + word1 + word2prefixed word
prefix1- + word1prefixed word 1 + -suffix2suffixed word 2
word1 (qualifier) + word2combined word

ပႃႇရႃႇမီႇတႃႇ

[မႄးထတ်း]
  • This template takes almost exactly the same parameters as {{affixusex}} and its shortcut {{afex}}; see the documentation of that template for more information. There are only slight differences between the two:
  1. When {{prefixusex}}/{{prefex}} is used, the parameter |altaff= can also be named |altpref=, for compatibility purposes.
  2. When interpolating a prefix before the first component (taken from the |altaff= parameter or the page name), {{affixusex}} checks that the prefix being inserted actually looks like a prefix (i.e. it ends with a hyphen and doesn't begin with a hyphen) before being interpolated. {{prefixusex}} does not make this extra check. This may matter in languages where prefixes are not normally followed by a hyphen (e.g. East Asian languages), or are followed by a different character (e.g. Hebrew and Arabic). For Latin-script languages, it usually doesn't matter.

In practice, these are very minor differences, and it is recommended to use {{affixusex}}/{{afex}} in all circumstances; {{prefixusex}} and {{suffixusex}} are maintained largely for compatibility.

တူၺ်းပႃး

[မႄးထတ်း]