Where can I find lang. files? I want to translate it.
amar
-
- Posts: 3
kimikelku
-
-
- Posts: 61
I guess you'll need to wait until there is a beta version for the public to start translating, since alot of things can change while nao is working on the project.
amar
-
- Posts: 3
I guess you'll need to wait until there is a beta version for the public to start translating, since alot of things can change while nao is working on the project.
Nao
- Dadman with a boy
-
-
- Posts: 16,079
If you're comfortable with using Git, I'm planning to release the language files to a special repo over there, and allow you guys to submit pull requests.
Nao
- Dadman with a boy
-
-
- Posts: 16,079
This is the desired format for French language files (for instance):
FORUM_ROOT/languages/index.french.php
This is the desired format in a tentative repo:
REPO_ROOT/French/index.french.php
I can easily have plugins in a separate repo because I'm using the repo as my Plugins folder in my local Wedge install, and I don't have to copy files. But I can't maintain a language repo the same way, because a 'professional' repo would need to separate all languages clearly, when the Wedge repo will require languages to be all in the same folder -- mostly because it's then easier to update by FTP.
Any solutions, maybe..?
FORUM_ROOT/languages/index.french.php
This is the desired format in a tentative repo:
REPO_ROOT/French/index.french.php
I can easily have plugins in a separate repo because I'm using the repo as my Plugins folder in my local Wedge install, and I don't have to copy files. But I can't maintain a language repo the same way, because a 'professional' repo would need to separate all languages clearly, when the Wedge repo will require languages to be all in the same folder -- mostly because it's then easier to update by FTP.
Any solutions, maybe..?
Bump for ideas on how to 'solve' this problem with the folder structure...
forumsearch0r
-
- Posts: 118
You might also want to consider that languages like German have a formal and an informal "sublanguage", so just taking the name of the language might narrow it too much.
Nao
- Dadman with a boy
-
-
- Posts: 16,079
Well, British language files in Wedge are called 'index.english-uk.php', so that would be a 'English-UK' folder, so an 'English' folder still makes sense, of course.
forumsearch0r
-
- Posts: 118
Depends which English is "the" English.
Nao
- Dadman with a boy
-
-
- Posts: 16,079
I've already discussed it. The main language, to me, is the most commonly 'written' one, on the Internet. US English is spoken by more people than British/UK English (even if you count Irish, Canadian, New Zealandish (?) and Australian variations into it, and whatever else might exist), so it gets to be the 'default' choice for me. If there were more French-Canadians speaking French, the default French language version would have tabernacles and crisses de calisse all over it. Well, I don't know why I'd have to use expletives in the translations, but whatever. :P
Still bumping for ideas on how to deal with the languages repo.
Possible solutions:
1- Just have everything in a single folder. Very, very messy, but whatever.
2- Keep English and French in the root, and have other versions in sub-folders. Meaning I'd probably drop support for other languages on wedge.org if I can't bother to update these folders here.
3- Have all languages in different subfolders, and expect me to systematically update my root languages folder with the files, everytime I apply a change. Don't count too much on that.....
4- Use some sort of symlink system that would allow me to use a separate repo with one folder per language, but have all of these folders' files (or at least most of the current ones) show up in my local Wedge repo's language folder. This is what I've been looking into, but I just have one problem: I have no idea how to do that. I'm aware that NTFS allows for 'proper' symlinks, i.e. hardlinks à la Linux, not silly 'shortcuts' à la Windows 95, I even have a program that moves games around on my hard drives and still lets them run without reinstalling (thanks to hardlinking), but I don't know how I'd do that with Wedge, plain and simple.
So... Again, opinions welcome! I'd like to do the languages repo next, really. That's REALLY the very first repo I'll be expecting contributions to, and I can't wait for that. (At the current point, it's unlikely that the language files are going to change a lot. Manipulating them was Pete's habit, but personally I prefer to avoid playing with them if I don't have to.)
Possible solutions:
1- Just have everything in a single folder. Very, very messy, but whatever.
2- Keep English and French in the root, and have other versions in sub-folders. Meaning I'd probably drop support for other languages on wedge.org if I can't bother to update these folders here.
3- Have all languages in different subfolders, and expect me to systematically update my root languages folder with the files, everytime I apply a change. Don't count too much on that.....
4- Use some sort of symlink system that would allow me to use a separate repo with one folder per language, but have all of these folders' files (or at least most of the current ones) show up in my local Wedge repo's language folder. This is what I've been looking into, but I just have one problem: I have no idea how to do that. I'm aware that NTFS allows for 'proper' symlinks, i.e. hardlinks à la Linux, not silly 'shortcuts' à la Windows 95, I even have a program that moves games around on my hard drives and still lets them run without reinstalling (thanks to hardlinking), but I don't know how I'd do that with Wedge, plain and simple.
So... Again, opinions welcome! I'd like to do the languages repo next, really. That's REALLY the very first repo I'll be expecting contributions to, and I can't wait for that. (At the current point, it's unlikely that the language files are going to change a lot. Manipulating them was Pete's habit, but personally I prefer to avoid playing with them if I don't have to.)
Norodo
-
-
- Oh you Baidu, so randumb. (60 sites being indexed at once? Jeez)
- Posts: 469
Stick it all in the database.
;)
;)
Nao
- Dadman with a boy
-
-
- Posts: 16,079
Well, Pete did that for BBCode, and we know how it ended... No UI to modify the codes, and if I happen to consider changing the default code for a tag, I'll have to ditch my table and refill it.
Also, it doesn't help with uploading modified files by FTP... :^^;:
Unless maybe Wedge started doing something revolutionary, like updating any and all of its files through the github repo... In which case, well, I guess for one it totally rocks your house, and for two it's a recipe for disaster... :P
(Although, I'll point out that it worked quite well with Aeva Media, but it was only with the site list, NOT with the mod's files!)
Also, it doesn't help with uploading modified files by FTP... :^^;:
Unless maybe Wedge started doing something revolutionary, like updating any and all of its files through the github repo... In which case, well, I guess for one it totally rocks your house, and for two it's a recipe for disaster... :P
(Although, I'll point out that it worked quite well with Aeva Media, but it was only with the site list, NOT with the mod's files!)
So, here's the current structure...
In the Wedge repo:
(root)
/core
/languages
- all English files
- all French files (<-- might possibly go.)
In the languages repo:
(root)
- all English files
- all French files
/english-uk
- all English UK files
/german
- all German files
Basically, whenever I make a change to an English file, I'd commit it to both the Wedge repo and languages repo, so that a Wedge package can easily be made out of the repo.
This causes the issue that, technically, it's a waste of repo space to duplicate these files. I was thinking of going for a submodule system for language folders, but I think there are issues with keeping both repos in sync, and whether Github can include the external repo in any automatically generated zip files..?
Anyone got experience with this..?
In the Wedge repo:
(root)
/core
/languages
- all English files
- all French files (<-- might possibly go.)
In the languages repo:
(root)
- all English files
- all French files
/english-uk
- all English UK files
/german
- all German files
Basically, whenever I make a change to an English file, I'd commit it to both the Wedge repo and languages repo, so that a Wedge package can easily be made out of the repo.
This causes the issue that, technically, it's a waste of repo space to duplicate these files. I was thinking of going for a submodule system for language folders, but I think there are issues with keeping both repos in sync, and whether Github can include the external repo in any automatically generated zip files..?
Anyone got experience with this..?