@bplex
Okay, I have a lack in php knowledge, I'll grant that. But considering the fact that I'm working 60 hours per week with html, javascript, perl/cgi, serious graphic arts, translations, etc. there isn't a lot of time or patience left in my brain to start learning more on php. I have a family, child, 2 large dogs, and they're already unhappy about my work load. Having said that, and believing that I'm not entirely stupid, I still have to disagree somewhat with the php guru bplex though, because ....he is going to need an open-source script. He can spend as much time as he would like on vShare. It's just not going to do him much good.
.... I've been working with code for the past 14 to 15 years and one of the biggest clues that I look for when working with translations, is the specific manner with which text is embedded into the code and command lines. For example, code is at least 99.99% of the time written in small letters (not including html tags which could go either way). So, when I see a line of code with something like 'Pending' or "Year" then it's the capital letter P or Y which indicate to me that this is merely a REFERENCE that is being used by the file that I'm looking at, and by very specific files that have command lines of sorts which are in turn referring to those specific words. Hence (and like I said, I've been doing this for years, writing translations that actually work) if I knew the names of all of the files with such exact references, then a modified global search and replace command can actually change those to whatever you want ... and still work ... as long as you're not using special characters (and even that can actually be done with yet more patience and time). The problems that I'm having with the translations aren't actually nearly as complicated as bplex infers. It's just a matter of knowing WHICH files and WHERE they're at, period. Zend encoding or not, doesn't make a difference if you have the right software!
EXAMPLE (hypothetical): The SQL DB, 12 Template files, 6 more hidden files within includes, and 47 additional files thoughout the video portal utilize the word 'Pending' in order to jive all across the board. Well, if I knew the specific names and locations of all 65 files (not counting the SQL), then I could change 'Pending' to 'Geewillickers' and guess what? Yes, it would all work just as well as it did before ...
But ... no problem. I'm giving up looking on the forum for translation assistance. I'll write to the support directly and hopefully will get something out of that. This Sunday I'll look at the sql db which I've already extracted in order to see if I can find something in there. Eventually all will be well, I was just hoping that I wouldn't have to tediously "snipe" at dozens or even hundreds of files over the course of months, while knowing that the developers could provide assistance in a matter of minutes, if they cared or wanted to.
Hey, have a great upcoming weekend and please keep an eye out for my other posts, the ones that have nothing to do with translations. It's been a pleasure and I really do appreciate every useful bit of information.
.
Bookmarks