XBMC will be renamed to Kodi for v14. Read here for more details

User talk:Udepub

From XBMC
Revision as of 04:35, 20 April 2013 by Udepub (Talk)

Jump to: navigation, search

Contents

1 Your changes to TVshows files refuse to be added.

Isn't the fourth reason you added as shows refuse to be added - the difference and definition between Aired order and DVD order setting in scraper? I think it is.--uNiversal 11:47, 11 April 2013 (EDT)

I think it's more about region differences. I just added Futurama. Aired and DVD order is the same at TTVDB. Though my DVD boxset differ quite a lot from the site. Season 1 has 13 episodes, TTVDB has 9 and so on. --udepub 12:09, 11 April 2013 (EDT)

Then say that, TVDB has always been quirky that way (tm), Yes according to futurama website it does have 13 eps for season 1 http://www.comedycentral.com/episodes/70pli7/futurama-fry-and-the-slurm-factory-season-1-ep-113 perhaps you want to point to that website and post at tvdb forums this fact, and reconsider your wording on xbmc wiki so its not misleading.
However even IMDB has 9 episodes for season 1 and so does http://futurama.wikia.com/wiki/Season_1_%28broadcast%29, also every other website that has anything futuramic episodic is like tvdb says. still hardly a scraper issue when its a generally accepted format on other online databases.--uNiversal 13:30, 11 April 2013 (EDT)
I've removed some of the negative words about scrapers. I think at least something should be there about this as it's not really easy to understand why just some of the episodes get scraped. --udepub 17:54, 11 April 2013 (EDT)
Yes I agree the information should be there, warning people that what is on online databases is not necessarily the order they expect and perhaps point to some workaround. with a couple examples If you have any good creative around this please feel free to document the fix..--uNiversal 17:57, 11 April 2013 (EDT)


2 How to name filenames in text (e.g. *.xml, .xml, xml or XML file)?

There doesn't seem to be any consistent rule. E.g. I've seen "*.xml file" and ".xml file". I like XML file better.

How about the XBMC log file?

E.g. I've seen "xbmc.log file", "xbmc log file" Maybe in this case one of the two would be better than "XBMC log file". I guess the first one?


It depends on the context. Basically, which ever is easier for the user to understand for that situation. For example, in a step-by-step section, I like to make things sound very literal and will use less formal names, or in a way that makes it easier for someone to find what they need. So there I will often say "get the XBMC.log file" because the file is actually called XBMC.log. While in some other place that's just giving general information, saying "XBMC's log file" is fine too.


One tricky part with XML files is that we talk about files that end in .xml, as well as files that end in other extensions, but are still considered XML files (such as NFO files).


Another example is saying XBMC v12 vs saying Frodo. Sometimes I will even combine the two, so that it makes sense for people who've gotten information from multiple sources, or heard someone use one or the other terms. Saying just v12 is a bit easier to understand, because you know it's a version number, but it could also be confusing because we often talk about version numbers of add-ons, other apps, etc. When you say "Frodo" people know you're talking about XBMC, but new users might not know that. It can be tricky.


So I would just take it on a case by case basis. If on one page or section, one way would be easier for the user to understand, but isn't the formal name, then I would go with what is easier to understand. If it's a more general page, then going with the more formal name would probably be good. As long as users/readers understand it, that's the important part. -- Ned Scott 09:55, 14 April 2013 (EDT)

3 Mos Capitalization...

Beware as changing from ==This Header== To ==This header== breaks all the links to that particular section from other pages that link there.--uNiversal 17:06, 19 April 2013 (EDT)

I wouldn't worry too much about breaking links to headers. I think the bot has a script that can fix those. -- Ned Scott 23:52, 19 April 2013 (EDT)
I guess the script only fix capitalization links? If there's one. :) Udepub 04:08, 20 April 2013 (EDT)
Do Wikis really make a difference between that? I thought ==This Header== to ==This header XYZ== would only matter. Though I think I've done such changes to section heading a couple times without checking links. I'll check later today. Udepub 03:57, 20 April 2013 (EDT)
Ok, I just tried and it's a difference. Udepub 04:05, 20 April 2013 (EDT)
Isn't there a built-in special page for broken links? Be it capitalization differences or completely broken links. Udepub 04:22, 20 April 2013 (EDT)

4 Sandbox

Correct link (Help:Main_page#Where_we_need_help)
Broken link - capitalization (Help:Main_page#Where_we_need_help - scrolls to top of page)
Broken link - none existent subsection (Help:Main_page#XYZ - scrolls to top of page)
Broken link

Personal tools
Namespaces

Variants
Actions
Navigation
Wiki help
Toolbox