Re: naming for SD-JSON grabber(s)
Nick Morrott <[email protected]>
| Newsgroups | gmane.comp.tv.xmltv.devel |
|---|---|
| Message-ID | <CAOQWjw1sSnWvg7y39HRxoV0Bkgjma4T-kEqG5L=zCOQ=j2d4cw@mail.gmail.com> |
On 23 May 2016 at 16:32, Hika van den Hoven <[email protected]> wrote: > Hoi John, > > Monday, May 23, 2016, 12:14:49 PM, you wrote: > >> On 23/05/16 10:45, Ian Campbell wrote: >>> On Sun, 2016-05-22 at 22:27 -0500, Robert Eden wrote: >>> >>>>> Namewise I'm wondering about something descriptive like >>>>> tv_grab_global_sd (raises pinky to mouth a la Dr Evil). I'm not sold >>>>> on the "zz" faux country code but if we want to stick to 2 letter code >>>>> (aside from huro) there's not much wriggle room. >>>>> [...] >>>> I think "global" is a bit long..... >>> >>> Getting well into bikeshedding here, but why does the length matter vs >>> clarity? It's not something that is going to get typed manually very >>> often (once it is working it'll be added to some script or config pane >>> somewhere, while setting up you'll mosdt likely just press up arrow >>> most of the time). >>> >>> With tab completion and the current set of grabbers today it's actually >>> just: >>> 'g' <TAB> >>> which is two characters ;-) >>> >>> That is until Greece (GR), Gabon (GA) etc get grabbers when it'll >>> become three ('g' 'l' <tab>) until Greenland (GL) get in on the act >>> when it'll have to be 'g' 'l' 'o' <tab> :-D >>> >>> Ian. > >> This man speaks the truth! > >> But if not "global", then how about "multi", for multiple countries. >> That could also be used for any other grabber which does, say, two >> countries, for which "global" might seem over the top. > >> John > > Have you even thought about the distinction between country and > language ;-) > I maintain a Dutch grabber (in Python, so not in the package) named > tv_grab_nl_py, but it also services Flemish Belgium, where they also > have a French grabber for Wallonia. Similar situations could apply to > for instance Switzerland and Canada. How about we extend the capabilities framework that grabbers already use and add a new (or extend an existing) capability type to add support for languages a grabber supports/outputs? Then an end-user could (for example) call: $ tv_find_grabbers lang=XX_yy and get a list of any grabbers that support their desired language. This avoids the grabber naming scheme becoming overloaded and grabbers having to be renamed whenever they add support for a new language. Cheers, Nick ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j