Typesetter (the core system) itself doesn't load any google fonts by default – it's the theme(s) which do. Hence there is no global configuration option for that.

Which theme(s) are you using?

That's a delimiter collision - e.g. use double quotes to delimit strings inside a  single quoted string…

<div style="text-align: left;">
  Dieses <a href="" id="bookmarklet-1">Bookmarklet</a> in die Lesezeichensymbolleiste ziehen und fallen lassen
</div>
<script>
  document.getElementById('bookmarklet-1').href='javascript:location.href="https://webcache.googleusercontent.com/search?q=cache:"+window.location.href';
</script>

BTW: how to paste code inside here in this Forum in this editor?

Use the 'Formatted' option from the 'Format' dropdown list (Normal, Heading 1, Heading 2, … Formatted)

... for typos?

Especially for MY typos:

<div style="text-align: left;">
  Dieses <a href="" id="#bookmarklet-1">Bookmarklet</a>
  in die Lesezeichensymbolleiste ziehen und fallen lassen
</div>
<script>
  document.getElementById('bookmarklet-1').href='javascript:alert("Oh!")';
</script>

-->

<div style="text-align: left;">
  Dieses <a href="" id="bookmarklet-1">Bookmarklet</a>
  in die Lesezeichensymbolleiste ziehen und fallen lassen
</div> 
<script>
  document.getElementById('bookmarklet-1').href='javascript:alert("Oh!")';
</script>

does not work

Funnily, it works here. Have you checked the browser console for JS errors (typos, syntax)?
It should actually work.

Hi Cito, just try

<div style="text-align: left;">Dieses <a href="" id="#bookmarklet-1">Bookmarklet</a> in die Lesezeichensymbolleiste ziehen und fallen lassen</div>
<script>document.getElementById('bookmarklet-1').href='javascript:alert("Oh!")';</script>

Assumed reason:
I believe JavaScript code is removed from the href attribute values (and others) so you can not "infect" your site when you copy HTML-formatted content from the Web to your site.
The clipboard may contain various types of content, e.g. Plain text, images, RTF [, etc.], and also HTML.
Fortunately, it is smart enough to omit <script> sections of HTML content when domain boundaries get crossed. However, since attribute values are not filtered automatically, Typesetter (or CKeditor) takes over.

Also, how to get rid of

@We are sorry, but this site is now blocked for editing by another user.[…]

Typesetter CMS does not support simultaneous editing of content by multiple admins. It is therefore recommended that you always log out after editing so that another user can log in immediately.

You can delete /data/_lock_[random hash] files on you webhost (via S/FTP or other direct file system access) to get rid of leftover admin sessions.

Youtube plugin for ckeditor is not bad either

Sure. both have their pros and cons.
In general, using dedicated section types suits my designs better, but sometimes an inline solution is the way to go.

though rather unknown.

Unknown? Um ... it actually ranks place 4 on all non-standard-build CKE plugins (out of over 300)
I'd rather call that one of the most popular.

1st merge is done - we're ver. 1.0-b4 now.

Mind forking?

You do not have 'YouTube Embed' on GitHub

Now I have

Maybe, it will be interesting for you.

Sure. Async loading was overdue. Awesome!

I'll merge versions short-time… be back.

The solution proposed by Jürgen can be used to upgrade Simple_Blog to version 3.5 and can be uploaded to the Typesetter site so it can be used by everyone.

[…] but i must say that the arrows of the details - summary - version make a better impression. This should be done - evtl. colored arrows - before publishing a new version [...]

When making plugins that deal with dynamically created content, one of the harder decisions always is, how much default front-end style and user experience behavior it should come with.

I personally prefer as-lean-as-possible solutions that …
  A) can still be easily overruled via custom CSS and
  B) use as little as possible JavaScript for client-side behavior, which can be hard or even impossible to modify, once initiated.

When it comes to SimpleBlog, there are a few things in the markup that should be improved for better styling possibilities and DOM manipulation.
The problem is, SimpleBlog is very popular and any changes in the html output will cause issues with existing and custom styled installations, when the plugin gets the update.
That's why I always use customized versions, adapted for the current use case.

IMO SImpleBlog should in fact become part of Typesetter core. This would allow much better (Bootstrap) integration and interoperability with other plugins.
But that's nothing done in a few hours, at least not for me.