Alaettin Çakıcı Sedat Peker Ali Yasak Dündar Kılıç Savaş Buldan Ömer Lütfü Topal Sami Hoştan
test section
lity. We likely don't want to link to the exact spot in mid-sentence where the redirect-from term was used in the article, but rather to the section containing it, for context. We do sometimes have cases, but these are generally to tables, list items, or other discrete blocks of content that just don't happen to have separate We likely don't want to link to the exact spot in mid-sentence where the redirect-from term was used in the article, but rather to the section containing it, for context. We do sometimes have cases, but these are generally to tables, list items, or other discrete blocks of content that just don't happen to have separate We likely don't want to link to the exact spot in mid-sentence where the redirect-from term was used in the article, but rather to the section containing it, for context. We do sometimes have cases, but these are generally to tables, list items, or other discrete blocks of content that just don't happen to have separate We likely don't want to link to the exact spot in mid-sentence where the redirect-from term was used in the article, but rather to the section containing it, for context. We do sometimes have cases, but these are generally to tables, list items, or other discrete blocks of content that just don't happen to have separate We likely don't want to link to the exact spot in mid-sentence where the redirect-from term was used in the article, but rather to the section containing it, for context. We do sometimes have cases, but these are generally to tables, list items, or other discrete blocks of content that just don't happen to have separate subheadings. Another problem with auto-anchoring from a template like be that if the page already has a heading (or other anchor) by this name, and the template is inserted above it (e.g., because the term is first used in the lead section in the article, despite having its own entire section lower down in the article body), then the template would "usurp" all incoming links to that section (the target ID of which would be changed on the fly to something like foo-2
We likely don't want to link to the exact spot in mid-sentence where the redirect-from term was used in the article, but rather to the section containing it, for context. We do sometimes have cases, but these are generally to tables, list items, or other discrete blocks of content that just don't happen to have separate subheadings. Another problem with auto-anchoring from a template like be that if the page already has a heading (or other anchor) by this name, and the template is inserted above it (e.g., because the term is first used in the lead section in the article, despite having its own entire section lower down in the article body), then the template would "usurp" all incoming links to that section (the target ID of which would be changed on the fly to something like foo-2
I meant
this discussion (I made a one-letter typo, but the discussion isn't that important).
Yes, I guess I meant #foo anchors (I have only ever added them with {{
anchor}}).
So you agree that such a template (and sure, my name was just off-the-cuff) would be useful as a way to bold and provide a kind of inline documentation of the reason for the bolding.
My thought about a secondary role of providing an automatic anchor was to try to "encourage" the use of anchors for redirects. Of course, I mean the kind of redirects that should go to certain sections (not redirects for different spellings, capitalizations, and the like for which the correct target is the article itself and bolding is not applicable). I don't have any stats, but I would guess that a very large percentage of redirects that could/should go to a sub-section just go to the article. And many that once went to a sub-section (via direct link to the header) are broken as evidenced by the report. So more anchors are good. And making it easier to add anchors would result in more anchors. I get your point that sometimes the anchor location should be a different section that the first bolded use - the template would need to have a |make anchor=yes/no to handle this (we would have to pick a default).
As far as the other problem you mentioned - that the anchor should be put before the section header, not mid-section where the term is bolded - I haven't experienced the operation you described. I just experimented and if I put an anchor in the middle of a section of text, viewing a link to the anchor for me displays the entire section (but not the header (title)). It does not go to the "exact spot mid-sentence" like you said. Is this unique to my browser perhaps? If what I see is repeatable and universal, although not ideal, it may better than no anchor. Maybe we could get a bot to find these "auto-mid-section-anchors" added by this template and just move the anchor to before the prior section heading.
Alaettin Çakıcı Sedat Peker Ali Yasak Dündar Kılıç Savaş Buldan Ömer Lütfü Topal Sami Hoştan
test section
lity. We likely don't want to link to the exact spot in mid-sentence where the redirect-from term was used in the article, but rather to the section containing it, for context. We do sometimes have cases, but these are generally to tables, list items, or other discrete blocks of content that just don't happen to have separate We likely don't want to link to the exact spot in mid-sentence where the redirect-from term was used in the article, but rather to the section containing it, for context. We do sometimes have cases, but these are generally to tables, list items, or other discrete blocks of content that just don't happen to have separate We likely don't want to link to the exact spot in mid-sentence where the redirect-from term was used in the article, but rather to the section containing it, for context. We do sometimes have cases, but these are generally to tables, list items, or other discrete blocks of content that just don't happen to have separate We likely don't want to link to the exact spot in mid-sentence where the redirect-from term was used in the article, but rather to the section containing it, for context. We do sometimes have cases, but these are generally to tables, list items, or other discrete blocks of content that just don't happen to have separate We likely don't want to link to the exact spot in mid-sentence where the redirect-from term was used in the article, but rather to the section containing it, for context. We do sometimes have cases, but these are generally to tables, list items, or other discrete blocks of content that just don't happen to have separate subheadings. Another problem with auto-anchoring from a template like be that if the page already has a heading (or other anchor) by this name, and the template is inserted above it (e.g., because the term is first used in the lead section in the article, despite having its own entire section lower down in the article body), then the template would "usurp" all incoming links to that section (the target ID of which would be changed on the fly to something like foo-2
We likely don't want to link to the exact spot in mid-sentence where the redirect-from term was used in the article, but rather to the section containing it, for context. We do sometimes have cases, but these are generally to tables, list items, or other discrete blocks of content that just don't happen to have separate subheadings. Another problem with auto-anchoring from a template like be that if the page already has a heading (or other anchor) by this name, and the template is inserted above it (e.g., because the term is first used in the lead section in the article, despite having its own entire section lower down in the article body), then the template would "usurp" all incoming links to that section (the target ID of which would be changed on the fly to something like foo-2
I meant
this discussion (I made a one-letter typo, but the discussion isn't that important).
Yes, I guess I meant #foo anchors (I have only ever added them with {{
anchor}}).
So you agree that such a template (and sure, my name was just off-the-cuff) would be useful as a way to bold and provide a kind of inline documentation of the reason for the bolding.
My thought about a secondary role of providing an automatic anchor was to try to "encourage" the use of anchors for redirects. Of course, I mean the kind of redirects that should go to certain sections (not redirects for different spellings, capitalizations, and the like for which the correct target is the article itself and bolding is not applicable). I don't have any stats, but I would guess that a very large percentage of redirects that could/should go to a sub-section just go to the article. And many that once went to a sub-section (via direct link to the header) are broken as evidenced by the report. So more anchors are good. And making it easier to add anchors would result in more anchors. I get your point that sometimes the anchor location should be a different section that the first bolded use - the template would need to have a |make anchor=yes/no to handle this (we would have to pick a default).
As far as the other problem you mentioned - that the anchor should be put before the section header, not mid-section where the term is bolded - I haven't experienced the operation you described. I just experimented and if I put an anchor in the middle of a section of text, viewing a link to the anchor for me displays the entire section (but not the header (title)). It does not go to the "exact spot mid-sentence" like you said. Is this unique to my browser perhaps? If what I see is repeatable and universal, although not ideal, it may better than no anchor. Maybe we could get a bot to find these "auto-mid-section-anchors" added by this template and just move the anchor to before the prior section heading.