Plugins » Roboto Sans 2014 Web Fonts 1.0.2014

Roboto Sans 2014 Plugin
Topic Closed
mabu
254 Posts
2.9K Downloads
3 Themes
8 Plugins

With the Typesetter-master 5.1 things are different : The google-fonts-plugin works ok, even though the fonts themselves appear only rarely but a list of proposals.

Font-Plugins :The problems with the missing bold - fonts exist here only in the example window - not in the websites.

My mistake was to try 4.61 at first. So i have hope to fix the fonts2018 which has exactly the same structur.

 

Edited: 2 years ago#10743

juergen
1.5K Posts
53.7K Downloads
16 Plugins
design, web development & visual effects
4.6(.1) was a bit troublesome and premature release.
Edited: 2 years ago#10744

juergen
1.5K Posts
53.7K Downloads
16 Plugins
design, web development & visual effects

The google-fonts-plugin works ok, even though the fonts themselves appear only rarely but a list of proposals.

If you find a pattern which ones fail, we can probably fix it.

2 years ago#10745

mabu
254 Posts
2.9K Downloads
3 Themes
8 Plugins

What i do not understand is why it does not function in the example windows while other things do. Perhaps You can fix this in the master.

I will test the fonts which do not appear  with their fontstyle, and i hope it has nothing to do with firefox.

An example  http://net.square7.ch/gwebfont1.jpg

In a few days ( i have over 200 free fonts on my disk)  i hope to have completed the first fonts2018-version (with a link )

Edited: 2 years ago#10753

mabu
254 Posts
2.9K Downloads
3 Themes
8 Plugins

I  have a small question while generating the font-family-addons: You gave me Abhaya-Libre1.0,  and i see that You use in the end of the css :

abhayalibre-bold with normal-normal and the 800-font ,  and after that

abhayalibre-extrabold (!?) with  normal-normal and the same 800-font (instead of  700 and 800).

In the beginning You use twice abhayalibre and then twice abhayalibre-medium.

If i use  https://fonts.googleapis.com/css?family=Abhaya+Libre:regular,500,700 (which gets the fonts from google and functions), then it functions by replacement of the  local('AbhayaLibre-Regular') with : font-familiy (abhayalibre-regular)  etc. . I do not see how You generate the exact  font-style with Your method.

 

 

Edited: 2 years ago#10776

juergen
1.5K Posts
53.7K Downloads
16 Plugins
design, web development & visual effects

abhayalibre-bold with normal-normal and the 800-font ,  and after that

My fault, line 98 of AbhayaLibre.css should actually be

  font-weight:bold; /* using the extrabold weight as well */

abhayalibre-extrabold (!?) with  normal-normal and the same 800-font (instead of  700 and 800).

It simply doesn't make sense to add an additional bold weight to the the abhayalibre-extrabold family - it won't get any bolder than 800.

In the beginning You use twice abhayalibre and then twice abhayalibre-medium.

Since we cannot define font-weights in CKEditor's Font dropdown, we need to create separate css font-families for the weights in the stylesheet.
A single abhayalibre family (that's what Google Fonts delivers) wouldn't suffice if we want to get all the 5 weights.

In order to always be able to use CKEditor's [B] bold button (which will wrap the selected text in a <strong> tag) we also need a real bold font variant for each of the defined families. So with Abhaya Libre, the normal/bold weight mapping works this way:

Font-Family             Normal Weight Font              Bold Weight Font

abhayalibre             abhaya-libre-v3-latin-regular   abhaya-libre-v3-latin-600 
abhayalibre-medium      abhaya-libre-v3-latin-500       abhaya-libre-v3-latin-700
abhayalibre-semibold    abhaya-libre-v3-latin-600       abhaya-libre-v3-latin-800
abhayalibre-bold        abhaya-libre-v3-latin-700       abhaya-libre-v3-latin-800
abhayalibre-extrabold   abhaya-libre-v3-latin-800       n/a

which translates to

Font-Family             Normal Weight   Bold Weight

abhayalibre             Regular         Semi-Bold
abhayalibre-medium      Medium          Bold
abhayalibre-semibold    Semi-Bold       Extra-Bold
abhayalibre-bold        Bold            Extra-Bold
abhayalibre-extrabold   Extra-Bold      n/a

That's pretty much how Adobe treats quite some fonts for formatting with the [B] button.
E.g. Helvetica Neue 45 Light set to Bold will be Helvetica Neue 65 Medium

Normal            Bold
25 (Ultra Light)  45 (Light)
35 (Thin)         55 (Roman)
45 (Light)        65 (Medium)
55 (Roman)        75 (Bold)
65 (Medium)       85 (Heavy)
75 (Bold)         95 (Black)

It's a common practice to use the next-but-one font weight as bold, but it depends largely on the font.
With Abhaya Libre, the font weight differences are not so pronounced and Extra-Bold is lighter than many other serif fonts' bold weight.

So, it's up to you (or me) to decide, which weights qualify/map best as bold.

Edited: 2 years ago#10778

juergen
1.5K Posts
53.7K Downloads
16 Plugins
design, web development & visual effects

local('AbhayaLibre-Regular')

local() references to locally installed fonts (on the client system). If it is installed, the web browser will use the local font instead of downloading the ones defined via url() .
We can suppress usage of local fonts (which sometimes render ugly) e.g. by using local('☺') - this will tell the browser to use the local font ☺, which obviously doesn't exist.

Using the ☺ trick: © by Paul Irish :o)

2 years ago#10779

mabu
254 Posts
2.9K Downloads
3 Themes
8 Plugins

The last point of my question was still a bit different : The general font-face-declaration  allows to fill in any name for the font-family.

Thats what i did with the file which is generated with

https://fonts.googleapis.com/css?family=Abhaya+Libre:regular,500,600,700,800 ( or any font like 'trirong' - googlefont...) in the browser , which can be saved as css.css. The https - links within this css-file deleiver in the browser the specific fonts which can be saved.

In this css.css - file the names of the font families are all equal. If i use equal names in the abhayalibre.php then the ckeditor doesnt know what to use (or how does he ?) - so i  changed in  each font-face the  names of the font-families to the names of the local font-families - so that each font-face has a different font-family-name -- which is not false and functions with web-loaded fonts. But i want to use local-font-files first, then the files in the CMS and first then the fonts loaded from google.

So it must be possible to modify the font-faces to a big form as in https://google-webfonts-helper.herokuapp.com/fonts/abhaya-libre?subsets=latin --- and append the web-https :

@font-face { font-family: 'abhayalibre-regular'; font-style: normal;  font-weight: 400;

src: url('../fonts/abhaya-libre-v3-latin-regular.eot'); /* IE9 Compat Modes */

src: local('Abhaya Libre Regular'), local('AbhayaLibre-Regular'),

url('../fonts/abhaya-libre-v3-latin-regular.eot?#iefix') format('embedded-opentype'), /* IE6-IE8 */

url('../fonts/abhaya-libre-v3-latin-regular.woff2') format('woff2'), /* Super Modern Browsers */ -----  /* or Abhaya-libre-regular.ttf  from google*/

url('../fonts/abhaya-libre-v3-latin-regular.woff') format('woff'), /* Modern Browsers */

url('../fonts/abhaya-libre-v3-latin-regular.ttf') format('truetype'), /* Safari, Android, iOS */

url('../fonts/abhaya-libre-v3-latin-regular.svg#AbhayaLibre') format('svg'), /* Legacy iOS */ ---  /* and append :: */

url(https://fonts.gstatic.com/s/abhayalibre/v3/e3t5euGtX-Co5MNzeAOqinEYj2rCrdZJ.woff2) format('woff2'); unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD; }

Eventually it is necessary to use other fonts than abhaya-libre-v3-latin-regular (maybe the direct fonts from google, which have other names, or transformed fonts of the url(https://fonts.gstatic.com/s/abhayalibre...)  by fontsquirrel -- etc.

There must be a reason why this mostly uses the loaded fonts from the web. ( The above "Helvetica Neue 45 Light set to Bold will be Helvetica Neue 65 Medium" etc.  is a branch of a science for each font ) - to this theme : a font-declaration table for everybody

 

 

 

 

Edited: 2 years ago#10780

juergen
1.5K Posts
53.7K Downloads
16 Plugins
design, web development & visual effects

The last point of my question was still a bit different : The general font-face-declaration  allows to fill in any name for the font-family.
Thats what i did with the file which is generated with https://fonts.googleapis.com/css?family=Abhaya+Libre:regular,500,600,700,800 ( or any font like cormorant...) in the browser , which can be saved as css.css. The https - links within this css-file deleiver in the browser the specific fonts which can be saved.

Yes, the font-family name noted in the css doesn't have to match the actual font name.

In this css.css - file the names of the font families are all equal. If i use equal names in the abhayalibre.php then the ckeditor doesnt know what to use (or how does he ?)

No it doesn't. That's a problem with CKEditor's Font dropdown. We cannot add weights to list items, only font-families. Therefore we need to create distinct families via our custom css.

- so i  changed in  each font-face the  names of the font-families to the names of the local font-families - so that each font-face has a different font-family-name -- which is not false and functions with web-loaded fonts.

In earlier versions there was a bug in CKE's css normalizer that forced us to use all-lowercase family names.
Although it was fixed, I made a habit of using all-lowercase font names. But in the meantime it should work with the local font name (e.g. 'Ahbaya Libre Regular').

But i want to use local-font-files first, then the files in the CMS and first then the fonts loaded from google.

The webbrowser will always try to use local fonts before downloading them.

So it must be possible to modify the font-faces to a big form as in https://google-webfonts-helper.herokuapp.com/fonts/abhaya-libre?subsets=latin --- and append the web-https :

@font-face { font-family: 'abhayalibre-regular'; font-style: normal;  font-weight: 400;
src: url('../fonts/abhaya-libre-v3-latin-regular.eot'); /* IE9 Compat Modes */
src: local('Abhaya Libre Regular'), local('AbhayaLibre-Regular'),
url('../fonts/abhaya-libre-v3-latin-regular.eot?#iefix') format('embedded-opentype'), /* IE6-IE8 */
url('../fonts/abhaya-libre-v3-latin-regular.woff2') format('woff2'), /* Super Modern Browsers */ -----  /* or Abhaya-libre-regular.ttf  from google*/
url('../fonts/abhaya-libre-v3-latin-regular.woff') format('woff'), /* Modern Browsers */
url('../fonts/abhaya-libre-v3-latin-regular.ttf') format('truetype'), /* Safari, Android, iOS */
url('../fonts/abhaya-libre-v3-latin-regular.svg#AbhayaLibre') format('svg'), /* Legacy iOS */ ---  /* and append :: */
url(https://fonts.gstatic.com/s/abhayalibre/v3/e3t5euGtX-Co5MNzeAOqinEYj2rCrdZJ.woff2) format('woff2'); unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD; }

I'm uncertain if the browser will actually download the additional font from Google in case characters out of the primary encoding range are used.
If it works, that would be a good solution, although a bit cumbersome to build manually - we still need to provide at least woff and woff2.

Eventually it is necessary to use other fonts than abhaya-libre-v3-latin-regular (maybe the direct fonts from google, which have other names, or transformed fonts of the url(https://fonts.gstatic.com/s/abhayalibre...)  by fontsquirrel -- etc.

There must be a reason why this mostly uses the loaded fonts from the web.

The benefit of loading fonts from google is that there's a probability that the client already has them in the browser cache - for the most popular fonts like Open Sans, it's almost certain.
Any self-hosted font will only be cached after the first page load.

(The above "Helvetica Neue 45 Light set to Bold will be Helvetica Neue 65 Medium" etc.  is a branch of a science for each font.)

It is. It is not only for CKEditor's limitation but also for cases where a bold weight will applied by css for inherited font families, such as
body { font-family: abhayalibre-medium; }
h1 { font-weight:bold; }

Faux-bold is not an option, not with a CMS called 'Typesetter' ;-)

Edited: 2 years ago#10781

mabu
254 Posts
2.9K Downloads
3 Themes
8 Plugins

The https://fonts.googleapis.com/css?family=Abhaya+Libre:regular,500,600,700,800    deleivers ( an extract - please look at it - the trirong-font is still bigger ... )

/* latin */     @font-face { font-family: 'Abhaya Libre'; font-style: normal; font-weight: 400;

src: local('Abhaya Libre Regular'), local('AbhayaLibre-Regular'),

url(https://fonts.gstatic.com/s/abhayalibre/v3/e3tmeuGtX-Co5MNzeAOqinEQfEnX.woff2) format('woff2'); unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD; }

As i use a list of  font faces in the php i changed this to :  font-family: 'abhayalibre-regular';   --- which functions always : in the PHP : Abhaya Libre normal/abhayalibre-regular,serif.... ( i have more so functioning addons)

This web- font-face needs no bold  etc.  -------- It uses internally:  font-style: normal; font-weight: 400;  --------------------------------------------------------

In Your Roboto Sans 2014 You use in the RobotoSans2014.php :

"Roboto2 Thin/roboto2-thin,sans-serif;" .  roboto2-thin is twice declared in the css  with and without italic - does the ckeditor use the first declaration ?

Please do not misunderstand me: I aim for clear declarations ( and a finally  systematic clear method).

 

Edited: 2 years ago#10782

juergen
1.5K Posts
53.7K Downloads
16 Plugins
design, web development & visual effects

The https://fonts.googleapis.com/css?family=Abhaya+Libre:regular,500,600,700,800    deleivers ( an extract - please look at it - the trirong-font is still bigger ... )

file sizes vary widely between different fonts, it's due to their geometry, optimizations, hinting etc. and of course the character encoding

/* latin */     @font-face { font-family: 'Abhaya Libre'; font-style: normal; font-weight: 400;
src: local('Abhaya Libre Regular'), local('AbhayaLibre-Regular'),
url(https://fonts.gstatic.com/s/abhayalibre/v3/e3tmeuGtX-Co5MNzeAOqinEQfEnX.woff2) format('woff2'); unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD; }

As i use a list of  font faces in the php i changed this to :  font-family: 'abhayalibre-regular';   --- which functions always : in the PHP : Abhaya Libre normal/abhayalibre-regular,serif.... ( i have more so functioning addons)

Yep.

This web- font-face needs no bold  etc.  -------- It uses internally:  font-style: normal; font-weight: 400;  ---------------------

It does. 400 is the Regular weight. If we don't provide a Bold weight (e.g. 600), the browser will render ugly faux-bold.
AFAIK the browser will not try to find a matching bold weight from a different font-family declaration. It must not do so. Therefore, if we create our custom css font-family 'abhayalibre-regular', we also need to provide a bold weight for that family, wich could then be Abhaya Libre Semi-Bold or Abhaya Libre Bold.

In Your Roboto Sans 2014 You use in the RobotoSans2014.php :
"Roboto2 Thin/roboto2-thin,sans-serif;" .  roboto2-thin is twice declared in the css  with and without italic - does the ckeditor use the first declaration ?
Please do not misunderstand me: I aim for clear declarations ( and a finally  systematic clear method).

With italics, is's merely the same as with bold. If we do not provide a distinct font, the browser will creat faux-italics (= oblique, mostly ugly) and faux-bold (= always ugly, and different browser do it differently).

/* THIN */
@font-face {
font-family:'roboto2-thin';
src:  url('../fonts/roboto-thin.eot');
src:  local('Roboto Thin'), local('Roboto-Thin'),
      url('../fonts/roboto-thin.eot?#iefix') format('embedded-opentype'),
      url('../fonts/roboto-thin.woff') format('woff'),
      url('../fonts/roboto-thin.woff2') format('woff2'),
      url('../fonts/roboto-thin.ttf') format('truetype');
font-weight:normal;
font-style:normal;
}
@font-face {
font-family:'roboto2-thin';
src:  url('../fonts/roboto-thinitalic.eot');
src:  local('Roboto Thin Italic'), local('RobotoThin-Italic'), local('Roboto-ThinItalic'),
      url('../fonts/roboto-thinitalic.eot?#iefix') format('embedded-opentype'),
      url('../fonts/roboto-thinitalic.woff2') format('woff2'),
      url('../fonts/roboto-thinitalic.woff') format('woff'),
      url('../fonts/roboto-thinitalic.ttf') format('truetype');
font-weight:normal;
font-style:italic;
}

css family   style   rendered font (file) 

Edited: 2 years ago#10783

juergen
1.5K Posts
53.7K Downloads
16 Plugins
design, web development & visual effects

Just to clarify the methods and behavior:

The way Google delivers the fonts + css is the correct way to do it. And it perfectly works as long as CKEditor's Font dropdown won't come into our way.
Of course, web browsers are smart enough to map normal and bold weights to the numerical weights defined in Google's css within a single large family.
We need to split the large family into subfamilies in order to make use of them in CKEditor's Font drowdown - that's where all the difficulties begin.

BTW: With CKEditor Styles Combo, we could do it a lot better, in technical terms. If we don't wrap text with <span style="font-weight:bold;">, <b> or <strong> tags but use custom defined classes, we can use Google Fonts right away. We could use sth. like

span.font-weight-100 { font-weight:100; }
span.font-weight-200 { font-weight:200; }
...
span.font-weight-900 { font-weight:900; }

This would work for any font. The browser would always pick the next-matching available weight, if the current one is missing.
Actually, that's way better.

Edited: 2 years ago#10784

mabu
254 Posts
2.9K Downloads
3 Themes
8 Plugins

In the Roboto2 Thin/roboto2-thin,sans-serif  the roboto2-thin-declaration is not  unambiguously.  To change the sequence of the first 2 font-faces from normal-normal to normal-italic has no influence. Something in the background happens what i do not understand - anyway :

The method which i aim at  is to mark a piece of text within ckeditor and choose the font-family from the dropdown. Of course i can make me a font-face-css, which many websites include, which loads the fonts online without ckeditor and without an addon.

A beta of the way i choose is the trirong - beta (for download). It functions, but it  does not not yet load the fonts from the CMS, which are not integrated. I know now how to go on, and i think i will be able to publish an addon within a week.

The google-webfont-font load is anyway only a limited method since other Sil-Fonts like from https://fontlibrary.org must be loaded from the CMS.

It seems that https://stackoverflow.com/questions/9327934/embedded-fonts-versus-an-external-resource?rq=1  had a similar problem ....

It already helps to remove the ../font/family from the css and then move the fonts into the css-directory....

Edited: 2 years ago#10785

juergen
1.5K Posts
53.7K Downloads
16 Plugins
design, web development & visual effects

In the Roboto2 Thin/roboto2-thin,sans-serif  the roboto2-thin-declaration is not  unambiguously.  To change the sequence of the first 2 font-faces from normal-normal to normal-italic has no influence. Something in the background happens what i do not understand - anyway :

If you have Roboto installed locally on your computer I'd rather uninstall it when testing own web fonts, otherwise you may get unclear results.
Can't imagine a different cause at the moment.

The method which i aim at  is to mark a piece of text within ckeditor and choose the font-family from the dropdown. Of course i can make me a font-face-css, which many websites include, which loads the fonts online without ckeditor and without an addon.

I'd say that's exactly what we're talking about ;)

A beta of the way i choose is the trirong - beta(for download). It functions, but it  does not not yet load the fonts from the CMS, which are not integrated. I know now how to go on, and i think i will be able to publish an addon within a week.

Three things that I see:

1)

                            "Trirong-extralightitalic/trirong-extralightitalic,serif;" .
                            "Trirong light/trirong-light,serif;" .
                            "Trirong lightitalic/trirong-lightitalic,serif;" .

Trirong light is missing in trirong.php

2)

in css/trirong.css your urls look like this:

url('../fonts/trirong-v3-latin...

but the actual folder name is font. Won't work this way.

3) Of course you can declare distinct italic families, but you don't need to because we have the [I] button in CKEditor and it does the right thing in terms of SEO and semanitcs, by wrapping the selected text inside an <em> tag. Emphasizing has semantic qualities, <style="font-family:somefont-italic"> does not. Same applies to the [B] button (=<strong>). Search engines rate that stuff.

The google-webfont-font load is anyway only a limited method since other Sil-Fonts like from https://fontlibrary.org must be loaded from the CMS.

Sure, there is a plethora of great free webfonts out there not yet in Google Fonts.
For FontLibrary: They actually do provide css links, e.g. <link rel="stylesheet" media="screen" href="https://fontlibrary.org/face/fantasque-sans-mono" type="text/css"/>
But their CSS defines families for every weight and style, even italics.

It seems that https://stackoverflow.com/questions/9327934/embedded-fonts-versus-an-external-resource?rq=1  had a similar problem ....

The question was asked in 2012 - things are a bit different nowadays. IMO the OP had several errors such as calling url('/assets/fonts/...') to be relative to his css, which it is not. It's absolute.
So I don't believe his question is relevant for us. We don't have to deal with CORS issues.
The mentioned Base64 encoding of font binary data is possible but a nightmare in terms of maintainability - I wouldn't do that.

It already helps to remove the ../font/family from the css and then move the fonts into the css-directory....

Possible, IMO merely a matter of taste. Most vendors keep css and fonts apart.

 

Edited: 2 years ago#10786

mabu
254 Posts
2.9K Downloads
3 Themes
8 Plugins

Sometimes i am just  blind  - font-fonts... probably because of the chaos of over 3000  font-families.

But "Trirong light/trirong-light,serif;" . The ckeditor fills in :  font-family: "trirong-light...

The font must be integrated before with the means of the css. In my version is only one ' trirong-light ', ie. every font face has a different name.

Your version with several identical font-face-names is too high for me(my limitations).

The first part in the php can be any name. It just appears in the dropdown.

What i still have to find out  is how the php fills the code into ckeditor.

So i have now  the main problem of choice of the best font-families.

Edited: 2 years ago#10787

juergen
1.5K Posts
53.7K Downloads
16 Plugins
design, web development & visual effects

But "Trirong light/trirong-light,serif;" . The ckeditor fills in :  font-family: "trirong-light...
The font must be integrated before with the means of the css.

It's already in the css.

In my version is only one ' trirong-light ', ie. every font face has a different name.
Your version with several identical font-face-names is too high for me(my limitations).

I know how puzzling it can be to debug such sets, because there may be issues with the font files, the css and the CKE implementation.
But it will work this way in the end.

@font-face {
  /* Plain */
  font-family: 'myFontFamily';
  src: url('MyFontFamily-Regular.ttf') format('truetype');
  font-weight: normal;
  font-style: normal;
}
@font-face {
  /* Italic */
  font-family: 'myFontFamily';
  src: url('MyFontFamily-Italic.ttf') format('truetype');
  font-weight: normal;
  font-style: italic;
}
@font-face {
  /* Bold */
  font-family: 'myFontFamily';
  src: url('MyFontFamily-Bold.ttf') format('truetype');
  font-weight: bold;
  font-style: normal;
}
@font-face {
  /* Bold-Italic */
  font-family: 'myFontFamily';
  src: url('MyFontFamily-BoldItalic.ttf') format('truetype');
  font-weight: bold;
  font-style: italic;
}

I'd recomment to load the css in the first place and test it with such HTML

<div style="font-family:myFontFamily;">myFontFamily: Regular, <em>Italic</em>, <strong>Bold, <em>Bold-Italic</em></strong></div>

As soon as this works, do the CKEditor implementation.
Just don't give up.

The first part in the php can be any name. It just appears in the dropdown.
What i still have to find out  is how the php fills the code into ckeditor.

The plugin hook call will alter CKEditor's configuration, which will be passed as gp_ckconfig (JSON) as part of the AJAX response for inline editing.
CKEditor will then render its UI based on this configuration.
It's one of the more complex parts of the CMS.

So i have now  the main problem of choice of the best font-families.

Quite a hard decision ;-)

Edited: 2 years ago#10789

mabu
254 Posts
2.9K Downloads
3 Themes
8 Plugins

2. The structure of the trirong.css comes from the css which is generated by

https://fonts.googleapis.com/css?family=Trirong:100,100italic,200,200italic,300,300italic,regular,italic,500,500italic,600,600italic,700italic,700,800,800italic,900,900italic

To modify it is quite easy as long as the fonts come from google helper - the otf-fonts can be converted online.

----------------------------------------------------------------------------------------------------------------------------------------------------------------------

2. The roboto 1.0 -plugin makes Typesetter unstable.(!?)

Therefore i give You here a new nearly complete version with fonts from google-helper with a much higher compatibility :  Roboto 1.8 Typesetter.

In the roboto18.php is still an incompatibiliy with two formatations : Roboto Cnd Light/roboto-condensed-light,sans-serif;" .  /*n n */
                            "Roboto Cnd/roboto-condensed,sans-serif;"

If You take other family-names in the php, then the momentary users will loose some of their their formatations.

I hope You can do something with it.

 

Edited: 2 years ago#10790

juergen
1.5K Posts
53.7K Downloads
16 Plugins
design, web development & visual effects

2. The roboto 1.0 -plugin makes Typesetter unstable.(!?)

Unstable? So you mean you get errors? Which type - Javascript or PHP/server side?

Roboto 1.0 was the older 2011 version with the curved R-leg. I'd consider it deprecated - Roboto 2014 (current version) comes with significant improvements.

2 years ago#10791

mabu
254 Posts
2.9K Downloads
3 Themes
8 Plugins

The system becomes slow and tough (no errors)  - also with the google-analytics -plugin and with one of the previous - next -plugins.

Perhaps this happens because of the threefold font-family declaration of the same family(a bit like multiple declarations in c++), which might disturb the browser. The effect disappeares after their deinstallation.

There are connexions to a better functioning if i add all css-ses of the CMS together. The latter is also necessary for the bootstrap-plugin.

Edited: 2 years ago#10792

mabu
254 Posts
2.9K Downloads
3 Themes
8 Plugins

The very new Roboto 1.8 for Typesetter contains also the condensed font  from google font helper.

It als contains a second css which allows to style the normal way without ckeditor and

  a demo.html, which proves that the css is font-face-compatible

Not yet solved is the styling of the dropdown with its specific font (by a .js )

I have now found  a bullet proof styler at : https://transfonter.org/ which als generates a demosite
Edited: 2 years ago#10793

Topic Closed

 

News

elFinder 2.1.50 in Upcoming Release
12/28/2019

A new release for Typesetter is in the works with a lot of improvements including the ... Read More

Typesetter 5.1
8/12/2017

Typesetter 5.1 is now available for download. 5.1 includes bug fixes, UI/UX improvements, ... Read More

More News

HH-Support

Company located in Tórshavn, Faroe Islands. * Webpage Design * Consultant & Provider of a wide range of programs for visually impaired and dyslextics.

Find out more about our Provider Spotlight

Log In

  Register