Talk:BSicon
WikiProject BSicon (discussions) | ||||
---|---|---|---|---|
Local projects: | ||||
Deutsch | English | Esperanto | Español | Français |
Italiano | 日本語 | 한국어 | Nederlands | Norsk (bokmål) |
Português | Russian/Русский | Svenska | 中文 |
| ||
Threads older than 1 year may be archived. |
Talk pages
[edit]In an effort to consolidate all of the BSicon discussions, please introduce new topics on one of these pages:
- Talk:BSicon/New icons and icon requests
- Talk:BSicon/Renaming
- Talk:BSicon/Renaming/ABZ (
ABZql
/ABZl+34
& related icons) - Talk:BSicon/Renaming/BUE (
BUE
& related icons) - Talk:BSicon/Renaming/k (
kHST2
/kABZql
& related icons) - Talk:BSicon/Renaming/SPL (
SPLa
/SPLe
& related icons) - Talk:BSicon/Renaming/Canals (
uLOCKSu
/WASSER
& related icons) - Talk:BSicon/Renaming/Roads (
RP2
/RA
& related icons)
- Talk:BSicon/Renaming/ABZ (
- ↳ Talk:BSicon/Redirects
- Talk:BSicon/Icon topology and semantics
- Talk:BSicon/Icon geometry and SVG code neatness
- Talk:BSicon/Icon geometry and SVG code neatness/Formations (
hSTRa
/tSTRa
& related icons) - Talk:BSicon/Icon geometry and SVG code neatness/Drawbridges (
DBK
/HBKq
etc.)
- Talk:BSicon/Icon geometry and SVG code neatness/Formations (
- Talk:BSicon/Obsolete and deletions
- Talk:BSicon/Colors (RGBs, namings, categories, etc.)
- Talk:BSicon/Categorization
- {{}} Talk:BSicon/Templates
- Talk:BSicon/Canals
More talks can be found at:
Project talk
[edit]Category talk
[edit]- Category talk:BSicon/railway
- Category talk:Icons for railway descriptions/border
- Category talk:Icons for railway descriptions/hub
- Category talk:Icons for railway descriptions/legende
- Category talk:Icons for railway descriptions/arrow
- Category talk:BSicon/railway/stations
- Category talk:Icons for railway descriptions/parallel railways
- Category talk:Icons for railway descriptions/parallel railways/loop
- Category talk:Icons for railway descriptions/experimental
- Category talk:Icons for railway descriptions/experimental/borders
- Category talk:Icons for railway descriptions/experimental/platform
- Category talk:BSicon/road–rail/crossing
- Category talk:Icons for motorway descriptions/generic/crossing rail
- Category talk:Icons for railway descriptions/text/experimental
File talk
[edit]- File talk:BSicon utSKRZ-G2o.svg
- File talk:BSicon uemTHSTACCu.svg
- File talk:BSicon PARKING.svg
- File talk:BSicon lMENDEa.svg
- File talk:BSicon STR+lBUEq.svg
- File talk:BSicon uhkLSTR.svg
There may be more. Some of these may refer to more than a single file, but to the whole set they belong to; those discussions should be moved here.
Wikipedia talk
[edit]Note that these pages should be used for discussions about the Catalog pages, not specific BSicons.
- en:Wikipedia talk:Route diagram template/Catalog of pictograms
- en:Wikipedia talk:Route diagram template/Catalog of pictograms/straight tracks
- en:Wikipedia talk:Route diagram template/Catalog of pictograms/stations
- en:Wikipedia talk:Route diagram template/Catalog of pictograms/parallel stations
- en:Wikipedia talk:Route diagram template/Catalog of pictograms/branchings
- en:Wikipedia talk:Route diagram template/Catalog of pictograms/junctions
- en:Wikipedia talk:Route diagram template/Catalog of pictograms/parallel junctions
- en:Wikipedia talk:Route diagram template/Catalog of pictograms/parallel crossings and crossovers
- en:Wikipedia talk:Route diagram template/Catalog of pictograms/others
- en:Wikipedia talk:Route diagram template/Catalog of pictograms/generic roads
- en:Wikipedia talk:Route diagram template/Catalog of pictograms/watercourses
Deletion requests
[edit]- (See discussion page)
- more at [1], [2] and [3]
New version of BSicon_uhSTRae.svg
[edit]I need a version of this bridge that obscures whatever is beneath the bridge, so I added a white square below the parapets, but otherwise it appears identical. I cannot upload it, as it says I was not the original author. It suggests giving it a new name. What new name would anyone suggest for an icon that looks identical to an existing one? Bob1960evens (talk) 14:35, 23 January 2024 (UTC)
- As a temporary solution, I have uploaded it as (
uehSTRae
), but it doesn't appear on the table of icons, because the other versions sit on a line labelled BRUCKE. Bob1960evens (talk) 14:51, 23 January 2024 (UTC)- I note that the (
uhSTRae
) icon displays because there is a redirect for uBRUCKE, but cannot find how to create a redirect. Bob1960evens (talk) 11:36, 25 January 2024 (UTC)
- I note that the (
- The correct filename is (
uhMSTRae
),M
signifying the the icon contains masking – which, by the way, should be #F9F9F9 rather than white. Useddenim (talk) 03:59, 30 January 2024 (UTC)
- The correct filename is (
BSicon/Catalogue: exm group of prefixes
[edit]I'm reading BSicon/Catalogue (its talk page redirects here), trying to make sense of the fine details on the rules for the various groups of prefixes. I can't help but coming to the conclusion that what is presented as one exm group is really two groups: one group with letters ex, and a second group with letters mfgu. It is in particular confusing that the description in the Naming logic section does not even hint at the fact that f, g, and u are possible letters here! Consider (uexgKRZo
) and (gexuKRZo
).
I'd suggest splitting the exm group, description-wise. Also, in view of ufg being allowed in two different groups: is there ever a case in which two of ufg appear before ex? If not, then the description of the first ufg group could be tightened to have at most one of the prefixes (right now it says ‘zero or more’). 88.129.117.158 13:18, 5 July 2024 (UTC)
Best practice testing for icon existence?
[edit]I find a frequent headache when coding line diagrams is that icons I'd like to use don't exist. Concrete example: in BSicon/Catalogue/formations#Left & right variants the table lists lMKRZo-L
, but when I try to use it in a diagram, I only get those unreadable blue scribbles :-( which apparently signal “file not found”. I suppose one remedy could be to craft the icon in question, but (apart from the fact that not everybody have the SVG skills needed) when I'm in a diagram coding mindset I don't want to constantly switch to an icon designing mindset. Sometimes it makes more sense to change the diagram layout, or perhaps use overlays (although not in the case cited) to construct highly specialised combinations. Moreover, just previewing the diagram one is working on isn't always the best way to spot missing icons; even if the blue scribbles are noticeable, it can be quite difficult to pinpoint which icon is generating the error.
I find that for complex diagrams I prefer to work off-line, in a text editor. In that case, I can moreover use scripting (in the editor) to scan the diagram and alert me of missing icon errors before I copy the code into a browser to have it rendered. But given a purported icon ID, what would be the best way of testing whether that icon exists? One approach seems to be to construct the corresponding URL (e.g. https://commons.wikimedia.org/wiki/File:BSicon_lMKRZo-L.svg
) and then fetch that—this gives me an OK (200) response if the icon exists and a not-found (404) response if it doesn't. However, those URLs don't refer to the icon graphics as such, but (despite the file extension) to an HTML page with lots of detail information about the file, for example lists of pages on various wikis that make use of this icon—for Commons to compile all that information is definitely overkill for this use-case! (I can reduce network load by switching HTTP method from GET to HEAD, but that still requires the server to say how long the body produced in response to a GET would be, so Commons still have to do all the work of producing the page.)
Is there any alternative? Might Wikidata (a.k.a. the “Structured data” tab) be used instead? 88.129.117.158 10:00, 8 July 2024 (UTC)
- FWIW, I created (
lMKRZo-L
) for you (and also (lKRZo-L
) while I was at it). Useddenim (talk) 16:26, 8 July 2024 (UTC)- Sadly, not worth all that much to me at the moment, since my main point about that icon was that merely being listed in the catalogue is no evidence an icon exists. But there is certainly a positive probability someone will find it useful. 88.129.117.158 09:12, 12 July 2024 (UTC)
Busway icons for track diagrams
[edit]I am considering making a busway track diagram outside of w:Template:South Station (subway), but I don't know if (uSTR
) or (RP2
)/ (vRP1
) should be used. On one hand, considering that busways are only for buses, it might make sense to use (uSTR
). But on the other hand, busways are not railways as they are paved roadways, so it might also make sense to use (RP2
). Alternatively, an entirely new set of icons could be created for busways, including busway junction icons and busway-LRT/tram icons. What are your suggestions? AlphaBeta135talk 01:10, 11 September 2024 (UTC)
- @AlphaBeta135: TBH, the answer is "whatever looks right to you". I would suggest taking a look at the pages using Template:Bus-routemap for ideas, as there is no consistency. And another thought I had would be to use this overlay: (
GRZ white
※uSTR
) to differentiate BRT from rail transit. Useddenim (talk) 01:43, 12 September 2024 (UTC)
Anonymous reversion without comment of edit involving link wording
[edit]I recently made an edit which I believe improves the accessibility of the links. Specifically, I removed several "here" links and replaced them with links that say what is being linked to. Blind people often navigate a page by getting a list of links, and "here" links are meaningless. Also, I as a currently sighted person am often confused by "here" links and wind up clicking the wrong link. However, my edit was reverted without explanation by a non-logged-in editor. Since they weren't logged in, and I cannot count on their IP address being durable, I can't contact them on their talk page to find out why they reverted my edit.
I plan on reverting the reversion. I invite the reverting editor to discuss their concerns here or at least in their log note rather than reverting anonymously and without comment. If my edit is reverted again without comment, I pledge not to get into an edit war but rather will raise the issue on Request for Comment.