Reply to Re: Too match text I think.

Your name:

Reply:


Posted by Steve on 10/13/06 20:54

".:[ ikciu ]:." <no@mail.com> wrote in message
news:egojrk$ka8$1@news.dialog.net.pl...
| Hmm Steve <no.one@example.com> wrote:
| > ok, don't just drop a bomb and run. support your oppinion with fact or
| > experience so that fritz can learn. from my standpoint, the ONE FILE
| > approach is VERY hard to manage on a scale of
| > languagesSupported*(amountOfText/2)^2...and i mean that literally in a
|
| nope you have only ONE file if you want to make changes you will do it in
| only one file not in X


i said SUPPORT your oppinion...NOT RESTATE IT! you're telling me that you
want to search ONE FILE that has MULTIPLE sections where language text needs
to be maintained and update them all WITHOUT making a mistake...EVER.
ROFLMFAO. have YOU EVER programmed with i18n in mind?!

how do you overcome the memory wasted in pulling in ONE FILE when only a
small portion of it is needed?

i say again, SUPPORT your oppinion with FACT or EXPERIENCE...NOT UNINFORMED
PREFERENCE.

| > mathematic scale of difficulty. PLUS, ONE FILE will become quite
| > large and when included, consumes an *enormous* amount of memory if
| > supporting very many languages. using a SINGLE file eliminates BOTH
| > problems. what leads you to another oppinion?
|
| just make template for example
|
| <div id="data">
| <h1>{title}</h1>
| <p>{body}</p>
| </div>
|
| 1. in session you will store current language
| 2. when you will show data just get adequate text (language) - for session
| language variable from db or xml file
| 3. put it into your template
| 4. have fun

first, you DON'T need templates AT ALL. a simple translation function
suffices:

<h1><?= language::translate(phrases::$helloWorld, language::en_us) ?></h1>

not saying one is better than the other, just that you aren't limited to
just template based design.

1. store the current language...no shit?!
2. you: pull in one enormous file and parse to get to the right section.
us: pick the correct language file (smaller by leaps and bounds) and
parse.
3. again, no shit?!
4. actually program i18n first, then continue to drivel.

[Back to original message]


Удаленная работа для программистов  •  Как заработать на Google AdSense  •  England, UK  •  статьи на английском  •  PHP MySQL CMS Apache Oscommerce  •  Online Business Knowledge Base  •  DVD MP3 AVI MP4 players codecs conversion help
Home  •  Search  •  Site Map  •  Set as Homepage  •  Add to Favourites

Copyright © 2005-2006 Powered by Custom PHP Programming

Сайт изготовлен в Студии Валентина Петручека
изготовление и поддержка веб-сайтов, разработка программного обеспечения, поисковая оптимизация