User:Dodde/t

Various ways to handle undefined :

Simplest and most basic:


 * Syntax: FL-link
 * Equivalent:
 * Usage: With this syntax the internal link has to be the same as the FL link. It is not possible to have a different text in the internal link. This will probably be used in 95% of all cases.


 * One might want to have different text on the internal link compared to the internal link itself.
 * One might want to make an FL-link pointing to an FL-wikt with another pagename than being used on the internal wikt.
 * This is possible with following code:

|}}
 * Syntax: FL-link
 * Syntax: FL-link
 * The problem with this code is that if you want to type an internal link text, you have to give the arguments for FL-link aswell as internal link, even if they are same.
 * It's however not very intuitive. There are various ways to come around this. One way is to att the parameter text= for internal link text. The code will then look likt this (not tested):


 * Syntax: FL-link
 * Syntax: FL-link
 * Syntax: FL-link
 * Syntax: FL-link
 * Syntax: FL-link
 * Syntax: FL-link
 * What is good with this is that is is intutive and is easy to not do wrong.

Consider here is yet not discussed:
 * how to add parameters for gender
 * how to add the possibility to link to Chinese Wiktionary which need to be linked to in a different way.
 * how to state if the FL-link should exist, be red-linked, or be blue-linked (linking to non-existing wiktionaries will never be a choice even if the template is used for all translations with no exceptions. I would suggest using the template without the parameter link= should create the translation with no link to the FL-Wiktionary. Then the argument link=blue and link=red respectively for the different colours of the link. If it is decided that only existing pages on FL-Wiktionaries should be linked to, I would suggest simply "link=" to be enough to create the blue link.
 * to get the best from two worlds, we could have two templates undefined and (alternatively  with undefined being the most basic template similar to the one displayed in the top, while / could contain all the complex structures. Since this template will be used not so often, the complexity won't be much of a problem. If gender is decided to be included, it should be added in the simple template, aswell as the link= parameter if it is decided to use a template for all translations, with no exception.