| Wiktionary:Grease pit/2013/March Mar 5th 2013, 02:05 | | | | Line 26: | Line 26: | | | | | | | | :: What are the default settings (the docs[http://www.mediawiki.org/wiki/Extension:WebFonts] only list all ''supported'' languages)? Which fonts set from Common.css? Where is our documentation for this? Which specific browser or OS inadequacies are we serving fonts for? ''—[[User:Mzajac |Michael]] [[User talk:Mzajac |Z.]] <small>2013-03-05 01:58 z</small>'' | | :: What are the default settings (the docs[http://www.mediawiki.org/wiki/Extension:WebFonts] only list all ''supported'' languages)? Which fonts set from Common.css? Where is our documentation for this? Which specific browser or OS inadequacies are we serving fonts for? ''—[[User:Mzajac |Michael]] [[User talk:Mzajac |Z.]] <small>2013-03-05 01:58 z</small>'' | | | + | :::"Supported languages" seems to mean languages which fonts are served for by default. The only fonts set from Common.css are for {{temp|Bugi}}, {{temp|Ethi}}, and {{temp|Mymr}}, I think. --[[User:Yair rand|Yair rand]] ([[User talk:Yair rand|talk]]) 02:05, 5 March 2013 (UTC) |
Latest revision as of 02:05, 5 March 2013 I started a new page WT:CSS, because it was pointed out that our main style sheet is not documented. —Michael Z. 2013-03-01 19:34 z [edit] translation tables slow I think starting with the introduction of Web fonts (but I'm not sure), it now takes a long time for translation tables to drop-down-able. (Newest Firefox for Mac; newest Firefox for Windows.) Is there anything to be done about this?—msh210℠ (talk) 06:42, 4 March 2013 (UTC) - I suspect that it's not the translation tables, per se, but just general slowness. I could be wrong, but I believe that pretty much nothing clickable becomes active until the page is finished being drawn. I've noticed slowness everywhere- not just on pages with web fonts. Chuck Entz (talk) 06:59, 4 March 2013 (UTC)
- Over the years this Wiki has become slower and slower. Every time somebody adds a bit more cleverness, or adds complications to a template, or replaces simple text with a template allowing users to change its appearance, it gets a little bit slower. I think we should stamp down on added cleverness, and maybe roll back some we already have. KISS SemperBlotto (talk) 08:11, 4 March 2013 (UTC)
- I wonder too how much past cleverness might have simpler and more elegant solutions, now that folks have a clearer idea what we want for the site. I know that some processes I've encountered at various job sites have fossilized from years and years of past half-formed ideas about what was required, and sitting down and looking at specific inputs and required outputs can often lead to a much more streamlined way of doing things. -- Eiríkr Útlendi │ Tala við mig 16:19, 4 March 2013 (UTC)
- Isn't {{t}} and its relatives a reasonable suspect for performance problems? Can't someone figure out a way for Lua to improve performance. The number of large and very large translations tables seems to be growing faster than average page size. DCDuring TALK 18:23, 4 March 2013 (UTC)
- If Scribunto really can make templates like {{t}}, {{context}} and other big templates load faster, it could be a very useful tool for improving the usability of our larger pages. Mglovesfun (talk) 18:55, 4 March 2013 (UTC)
- Have you tried turning off WebFonts in the preferences? -- Liliana • 18:27, 4 March 2013 (UTC)
- Good point. Okay, two more bits of information: (1) I think it only happens the first time I load an entry (any entry, not the specific one I'm looking at) in a cacheless browser. (2) I just tried it with WebFonts off and it didn't happen. (Or if it did then it was small enough a delay that I didn't notice it, which was not my experience previous times.)—msh210℠ (talk) 19:50, 4 March 2013 (UTC)
- Just what I suspected: downloading all these fonts takes a long time and the browser is effectively frozen while it happens. This makes WebFonts a real nuisance. -- Liliana • 20:26, 4 March 2013 (UTC)
-
-
- how do we make we bfonts opt-in, on a per-language basis? My browser downloads 1.6 MB of web fonts on this site, but needs zero of them to display all of the languages on the Main Page. This is irresponsible for any website, much less one that should be accessible to people with poor network bandwidth. —Michael Z. 2013-03-04 20:42 z
-
-
-
- Wow, I thought the whole webfonts feature only kicked in if the browser was missing a font required to display a given page. I had no idea it was causing downloads even when not needed. That's not good. -- Eiríkr Útlendi │ Tala við mig 20:49, 4 March 2013 (UTC)
- It only loads a font when there's some text on the page that is set to use a specific font and the user doesn't already have that particular font on their computer, even if they already have some other font that could display the text, I think. --Yair rand (talk) 21:08, 4 March 2013 (UTC)
- I've been having this issue since December. No idea what's causing it. --Yair rand (talk) 21:04, 4 March 2013 (UTC)
So who chose the web font files for Wiktionary? Are they the same fonts that we are specifying in MediaWiki:Common.css? —Michael Z. 2013-03-05 00:15 z - The WebFonts default settings, which we're currently using and can get changed through bugzilla, apply certain fonts to certain languages. Since this doesn't cover all of our uses, there are also some set from Common.css. --Yair rand (talk) 01:28, 5 March 2013 (UTC)
-
- What are the default settings (the docs[1] only list all supported languages)? Which fonts set from Common.css? Where is our documentation for this? Which specific browser or OS inadequacies are we serving fonts for? —Michael Z. 2013-03-05 01:58 z
- "Supported languages" seems to mean languages which fonts are served for by default. The only fonts set from Common.css are for {{Bugi}}, {{Ethi}}, and {{Mymr}}, I think. --Yair rand (talk) 02:05, 5 March 2013 (UTC)
 |  |
