Sure, i have to translate it anyway and when integrated in core
everyone benefits.
So how are we gonna do that?

Should i only supply the resource bundles and you will use them to
update the next version (so put in the variables yourself).

Or should i supply resource bundles and updated core code, and if so
which version etc?

With version locking i meant, for example, deciding to just use FC
5.1.6, make it work and don't update anymore. Then i could update core
stuff etc without the problem being overwritten by updates, but that
isn't the case here anyhow.

On Aug 4, 1:23 am, Blair McKenzie <[email protected]> wrote:
> If you would like to supply translations of core bundles that's a different
> matter. We'd be delighted to put that into core.
>
> What do you mean by version locking?
>
> Blair
>
> On Mon, Aug 3, 2009 at 10:28 PM, Marco van den Oever <
>
> [email protected]> wrote:
>
> > I am a bit in doubt, i see a lot of core stuff that needs to be
> > translated, now i can go and do that but that would make any future
> > updating to newer core a problem.
>
> > How do i handle this? Is this something you can't solve anyhow and is
> > a reason why "version locking" exists?
>
> > Can people share their insight / experience on this?
>
> > Thanks.
>
> > On Aug 3, 1:39 pm, Marco van den Oever <[email protected]>
> > wrote:
> > > I have bundled all issues and suggestions in this bug:
>
> > >http://bugs.farcrycms.org/browse/FC-1961
>
> > > I don't want to change stuff in core types so that updating will be
> > > harder.
>
> > > On Aug 3, 5:57 am, Blair McKenzie <[email protected]> wrote:
>
> > > > New resources can't be added automatically to the file, as it would
> > take too
> > > > much processing time. The internationalisation
> > > > page<
> >http://docs.farcrycms.org/display/FCDEV50/Internationalisation+%28i18..
> > .>on
> > > > the wiki should cover most of what you need for updating and adding
> > > > resource bundles. Or maybe it needs to be improved, let me know.
>
> > > > Blair
>
> > > > On Sun, Aug 2, 2009 at 8:37 PM, Marco van den Oever <
>
> > > > [email protected]> wrote:
>
> > > > > Another question.
>
> > > > > Right now in a type the "displayname" attribute is used to show the
> > > > > title in the type listing admin.
>
> > > > > Of course you can override it with the "title" attribute in the
> > > > > customlist page.
>
> > > > > My question is, what is the correct way to set variables for type
> > > > > titles that are shown in the listing admin in:
>
> > > > > <admin:header title="Tickets Administration" />
>
> > > > > and
>
> > > > > <ft:objectAdmin title="Tickets Administration".
>
> > > > > Is there a official way (format) of doing so or can i just set a
> > > > > variable and output it in those "title" attributes?
>
> > > > > I don't currently see it in the admin.properties file between other
> > > > > objectadmin.bla...@label variables.
>
> > > > > On Jul 31, 3:03 pm, Marco van den Oever <[email protected]>
> > > > > wrote:
> > > > > > What a awesome feature it is :)
> > > > > > I saw that not all items are translated yet, so couple of
> > questions.
>
> > > > > > Does anybody already has a full translated version?
> > > > > > If not, is anybody working to fully include all farcry elements to
> > be
> > > > > > translated?
>
> > > > > > Further, just to be sure, when no one has or gonna attempt a full
> > > > > > translation i need to translate it myself, i am using FC 5.1.6, can
> > i
> > > > > > translate with the current files included in that version and are
> > > > > > these files being active for Farcry as they are?
>
> > > > > > Or is the advice when doing so first update to FC 5.2?
>
> > > > > > Thanks.
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message cos you are subscribed to "farcry-dev" Google group.
To post, email: [email protected]
To unsubscribe, email: [email protected]
For more options: http://groups.google.com/group/farcry-dev
--------------------------------
Follow us on Twitter: http://twitter.com/farcry
-~----------~----~----~----~------~----~------~--~---

Reply via email to