Skip to content
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

i18n support for composer.json #1954

Closed
dominikzogg opened this issue May 31, 2013 · 10 comments
Closed

i18n support for composer.json #1954

dominikzogg opened this issue May 31, 2013 · 10 comments

Comments

@dominikzogg
Copy link

We would like to add i18n support for composer.json

"i18n": {
      "en": {
        "name": "The successor of Catalog for Contao Open Source CMS",
        "description": "METAMODELS ARE THE REPLACEMENT FOR THE FAMOUS CATALOG EXTENSION FOR CONTAO WITH FOCUS ON FLEXIBILITY AND EXTENDABILITY.",
        "screenshot": [
          "http://now.metamodel.me/tl_files/standard/layout/images/metamodels.png",
          "http://de.contaowiki.org/images/de/thumb/6/6b/MetaModels_Backend_System.png/800px-MetaModels_Backend_System.png",
          "http://de.contaowiki.org/images/de/thumb/7/7f/MetaModels_Backend_System_ER.png/600px-MetaModels_Backend_System_ER.png",
          "http://de.contaowiki.org/images/de/thumb/e/e4/MetaModels_Backend_System_Beispiel.png/600px-MetaModels_Backend_System_Beispiel.png"
        ]
      },
      "de_DE": {
        "name": "Nachfolger des Catalog für das Contao Open Source CMS.",
        "description": "now metamodel me :-)",
        "screenshot": "http://now.metamodel.me/tl_files/standard/layout/images/metamodels.png"
      },
      "de_CH": {
        "name": "Nachfolger des Catalog für das Contao Open Source CMS.",
        "description": "now metamodel me :-)",
        "screenshot": "http://now.metamodel.me/tl_files/standard/layout/images/metamodels.png"
      }
    },
@discordier
Copy link
Contributor

Seconded, locale handling should be possible somehow to allow a better integration into CMS etc.

@Seldaek
Copy link
Member

Seldaek commented Jun 3, 2013

You can very well put this all in "extra". I doubt there is much point in standardizing this stuff because IMO this all should be in english, but I can see the benefit for CMS plugins to be more end-user friendly.

@Seldaek
Copy link
Member

Seldaek commented Jun 3, 2013

What we could have is some common extra patterns in the composer docs so that people don't reinvent it in different ways, but I don't think composer needs to be aware of all this.

@dominikzogg
Copy link
Author

@Seldaek sounds good to me

@discordier
Copy link
Contributor

Same for me.
So we will document them and add them as PR to https://github.com/composer/composer/blob/master/doc/07-common-extra.md and link to it from https://github.com/composer/composer/blob/master/doc/04-schema.md#extra?

Or can anyone come up with a better name?

@Seldaek
Copy link
Member

Seldaek commented Jun 3, 2013

I would maybe put that in doc/articles/ rather, because it's more "random" knowledge than really part of the main docs.

@discordier
Copy link
Contributor

So we go for doc/articles/well-known-extra.mdbut linked to from 04-schema.md#extra?

@Seldaek
Copy link
Member

Seldaek commented Jun 3, 2013

Sounds good to me.

@discordier
Copy link
Contributor

As Picard said: "make it so!" :)

@Seldaek
Copy link
Member

Seldaek commented Jan 1, 2014

Closing the issue to clean up, but feel free to send a doc PR still :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants