User talk:SAKryukov/Wiki: Difference between revisions

Line 117:

:::::::::: I'll do this after posting the present reply. I use many browsers and test everything using them. I mostly use Vivaldi, which I highly recommend. It is equivalent to Chrome/Chromium (Blink+V8), just controls/options are a lot better. Unfortunately, for advanced development Blink+V8 is the only option. Even more unfortunately, all Mozilla stuff is left behind precisely because of audio stuff: it has a critical defect in rendering sounds with Web Audio. Opera and newest Microsoft Edge (not even beginning of 2020, but later Blink+V8 (Chromium) version) work fine, but recently I faced and unforgivable defect: it Edge does not support AV1 codec, which is a present-day top video standard of near-impossible fantastic quality, compression level, and responsiveness. — [[User:SAKryukov|SA]], ''Sunday 2020 December 6, 23:32 UTC''

== An incidental wiki syntax note ==

Hello SA, <br>

for people used to Github or GitLab wikis this may come unexpected: the wiki syntax for internal links is <code><nowiki>[[some title]]</nowiki></code> or <code><nowiki>[[Some title]]</nowiki></code>. Both addressing the same target page "Some title": the first character of any page title is automatically forced to uppercase. Subsequent inner underscores (or spaces) in internal links are transformed into one space, outer underscores (or spaces) are ignored. So [[User_talk:SAKryukov]] is the same as [[User talk:SAKryukov]] same as [[user talk:SAKryukov]] same as [[User____talk:SAKryukov]] same as [[__user____talk:SAKryukov__]]. The pipe char within titles (separating the target page on the left, and the text on the right of it) is only needed if the text differs in a significant way from the target page title, for example [[User talk:SAKryukov|other title]] (being <code><nowiki>[[User talk:SAKryukov|other title]]</nowiki></code> in wikitext). Sorry that I abused your talk page title, but it's really the best choice: it has a space in it and it's bolded because we are already here (the self-link feature), so the equivalence is obvious without any need to navigate. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 21:32, 12 December 2020 (UTC)

: Thank you. This is useful, only I did not understand the purpose of your last edit and what would be your advice. From my point of view, it looks like a pleasure of getting rid of underscores. After several attempts to understand what you suggest to change, I simply looked at your signature (and some of my previous links, for that matter and found that it uses a blank space instead of underscore. It makes perfect sense, according to the rules of processing you just explained and the practical merits. So I simply replaced underscores with blank spaces, which is really better. I did not understand why would you add a new section under the same name, and a link to a non-existing page, why you mentioned GitHub and GitLab, and so on. Please, no need to answer these questions unless you think I do something wrong — in essence, everything looks clear anyway.

@@ Line 117: / Line 117: @@
 :::::::::: I'll do this after posting the present reply. I use many browsers and test everything using them. I mostly use Vivaldi, which I highly recommend. It is equivalent to Chrome/Chromium (Blink+V8), just controls/options are a lot better. Unfortunately, for advanced development Blink+V8 is the only option. Even more unfortunately, all Mozilla stuff is left behind precisely because of audio stuff: it has a critical defect in rendering sounds with Web Audio. Opera and newest Microsoft Edge (not even beginning of 2020, but later Blink+V8 (Chromium) version) work fine, but recently I faced and unforgivable defect: it Edge does not support AV1 codec, which is a present-day top video standard of near-impossible fantastic quality, compression level, and responsiveness. &mdash;&nbsp;[[User:SAKryukov|SA]],&nbsp;''Sunday&nbsp;2020&nbsp;December&nbsp;6,&nbsp;23:32&nbsp;UTC''
+== An incidental wiki syntax note ==
+Hello SA, <br>
+for people used to Github or GitLab wikis this may come unexpected: the wiki syntax for internal links is <code><nowiki>[[some title]]</nowiki></code> or <code><nowiki>[[Some title]]</nowiki></code>. Both addressing the same target page "Some title": the first character of any page title is automatically forced to uppercase. Subsequent inner underscores (or spaces) in internal links are transformed into one space, outer underscores (or spaces) are ignored. So [[User_talk:SAKryukov]] is the same as [[User talk:SAKryukov]] same as [[user    talk:SAKryukov]] same as [[User____talk:SAKryukov]] same as [[__user____talk:SAKryukov__]]. The pipe char within titles (separating the target page on the left, and the text on the right of it) is only needed if the text differs in a significant way from the target page title, for example [[User talk:SAKryukov|other title]] (being <code><nowiki>[[User talk:SAKryukov|other title]]</nowiki></code> in wikitext). Sorry that I abused your talk page title, but it's really the best choice: it has a space in it and it's bolded because we are already here (the self-link feature), so the equivalence is obvious without any need to navigate. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 21:32, 12 December 2020 (UTC)
+: Thank you. This is useful, only I did not understand the purpose of your last edit and what would be your advice. From my point of view, it looks like a pleasure of getting rid of underscores. After several attempts to understand what you suggest to change, I simply looked at your signature (and some of my previous links, for that matter and found that it uses a blank space instead of underscore. It makes perfect sense, according to the rules of processing you just explained and the practical merits. So I simply replaced underscores with blank spaces, which is really better. I did not understand why would you add a new section under the same name, and a link to a non-existing page, why you mentioned GitHub and GitLab, and so on. Please, no need to answer these questions unless you think I do something wrong — in essence, everything looks clear anyway.