Search Forums
Kiwitrees on Twitter

    inactive, Require visitor authentication, type, sanity, census assistant, bug, php 5.6, colors theme, xmas, tree, menu, datatables, family, tags, Support/Bug Reporting, design, family facts, children, HTML block, Search and replace, internal messaging, contact links, news module, 7.1, simpl_grey, dropbox. token, descendants, ASSO, login upgrade, custom modules, future, place, mystyle, support, fact, message contactform, folder, research, new feature, request, statistics, 500, defacto, shared note, click, spouse, css, event, watermark, language, re-order, styles, multiple marriages, prefix, .mo, places, 1939 Register, custom, 3.3.0, pdf


    1636 posts

    But for pages, gallery, and menus I still think the best answer is to create two versions of each item (in the same module), one in Danish and one in American. Then there is no further translation required, and your Google translate on those pages will no longer be needed. But again, your choice. Perhaps I could change one of your “pages” as an example for you?

    Hopefully, when you “thanked” me for that post you meant that I should create the example 🙂 Anyway, I have done that. I used a small one: “Why the best man?”.

    If you visit the “Historic blogs” page, select “Why the best man?” and switch between the two languages. You will see a complete translation for each. (Note – I only used google for the initial translation. The words are not perfect, but much the same as your google translate code would give).
    Now if you visit the admin page for the pages module, you will see there are two “pages” for this item, one in Danish, one in English. If you do the same for the other pages (lots of copy/paste, and some help from google required) then the only user-defined translation you will need is for the page title “Historic blogs”.

    My personal kiwitrees site is