Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
It should be "Internationalization views" instead (no capital "V" in "views"). Please see here for more info: #1103208: Projects' names should be checked in .info files for correct capitalization.. While at it, don't forget the project's name here in d.o too ;)
Also, the name in i18nviews.info still days "name = Views translation". Shouldn't this change to "name = Internationalization views" too?
Comments
Comment #1
klonos...adding tags
Comment #2
webflo CreditAttribution: webflo commentedYeah your are right about the capitalization. But the name in the info file follows the i18n project.
i18n_field => Field translation
i18n_string => String translation
i18n_taxonomy => Taxonomy translation
i18n_menu => Menu translation
This is a won´t fix for me.
Comment #3
webflo CreditAttribution: webflo commentedBTW: Project name is already changed.
Comment #4
klonosThanx for the prompt fix and for taking the time to explain the i18n-naming "compliance" Florian ;)
Comment #5
Kristen PolI think it is confusing that the project name is "Internationalization views" while the module is "Views translation". Can the project name be changed to "Views translation" or are you worried people will get confused if the project name changes?
@webflo said the project name has changed and marked "won't fix" so I'm confused.
I'm reopening for clarification, but obviously put back to "won't fix" if that is the final decision.
Thanks,
Kristen
Comment #6
MichelleSee #1346158: Decide on coding standard for capitalization of module names [policy, no patch] and #1430452: Use Proper Name Case for core modules for current information on this policy.
Comment #7
miro_dietikerName changed back to be capital again.
Comment #8
Kristen PolI'm reopening this as it is confusing that the project name and module name are very different... as in the original issue:
So, there are 2 options:
1. Change project name to "Views Translation"
or
2. Change module name to "Internationalization Views"
I don't have a strong opinion either way but @Jose Reyero mentioned that perhaps "Views Translation" is a better name.
Right now I'm writing a multilingual Drupal 7 book and both @Jose Reyero and @Gábor Hojtsy thought I made a mistake when I wrote down to enable the "Views translation" module (as it's currently called). I did neglect to mention that the project name for that is "Internationalization Views". So, if the project and module name are going to stay out of sync, then I will need to make that more clear in the book.
Thanks!
Kristen
Comment #9
miro_dietikerThe project short name is "i18nviews" and cannot be changed. It's a subproject of the i18n family, thus "Internationalization Views".
For the modules it provides it follows the i18n pattern of translation. Let's pick a few names.
Core already starts with its ugly inconsistency about module names:
module translation technically introduces node translation ... it's module name is "Content translation". OK so, node is content. We don't use "node" in the UI.
Then comes i18n that adds i18n_node on top of it that names its module "Multilingual content". Huh?
However most i18n modules and translation modules follow the pattern to provide "XXX translation" like "Field translation", "Menu translation", ...
That's a common pattern that seems to barely follow the core initiation. And that's where we finally decided to follow the pattern.
(I see most inconsistencies currently in e.g. "Multilingual Forum" instead of "Forum translation" and "Multilingual content"...)
The recent discussion about Capitalization of modules hasn't reached i18n yet. So all "XXX translation" modules are still lowercase. We first should start the discussion there.
Changing the project name would be the worst thing. And changing the module name would be far from all patterns...
Any better idea?
Comment #10
Kristen PolI'm not talking about changing the "i18nviews" name file names. I'm talking about changing the name within the .info file:
Meaning the inconsistency is between the drupal.org project page name/title (that says "Internationalization Views") and the name in the .info file (that says "Views translation"). When someone *downloads* the module, they see "Internationalization Views" but when they go to *enable* the module they see "Views translation". That is the confusing part.
I hope I have clarified the problem. I have no problem with the "i18nviews" name.
Kristen
Comment #11
miro_dietikerThat's exacly the same thing i'm talking about.
The project name you download is i18nviews which is "Internationalization Views"
And the module containing follows my interpretation of the standard how i18n modules are named meanwhile "Views translation" ... or "Views Translation" once capitalization occurs. When changing the module name (yes, the name in the .info file...) to what you suggest we would be against the pattern of all/most other translation/i18n module names.
Comment #12
Kristen PolIt seems like the best thing (to keep in sync with the other Internationalization (i18n) modules) would be to change the "project title" for the project to "Views Translation" (no change to the "short project name" which is "i18nviews"). And, then update the .info file to follow the new uppercase policy by capitalizing the "T" in "Translation".
I will send to @Jose Reyero to see how he suggest this be resolved.
Thanks,
Kristen
Comment #13
Jose Reyero CreditAttribution: Jose Reyero commentedSince both options make sense, I'd say the maintaner's preference is ok and there's no point in discussing more about this.
There are many other open issues that really need our attention :-)
Comment #14
Kristen Pol@Jose Reyero - I'm not sure I understand... does your comment mean you are okay with the project title and the module name being different? Or, that they should just choose one of them and change the other to match?
Kristen
Comment #15
Kristen PolJose emailed and said that it was up to the maintainers to decide what they want to do.
Kristen