I still don't get what infractions are compared to warnings (I'm sure I'll get it once I dive into your 70-post topics ;)), but I sure hope the extra kilobyte of language strings will end up in a less 'public' file than index.english.php soon... ;)
A complete and more powerful replacement.but I sure hope the extra kilobyte of language strings will end up in a less 'public' file than index.english.php soon...
If you mean what's already committed, check what it is. It is not the warning system, it's the moderation centre which is sort of needed for the board index since that's what's happening, a new virtual category that contains virtual boards. I forget, I haven't committed half of this because of the ever sprawling changes.Oh, speaking about English, I really think we should add a $txt['parent_lang'] parameter. Because it's not only about English UK, or Brazilian Portuguese, or whatever... Every language has its own variations, and maybe the reason we're not seeing these variations around is precisely because it's so annoying to maintain a file for a minority..?
Every language has its variations, which is precisely why we get into English US vs English UK, or Portuguese BR vs Portuguese PT and so on. Extra files are going to need to be maintained for those, it's not avoidable.
The only real difference as far as parent language goes is how much difference there really is. English UK vs English US has some major differences but it also has an awful lot of similarities, so it would make sense to have the parent language.
The parent language aspect does sort of require the other language to be installed. If you want to set up a forum for local events in Portugal (emphasis: Portuguese/PT), that's fine because presumably it's the parent language. But if you want to install a forum for local events in Brazil (emphasis: Portuguese/BR), you then need to install *two* language packs. This is not intuitive even if it is documented somewhere.
I don't know how significant the differences are - though I did ask for some feedback on this - but the impression I've been given is that the variations are big enough to warrant two sets of language files being maintained.For instance, Québec people (around 10M, IIRC..?) speak French, but they have their own words for tons of things. I'm pretty sure that if they could do a Québecois language file, and set parent_lang to French, and just provide a few files with rewrites, and fall back to French for the rest, they'd be really happy to work on it.
Let's take that as a practical example. Yes, you're probably right in that it probably wouldn't need a complete set of files.
However, that does make language loading more complex (in trying to report missing files etc.) and more importantly: is it logical or appropriate to ask those forum cases to install *both* French and the Québecois language files? (Ignore, for the moment, that French is already bundled)
Technically, English UK should be a complete full set of language files, it only isn't because I'm essentially too lazy to do so and I know that English US is *always* loaded because there must be a fallback for error-prevention-in-incomplete-translation purposes.
If the situation were reversed, and French were the only bundled language, with English US being the primary and English UK being a secondary, if I were setting up a forum for *British* users (i.e. the minority speakers), I would not want to install both English US and English UK, even if I only made English UK selectable by users.
As far as suffixes go, I've always seen where it could be practical but I've always had the feeling it's going to be a feature that no-one but you is going to use anyway :(
Posted: April 30th, 2013, 12:35 AM
Back on topic, it seems that it is working as expected elsewhere with that code, so I don't know why it is in normal execution. (At least, attachments are working even when > 4MB)