-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove references to provider when "Add provider name to bouquets" is enabled #249
Comments
@noguxi I'll close this now. |
I don't know if we should close this, this issue has two parts, the part of omitting the "- All channels" is fixed but the part of: I can try to look at this, @AbuBaniaz do you agree it is redundant to have a "#DESCRIPTION MEO - MEO" when "Add provider name to bouquets" is enabled? |
The tricky thing is that not all of us have access to all the providers so testing is different. I agree
Not everybody uses the plugin the same way nor for the same providers. I always enable the provider name, others may not do so, so for them they only see Maybe the solution is along the lines: |
The following is a list of providers with one section only (not complete). The Dutch terrestrial has several files, I don't know what one looks like when the provider name is enabled.
|
Thanks @AbuBaniaz I will look into this. Didn't know a bouquet file could have multiple sections so your solution is best. |
Or conversely, for providers with only one section, when provider name is added to bouquets, do not show the provider name. |
@noguxi |
@noguxi |
When "Add provider name to bouquets" is enabled there is no need to have reference of the provider in the list
In this example, the
#SERVICE 1:64:0:0:0:0:0:0:0:0:
#DESCRIPTION MEO - MEO
is not needed and should be omitted, or at least an option to omit when "Add provider name to bouquets" is enabled.
And when "Add provider name to bouquets" is enabled the " - All channels" from the NAME should be omitted too, it make sense only when the bouquet is a subset of All channels.
The text was updated successfully, but these errors were encountered: