Quote:
|
Originally Posted by qualiteam
I doubt there were any technical reasons to use Google Fonts. Designers use web fonts not because it is a technical requirement  |
Exactly. So why did they choose Google, when there are many alternatives available, all, without the "joys" of dealing with Google. That's the question in a more specific format really. See other posts on Google's "self-focus first" etc
Quote:
|
Originally Posted by qualiteam
...Google do cache their fonts in the way that allows them quickly fix problems with their CSS (if any happens)
|
The most relevant part here is
"...that allows them..." That's the issue isn't it? i.e. Them not XC or any end-user or whoever else. See comment above ^
Quote:
|
Originally Posted by qualiteam
What problem do you want to fix by switching from Google Fonts to "alternatives"?
|
That's the question that the Dev Team / Designers should be asking themselves surely? This particular issue is well known and well recognised (examples have already been posted by us and others on here and in other forums etc) so from a pro-active perspective... the answer, to what appears to be a self-created problem lies with Dev Team / Designers. As end-users, we can only report factual issues with finished XC products. If we become deeply involved in XC core design or re-design, we've lost focus on our own business we think
We only use Unix / Apple products and their third-party compatible products ourselves, but if there is an issue with any of these, it gets fixed. Quickly. Especially if it's a publicly acknowledged issue.
Quote:
|
Originally Posted by qualiteam
What alternatives would you suggest?
|
It does not matter at all what we suggest. It's 100% the designer's choice. If he/she/they did not see this issue in advance, okay everyone is human and it's a minor issue compared to others if we are being honest. However, many alternatives are readily available to them. If a designer opts for the "....ohhhhh....don't know which to choose..." approach. It would then becomes a bigger issue!
If it can be fixed. Fine. If it can't or it won't (because it's not sufficiently important enough currently) that's also fine. All actions are by the Dev Team though, not end-users who have identified the issue. Let's see what happens as we move into XC5.3.3.* etc