0

I am building a web site using

  • middleman 3
  • prototype template extension
  • en (English language) as default root language

According to this documentation

http://middlemanapp.com/advanced/localization/#toc_6

source/localizable/services.en.html.haml
source/localizable/services.es.html.haml

should generate

build/services.html
build/es/services.html

but bundle exec middleman build generates

build/services.en.html
build/services.es.html
build/es/services.en.html
build/es/services.es.html

I have tried moving both templates to root folder and not working.

Tun
  • 1,345
  • 13
  • 34
  • This seems to be prepared for content-negotiation. If this webserver feature is activated, the request of services.html will be answered with services.en.html This can be quite handy as the user gets automatically the page in his language if available. more: http://httpd.apache.org/docs/2.2/content-negotiation.html – rriemann Nov 11 '13 at 13:03
  • Thank for the input @salout. Middleman is supposed to handle that without the need of Apache web server. – Tun Nov 13 '13 at 04:45
  • 1
    Check out this issue: https://github.com/middleman/middleman/issues/1015 It got fixed already, so you might want to try the development (master) version of middleman. – rriemann Dec 10 '13 at 13:40

1 Answers1

0

According to @rriemann link, the Localizing whole templates does not work bug was reported on Sept 21, 2013 and fixed on Nov 1, 2013.

The issue was closed on Dec 1, 2013.

Tun
  • 1,345
  • 13
  • 34