Package Home

Zend Framework 2 Documentation (Manual)

PHK Home

File: /user-guide/styling-and-translations.html

Size:11088
Storage flags:no_autoload,compress/gzip (30%)

Styling and Translations — Zend Framework 2 2.4.2 documentation

Styling and Translations

We’ve picked up the SkeletonApplication’s styling, which is fine, but we need to change the title and remove the copyright message.

The ZendSkeletonApplication is set up to use Zend\I18n’s translation functionality for all the text. It uses .po files that live in module/Application/language, and you need to use poedit to change the text. Start poedit and open module/Application/language/en_US.po. Click on “Skeleton Application” in the list of Original strings and then type in “Tutorial” as the translation.

../_images/user-guide.styling-and-translations.poedit.png

Press Save in the toolbar and poedit will create an en_US.mo file for us. If you find that no .mo file is generated, check Preferences -> Editor -> Behavior and see if the checkbox marked Automatically compile .mo file on save is checked.

To remove the copyright message, we need to edit the Application module’s layout.phtml view script:

1
2
3
4
 // module/Application/view/layout/layout.phtml:
 // Remove this line:
 <p>&copy; 2005 - 2014 by Zend Technologies Ltd. <?php echo $this->translate('All
 rights reserved.') ?></p>

The page now looks ever so slightly better now!

../_images/user-guide.styling-and-translations.translated-image.png

Previous topic

Database and models

Next topic

Forms and actions

This Page

Note: You need to stay logged into your GitHub account to contribute to the documentation.

Edit this document

Edit this document

The source code of this file is hosted on GitHub. Everyone can update and fix errors in this document with few clicks - no downloads needed.

  1. Login with your GitHub account.
  2. Go to Styling and Translations on GitHub.
  3. Edit file contents using GitHub's text editor in your web browser
  4. Fill in the Commit message text box at the end of the page telling why you did the changes. Press Propose file change button next to it when done.
  5. On Send a pull request page you don't need to fill in text anymore. Just press Send pull request button.
  6. Your changes are now queued for review under project's Pull requests tab on GitHub.

For more information about the PHK package format: http://phk.tekwire.net