Norodo

  • Oh you Baidu, so randumb. (60 sites being indexed at once? Jeez)
  • Posts: 469
Re: Lang. files?
« Reply #15, on January 13th, 2014, 11:49 AM »
I have no experience with that, but I know I'm going to get started on a Norwegian translation as soon as possible. Is there a thread for coordinating language efforts?

Nao

  • Dadman with a boy
  • Posts: 16,063
Re: Lang. files?
« Reply #16, on January 13th, 2014, 01:00 PM »
Not for now; but there's the last blog post where you can start a reply or something, then if needed, I'll move it to a new topic, and then eventually (if Wedge gets any success), to its own board.
Re: Lang. files?
« Reply #17, on January 13th, 2014, 01:08 PM »
Re: my question, I decided that French didn't really justify being included in the main repo. I mean, who here speaks French, apart from me..??!
I'm not going to bother everyone with my stuff.
I'm still leaving French at the root of the languages repo, but it will no longer be in the Wedge repo.

So, basically, I have a /core/languages/ folder, which contains only the *.english.php files in the Wedge repo, but on my local repo, it also contains French files, because my /core/languages folder is also a copy of my languages repo. See what I mean..? It just means that everytime I'll make a change to the English files, I'll have it in a 'committable' state for both the Wedge and languages repos. So, from now on, English changes will be exactly duplicated between Wedge and languages repos, taking a bit more space, but making it easier to quickly generate a 'working' zip of Wedge.

wedge.helmer.co

  • Grumpy Old Man
  • Posts: 18
Re: Lang. files?
« Reply #18, on January 13th, 2014, 08:27 PM »
I think you should have at the languages in the same folder. It makes things in the long run a hell of a lot easier. Think about it for a minute, you have a new translation, you ftp it to the Languages folder and it instantly becomes available for use by Wedge just like English, English-UK and French.  Also for any mods, all language files are in the one directory were authors do not have to add or remember directory names for each language.

Plus you would have to predefine in advance each language directory name and add code to link the directory. Also the language tree consists of one directory instead of many which is less messy.

Just my thoughts.


John

Farjo

  • "a valuable asset to the community"
  • Posts: 492
Re: Lang. files?
« Reply #19, on January 13th, 2014, 08:51 PM »
Why does english need to be in the language repo if is is in the main repo? Nobody will download the english files because they already have them.

Nao

  • Dadman with a boy
  • Posts: 16,063
Re: Lang. files?
« Reply #20, on January 14th, 2014, 12:22 AM »
@Farjo, because then translators only need to check the languages repo for any changes, they don't have to subscribe to notifications for the Wedge repo just to do their (unpaid!) job.
Quote from ftab4me on January 13th, 2014, 08:27 PM
I think you should have at the languages in the same folder. It makes things in the long run a hell of a lot easier.
Again-- languages can still be put into the same folder. (In fact, right now, it's the only way to add a language -- you FTP the files to the languages root folder.)
There are separate folders in the languages repo to make it easier to handle language files for both translators and users. They download the language repo, then they extract the language files from the folder they want, into their languages folder's root.
I'm only putting the French language files at the root alongside English files because I'm the author, and I don't want the hassle of entering two folders to update my site by FTP, instead of just one.
Quote from ftab4me on January 13th, 2014, 08:27 PM
Think about it for a minute, you have a new translation, you ftp it to the Languages folder and it instantly becomes available for use by Wedge just like English, English-UK and French.  Also for any mods, all language files are in the one directory were authors do not have to add or remember directory names for each language.
Plugin language files are expected to remain in the plugin's personal folder. There's a language call (loadPluginLanguage) that replaces loadLanguage, and takes the plugin's ID into account to find the location of the language files. This is as designed by Arantor; I don't see any reason to change that. (Not taking into account the fact that I'm left the only maintainer of the plugin system now, and I've never actually used it, so that'll be a lot of fun[1]. The other two people who were making plugins for Wedge left this place some time ago, possibly because of real-life duties, or simply because they chose to go back to SMF too, I don't know, I'm no longer at SMF.)
 1. Which is why I'm in early plans of restoring some kind of SMF mod functionality in that you'll be able to modify source files like a regular mod, BUT it won't break your website if done incorrectly. I'll talk about that later.