Thanks for the technical details, Bartosz!
One would hope (but should confirm) that link prefixes are treated with the
same basic logic as link postfixes/trails, so assuming pre- and post-link
trails are enabled, "pre[[target]]post" is all linked, but
"pre[[target|linktext]]post" is only linked
On 2018-10-15 16:34, Trey Jones wrote:
I'm not sure how much impact it would have on existing link specifications
to make the change, but I think MGChecker has a good solution. The
"[[target|linktext]]extra" format allows you to specify exactly what part
of the text should have a link, while
I'm not sure how much impact it would have on existing link specifications
to make the change, but I think MGChecker has a good solution. The
"[[target|linktext]]extra" format allows you to specify exactly what part
of the text should have a link, while "[[target]]extra" would be understood
as a
> MZMcBrider wrote:
> I'm not sure I understand. I would expect a link trail with
> "[[Examples|Example]]s" since there is a link trail with "[[Example]]s".
> I'm not sure why anyone would associate link trail behavior with the presence
> or lack of a pipe character. The defining characteristic
MGChecker wrote:
>> Links using the pipe-form should not have the link target inflected.
>>This is important, as this is the natural escape route if inflection
>>gives wrong target for whatever reason.
>
>This is what I think is particularly odd about linktrails: Why do links
>like
ch-l] non-obvious uses of in your language
In my opinion we should try to first process the whole linked phrase by
inflection aka affix rules, and if that fails aka no link target can be found –
then and only then should regexps form prefix and linktrails be applied. If
applying prefix or l
The relevant Parsoid feature request for having VE use linktrails is
https://phabricator.wikimedia.org/T50463 since in general Parsoid just
generates [[Book|books]] when VE gives it `books`.
If VE gives Parsoid `books` it will assume that's what
the author actually meant, and will generate
... And, more importantly, its form doesn't say "separate the trail from
the link". Just like , it only *happened* to do it (I tried on
Wikipedia, and it doesn't do it now).
The point I'm trying to make in this thread is that happens to do
certain things other than showing wiki syntax without
Alas, no longer valid in XML or HTML5. (Although HTML5 will still
parse it as an empty comment, but with a "incorrectly-opened-comment"
error.
--
Brian
On Sat, Oct 6, 2018 at 6:57 AM Chad wrote:
>
> Found it :)
>
> https://www.w3.org/MarkUp/SGML/sgml-lex/sgml-lex
>
> Search for "empty comment
Found it :)
https://www.w3.org/MarkUp/SGML/sgml-lex/sgml-lex
Search for "empty comment declaration" :)
-Chad
On Fri, Oct 5, 2018, 11:50 PM Chad wrote:
> I'm personally a fan of .
>
> I came across it years ago--it's a null comment. Can't find the reference
> at the moment though.
>
> -Chad
>
I'm personally a fan of .
I came across it years ago--it's a null comment. Can't find the reference
at the moment though.
-Chad
On Thu, Oct 4, 2018, 2:25 PM Daniel Kinzler wrote:
> Am 04.10.2018 um 18:58 schrieb Thiemo Kreuz:
> > The syntax "[[Schnee]]reichtum" is quite common in the
> >
In my opinion we should try to first process the whole linked phrase by
inflection aka affix rules, and if that fails aka no link target can be
found – then and only then should regexps form prefix and linktrails be
applied. If applying prefix or linktrails creates a word that can be
inflected,
T129778
On Fri, Oct 5, 2018 at 3:59 PM Dan Garry wrote:
> On Thu, 4 Oct 2018 at 23:29, John Erling Blad wrote:
>
> > Usually it comes from user errors while using VE. This kind of errors are
> > quite common, and I asked (several years ago) whether it could be fixed
> in
> > VE, but was told
בתאריך יום ו׳, 5 באוק׳ 2018 ב-16:59 מאת Dan Garry <dga...@wikimedia.org
>:
>
> On Thu, 4 Oct 2018 at 23:29, John Erling Blad wrote:
>
> > Usually it comes from user errors while using VE. This kind of errors
are
> > quite common, and I asked (several years ago) whether it could be fixed
On Thu, 4 Oct 2018 at 23:29, John Erling Blad wrote:
> Usually it comes from user errors while using VE. This kind of errors are
> quite common, and I asked (several years ago) whether it could be fixed in
> VE, but was told "no".
>
I'd really appreciate it if you could give me more information
On Thu, Oct 4, 2018 at 2:25 PM Daniel Kinzler
wrote:
> Or how about {{}} for "this is a syntactic element, but it does nothing"?
Just make a template with a nice name ( {{~}} or something) and put the
nowiki in that.
___
Wikitech-l mailing list
Only thing more dangerous than running a bot on nowiki is running a bot on
dewiki.
Nope, newer touches dewiki.
On Fri, Oct 5, 2018 at 12:49 AM Roul P. wrote:
> Interesting, today this was topic in the German main forum:
>
>
Interesting, today this was topic in the German main forum:
https://de.wikipedia.org/wiki/Wikipedia:Fragen_zur_Wikipedia#Anwendung_von__in_Bildunterschriften
Today there are also more than one user indefinite blocked, which only
removed https://de.wikipedia.org/wiki/Benutzer:Entgr%C3%A4ten40
Am
We have the same in Norwegian, but linking on part of a composite is almost
always wrong. Either you link on the whole composite or no part of the
composite. If you link on a part of a composite, then in nearly all cases I
have seen the link is placed on the wrong term.
Some examples on what
-{}- is already commonly used on LanguageConverter wikis for "this is a
syntactic element but does nothing except separate a word".
The preprocessor already understands it on all wikis, as well. (But then
we explicitly serialize it to literally `-{}-` if your content language
doesn't have
Am 04.10.2018 um 18:58 schrieb Thiemo Kreuz:
> The syntax "[[Schnee]]reichtum" is quite common in the
> German community. There are not many other ways to achieve the same:
> or can be used instead.[1] The later is often the
> better alternative, but an auto-replacement is not possible. For
>
Am 04.10.2018 um 18:24 schrieb Lucas Werkmeister:
> I’m not an expert on dewiki, but I assume they still want word-ending links
> for simple stuff like [[Gesetz]]e (plural), [[Finger]]s (genitive). I would
> guess these cases are still more common than the long compound words where
> the trick is
The problem with all anti-linktrail practices is that they make search (or
search and replace) in the source very hard. This relies both to bot owners
and humans who use the insource: regex search engine.
I think a brand new approach would be necessary.
For example, [[foo]]bar would behave as now,
I once wrote some very, very silly code that kind of works for Hebrew, and
could possibly be adapted to other languages:
https://github.com/amire80/znavot
Pull requests welcome :)
בתאריך יום ה׳, 4 באוק׳ 2018, 19:59, מאת Thiemo Kreuz <
thiemo.kr...@wikimedia.de>:
> Hey!
>
> The syntax
Hey!
The syntax "[[Schnee]]reichtum" is quite common in the
German community. There are not many other ways to achieve the same:
or can be used instead.[1] The later is often the
better alternative, but an auto-replacement is not possible. For
example, "[[Bund]]estag" must become
I’m not an expert on dewiki, but I assume they still want word-ending links
for simple stuff like [[Gesetz]]e (plural), [[Finger]]s (genitive). I would
guess these cases are still more common than the long compound words where
the trick is used.
Am Do., 4. Okt. 2018 um 17:44 Uhr schrieb Amir E.
I'm really not an expert on German. However, I have been slowly analyzing
common trails in some other languages with purpose of doing smarter link
trailing some day. It's a very crazy and long term pet project :) In
theory, I could do it for German, too.
בתאריך יום ה׳, 4 באוק׳ 2018, 18:39, מאת C.
https://hu.wikipedia.org/w/index.php?title=Grafikus_matroid=prev=20406147
illustrates another use: separating - and { in the unusual case where this
string is wanted and you *don't* want language converter markup. ie
`-{foo}-` is different from `-{foo}-`. You don't usually notice
this because
Here is a list of removals. :-)
https://hu.wikipedia.org/w/index.php?title=Speci%C3%A1lis:Szerkeszt%C5%91_k%C3%B6zrem%C5%B1k%C3%B6d%C3%A9sei/BinBot=20180912205000=BinBot=28
Amir E. Aharoni ezt írta (időpont: 2018.
okt. 4., Cs, 16:47):
> Thanks. Can you please give some particular examples?
>
>
Thanks. Can you please give some particular examples?
בתאריך יום ה׳, 4 באוק׳ 2018, 17:41, מאת Bináris :
> Amir E. Aharoni ezt írta (időpont: 2018.
> okt. 4., Cs, 16:18):
>
> >
> > This sentence shows the template used at the end.{{Citation
> > needed|reason=Reliable source needed for the whole
Amir E. Aharoni ezt írta (időpont: 2018.
okt. 4., Cs, 16:18):
>
> This sentence shows the template used at the end.{{Citation
> needed|reason=Reliable source needed for the whole sentence|date=October
> 2018}}
>
> However, has less trivial use cases, that are not quite the same
> as
Hi,
In MediaWiki, the tag was created for writing characters without
having them interpreted as wiki syntax. An obvious and direct use case for
this is writing help pages about editing wiki pages in wiki syntax, for
example:
Writing '''words between three apostrophes''' will show
them in bold
32 matches
Mail list logo
