Per this thread, Translating Editable Template , there is a suggestion to use content or experience fragments in an editable template for translation. 

I have gone down this road using 6.4 to little success.  I have tried using Fragment translation two ways, within and outside the variants.  The issue is within the editable template the Experience Fragment path is not translated from en to the other languages.  What is the best practice for header and footer content using fragments and MSM?

Here is what I have tried:

1. I created a sites with multiple locals in the 6.4 standard with language masters and languages which roll out to regions and locales. 
2. I created an experience fragment with the language structure siteName/language/fragmentName
3. I create a live copy of the fragment languages
4. AEM properly created the fragment in the new language with inheritance setup
5. I broke inheritance to change the root path for the main menu and image link path
6. I added the header fragment to the editable template as a component
7. I rolled out changes to all locales
8. Header fragment remained en
9. I added a header container to the template
10. Authored a fragment component in the header container with the content fragment en path
11. Changes automatically rolled out to other locales
12. Fragment path was still en on all locales

Example Content paths

Fragment paths:

• English: /content/experience-fragments/smith/en/global/master.html
• French: /content/experience-fragments/smith/fr/global/master.html
• French within Experience: /content/experience-fragments/smith/en/global/header-french.html

Page paths:

• English: /content/smith/language-masters/en.html
• French: /content/smith/language-masters/fr.html