Jump to content

Search the Community

Showing results for tags 'website localization'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome to ProcessWire
    • News & Announcements
    • Showcase
    • Wishlist & Roadmap
  • Community Support
    • Getting Started
    • Tutorials
    • FAQs
    • General Support
    • API & Templates
    • Modules/Plugins
    • Themes and Profiles
    • Multi-Language Support
    • Security
    • Jobs
  • Off Topic
    • Pub
    • Dev Talk

Product Groups

  • Form Builder
  • ProFields
  • ProCache
  • ProMailer
  • Login Register Pro
  • ProDrafts
  • ListerPro
  • ProDevTools
  • Likes
  • Custom Development

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. The great latest localization enhancements for PW 2.5 raise some problems due to the multi-language site profile. I observed that when the site translation files are included in the core translation files language pack, they are unnecessarily uploaded to the Core Translation Files and I can delete them, but cannot move them to their appropriate location. As the translation files are distributed in one package, many of them downloaded directly from GitHub, it would be a smarter solution if the language pack uploader dispatched the site language files to the Site Translation Files section. It turned out in Ryan's answer on my GitHub issue report, that we cannot use these site translation files for monolingual sites, so it would be recommended if the language pack uploader detected the multilingual status and when it failed (due to monolingual site), it displayed a warning and did not upload the site language files.
×
×
  • Create New...