No internet connection
  1. Home
  2. Support

charset - utf ...

By wiso @wiso2018-12-23 12:34:43.810Z

hallo,
i have a problem with the german characters.
after crawling my site looks like that:

but should look like that:

but if i look in the "index.html" there is the right utf charset, i think:

.....
html lang="de-DE"...head><meta charset="UTF-8".....meta http-equiv="X-UA-Compatible" content="IE=edge"....script type="text/javascript"....

where can i find the mistake? what is the solution?
would be great if someone has a hint for me,
thank you and best regards,
wiso

  • 13 replies
  1. Leon Stafford @leonstafford2018-12-23 15:50:43.869Z

    Hi @wiso,

    It looks like this issue here:

    https://github.com/leonstafford/wp2static/issues/29

    Could you please add to that issue or on this forum, a sample snippet of code from your WordPress site's source and this static copy's source (ie, View Source from right-click within your browser).

    That will help me have some samples to work a solution for.

    1. H
      In reply towiso:
      mac @huji2019-01-16 14:49:38.436Z

      hi Leon, I have the same problem, how can I solve this problem, it is very urgent.

      1. Leon Stafford @leonstafford2019-01-23 03:04:11.308Z

        Hi @wiso, @huji,

        Please try this latest preview release, which adds a fix for UTF-8 encoded pages:

        https://github.com/leonstafford/wp2static/releases/tag/next_release_preview

        Most WordPress themes should have this included, else ensure this is in your HTML code, else the plugin doesn't properly handle the encodings:

        <meta charset="utf-8" />

        1. K@KajMagnus2019-01-26 00:30:22.870Z

          That links is broken? Maybe you meant: https://github.com/leonstafford/wp2static/releases and clicking the "Latest release" green text? results in version 6.3 released a few days ago. @huji

          1. Leon Stafford @leonstafford2019-01-26 01:59:41.275Z

            Thanks for that, @KajMagnus :)

            Let's touch base again soon.

            @huji, please let me know if any further issues.

      2. W
        In reply towiso:
        Woah @woah2019-02-04 17:59:30.249Z

        Same problem here... Tried the latest release ( 6.6.2 ) but it isn't working.

        1. W
          In reply towiso:
          Woah @woah2019-02-05 09:25:17.248Z

          I have checked Slack too, but there are no solutions yet?
          We are running this on a big live site but all text is now f*cked..

          1. W
            In reply towiso:
            Woah @woah2019-02-12 12:57:47.267Z

            Anyone already has fixxed this? Just checking last time otherwise will move on :)

            1. Leon Stafford @leonstafford2019-02-12 22:32:15.325Z

              Hi @woah,

              It's likely down to a combination of your database encoding, the encoding used when entering the content and any other conversion steps throughout the process.

              It's not something I can quickly troubleshoot with some back and forth over emails/forum, but if you would like to hire me for a few hrs, I can take a look at it for you.

              Alternatively, you may try to do the static conversion with HTTrack and some scripts for rewriting URLs, that may have better support for the encoding used.

              Cheers,

              Leon

              1. WWoah @woah2019-02-13 08:05:35.073Z

                Thanks for your reply Leon. All clear.. What about the root problem? If we can't run in root i know enough and we will just move on.

                1. Leon Stafford @leonstafford2019-02-13 08:39:05.515Z

                  can't run in root

                  ^ not clear what that means. Unrelated to the UTF-8 issue?

            2. W
              In reply towiso:
              Woah @woah2019-02-19 08:24:18.295Z

              "root" --> Main folder. Running as the live website. Yes unrelated but the UTF-8 still here too.