BuzzerBeater Forums

If people are sick of the wording 'jumpshot' and they change it to 'jumper'.....then eventually people will just get sick of the word jumper.

The idea is not to simply reword, the idea is to leave the wordings that are there, there, but to add OTHER wordings AS WELL to add flavor and variety. The idea is that we want more variety/play types etc...

We aren't gonna get a new GE with new types of events, so they would need to make different wordings for the same types of events so that they seem different. I think there is already several kinds of events that can just be worded differently in the viewer...

So what we ARE asking for (I think atleast) is a game viewer update, which could only be done by the BBs, where they actually add new texts. If this were done, all the LAs would get new tags in their queue to translate. I was an LA for several seasons and personally finished the Japanese translation (although I did not do the bulk of the work, I did a few thousand tags at the end so that finally the game could be released in japanese)...

Anyway The point is I know what I am talking about and Will obviously does not.

I guess the question I had based on how I interpreted what you read was whether the base American English version also had the text pulled from tagged resources like other localized languages or whether it was hardcoded. We have done some localization on the software product I work on and initially there were a lot of hardcoded strings in the program that we'd just say "If they're Spanish, do this instead." That quickly proved to be dumb and now we have a localization setup with keys for English-US, English-UK and Spanish and it's possible that if we expand to other markets that we could translate quite quickly. So pretty much all of my post was more just curiosity on that front.

Having multiple texts for the same event key would probably also be doable, and I'd agree that would be a nice implementation. If I take a hypothetical key like MIDRANGE_JS_BAD_MISS, for example, just adding five or ten versions like MIDRANGE_JS_BAD_MISS_1, etc. would solve the problem pretty cleanly - and when the calculation occurs that creates the key for viewer/pbp, it can select one of those 10 at random or even just by using a specific digit from the previous generated random number. But, yes, that would definitely require BB intervention and the usual caveat about development priorities and whatnot clearly are in effect.

Well with your work experience I think you understand the whole issue better than me.

THe English is the 'official' version. For translation, for the LAs, we see the English, and we have an editable field for each localization. You are correct they could make (may have) a seperate localization for American English which would be seperate from the base verbage...but I think this would make things more complicated. As you state, there are keys. I think the American English is then the 'default' or 'master' or something along those lines...the key point being that only BBs (and maybe some special GMs for all I know) can ever edit it. It is the official and in case of rule confusions etc., the translations/localization wording does not count, everything goes back to the core US English, hence why all GMs and LAs must speak English fluently.

I guess its kinda like when the French ran England and all official laws were French/Latin.

Maybe they should hire you to do a viewer update. Sounds like you got the experience and so forth. Maybe they could offer you a few seasons/years of supporter in lew of your work if they are too broke to give you cash for it. I guess it depends on how developer friendly the code for the viewer is. To me adding a few extra keys, a few lines of text, and some kind of functionality to randomly interpret a given event (which would be what the viewer reads from the GE) in multiple different ways, doesn'T sound too complicated...but then again maybe its a lot more complicated and time consuming than I imagine.

I'd be godawful at anything like the viewer to be honest - I could probably help revise the localization if needed but I'd have to think they've probably got little problem with that part. Haven't they said in the past that the viewer was sort of designed by someone external and they can't really update it? That's probably more of a problem - if that wasn't designed in a way that allows for that sort of extensibility then it really would require a total rewrite. Faking a new language to allow re-localizing the master would be a workaround, but if the viewer has the keys hardcoded in it, for example, it wouldn't be possible to add new keys easily.

It's all moot anyhow - I can't imagine this would be high on the priority list. But it's actually fun for me in that way where talking about something you know and almost nobody else cares about is. ;)

Because all your german GMs are doing is changing translations of the ENGLISH from the ORIGINAL game, IE USAs commentary. You are not adding anything new, just messing with wording...

IF USA changed its wording, then every nation in the world suddenly gets a message that they have to retranslate, and it woudl not be an LA to do it...not sure if even GMs have access...I think it would have to be a BB to change the original ENglish tag.

than why we take english (uk) for adding new lines and keep english (us) as it is :-)

Because all your german GMs are doing is changing translations of the ENGLISH from the ORIGINAL game, IE USAs commentary. You are not adding anything new, just messing with wording...

IF USA changed its wording, then every nation in the world suddenly gets a message that they have to retranslate, and it woudl not be an LA to do it...not sure if even GMs have access...I think it would have to be a BB to change the original ENglish tag.

than why we take english (uk) for adding new lines and keep english (us) as it is :-)

The problem with that strategy is that then we'd have to see all those extra 'u's and an s instead of a z in things like localize all through the site. (Admittedly, localize isn't a word that should be in BB, but still). The easiest solution would be add something like en-US2, which basically would copy all the text from the default en-US locale but then allow for changes in some of it. If it's true that changing the base English texts would require retranslation everywhere, this is the way around that - if it's not true, this wouldn't be necessary of course.