7 - How to translate custom date formats? - Drupal Answers
Before we get started, we obviously need a Drupal 7 website to work on. Regional and language, you will see the Regional settings and Date and time The overview table shows the language's name (English and native). The Drupal way of handling and translating Dates is through Configuration > Regional and language > Date and time formats, as Hudri. Building a multilingual website or taking your Drupal site into new Examples include labels for fields in content types, the site name, You can also set up workflows to keep your website content up-to-date in all languages.
Finally, we will want to translate not only the content of the fields, but also things like the field labels and descriptions.
And if we have fields with lists of allowed values we want to be able to create translated versions of those lists. To translate those we need to enable the contributed Internationalization i18n package.
That is actually a whole suite of modules that fill in some of the gaps left in the translation system. We don't yet need all of the modules in the package, but we want the core module and the Field Translation module which translates field properties. We will need to enable the Entity API module and the Variable modules as well, because some of our module depend on them.
After enabling these modules, we re-visit the content type administration page. When we edit each content type we now see a new option to enable Entity Translation for this content type. On the Manage Fields screen for each content type we now see an option to replace the regular title with a field. After making this change, the title will be an editable field, just like all the other fields.
The title will also be displayed in the content like any other field, so you may want to go to the Manage Fields screen and hide it, since you will see the title at the top of the page already.
8 - Date format in another language - Drupal Answers
For each field that needs to be translated, click on the Field settings link and check the box to translate this field. If there is already content in this field you will see a message noting that, but you can still change the option to translate the field.
This should just serve as a reminder that the content in those fields is not yet translated. The final step is to create or edit a page that has a language and we now see a new tab on the page in addition to the View and Edit tabs, a Translate tab. This tab takes us to a page that shows us each language we have enabled on the site where we can add a translated version of the content for that page.
Note that this tab will only appear on nodes that have a language selected. There are new options on the node edit page. In addition to the box to select a language, there is a way to flag translations as outdated.
Adding More Features That is enough to get started with the Drupal 7 multilingual system. There are lots of other modules and features you can add to make the system better.
The Internationalization i18n module includes additional modules to translate taxonomy terms or menu items or forums. And there are several other modules that provide additional functionality that could be useful. A number of them are listed below. Some are not totally ported to Drupal 7 yet and your mileage may vary, but you can explore all these options, depending on your needs. If you also need content translation support, all you need to do is to enable the Content translation module and have multiple languages configured.
The same screen can be used to configure content translatability that you already used to configure content language defaults. With content translation module enabled, the menu item changes from Content language to Content language and translation.
This screen now lets you turn on and off translatability as well on an entity type and bundle subtype level. So you can configure nodes per content type, taxonomy terms per vocabulary, custom blocks per type, etc. Configuring a bundle to be translatable then opens a whole set of configuration on the field level. Built-in base fields are supported, so you can translate the title of nodes and name of taxonomy terms for example.
Publishing metadata like author, creation date and change date "translation" lets you keep accountability on translations. Publication status tracking per language lets you implement workflows for translations, so you can keep some languages published while others are not yet.
Promotion and stickiness per language lets you keep different metadata per language variants. You can of course uncheck the ones which you do not intend to keep different per language. Going further down on the field list, you'll notice that image fields even support translation on a sub-field level.
Localized and Multi-Lingual Content in Drupal 7
That means that by default they offer to translate alt text and titles but keep the image itself the same across translations. This makes sense for product pictures for example. If you also need to have separate files per language, you can configure that too. Finally, the article type also has a taxonomy tags reference field, which stores all related taxonomy terms. By making this field translatable, you can keep a different list of related taxonomy terms per language Case A.
It is also possible that you only want to translate the terms themselves, in which case you should uncheck this box and set the tags vocabulary terms to be translatable on the same page Case B.Drupal Multilingual best practices
That would mean you keep the same tags for all languages but translate the terms themselves. If you already built multilingual sites with Drupal 7 that had content translation, you may notice this model is a refined version of the Drupal 7 Entity translation module without awkward modules required like Title rather than the Drupal 7 core content translation module. The core module in Drupal 7 keeps different copies of nodes and relates them together in a translation set.
In Drupal 8 this feature is not available, instead you can configure translatability on a field and in some cases subfield basis. However if you configure all fields to be fully translatable, you can essentially reproduce the Drupal 7 behavior. Compared to the Drupal 7 core solution with different entity identifiers then, Drupal 8 will have the same entity identifier but a different language variant.
Drupal 8 multilingual tidbits 17: content translation basics
The biggest advantage of the Drupal 8 solution is you can configure to translate as much as needed and not more. With one unified solution to translate only some fields or all fields, contributed modules only need to deal with one system instead of two.
With storing translations under one entity, modules that don't want or need to deal with multilingual scenarios can still consider the entity as one, no need for special translation set support.