RISC OS Translation ?
Pages: 1 2
Jerome Mathevet (1630) 19 posts |
Is there any desire/effort going into translating RISC OS for other languages ? I have no problem using RISC OS in english, but thought RO would “sell” more (especially with people buying RPi) if there was a mecanism to change the language for all messages of the OS. Having many untranslated apps living with a translated OS is not a problem since it can happen too in the Linux world (and people don’t seem to complain). I can dig up my translated french ressources for anyone who wants to add them somewhere (from RO4). |
Jeffrey Lee (213) 6048 posts |
There’s certainly a desire for more languages to be supported. German has been mentioned once or twice; I think you’re the first Frenchman to come forward. If you can release your French resources then that should be a good start. The build system is capable of producing multi-lingual ROMs, it’s just a case of getting all the translations we need. I wonder if there are any tools hidden in CVS to allow easy detection of which messages need translation. |
Raik (463) 2061 posts |
Here http://www.a4com.de/riscos/down/IntlTerrV120all.zip is the multilingual Terr.App. It works on my beagle with german. |
Dick Tanis (1648) 36 posts |
Hello Jerome, As a member of the Dutch Acorn/RISC OS User Group ‘Big Ben Club’ I made Dutch translations for RISC OS 3/4 in the past (http://www.dune.demon.nl/tabsoft/nl-soft.html). Currently we are developing a Dutch translation for RISC OS 5.19. We intend to release it in the spring of next year. Got a question for the ROOL team. It’s nice that multiple language support is available in the ROM but are you going to release ROM-images with multiple languages, if for example I give you the Dutch messages for RISC OS 5? We would like to know this because we are still thinking about how to the distribute our translation. |
Rick Murray (539) 13840 posts |
Isn’t this how it is supposed to work? That if you select a specific Territory, the languages appropriate to that Territory would be loaded as default (reverting to English if language blah not found)? I have two questions for the ROOL team:
1 The French have this awesome insult that is, let’s say if you say it to your boss you might not work there much longer. It’s “espèce de chameau”. Literally, you will be in a heated argument and then you will yell “you species of camel!”. Not a camel, but a species of camel. That really tickles me. |
Raik (463) 2061 posts |
I hope I have not too much misunderstood. My English is very bad. Sorry if I should have misunderstood something. |
Jeffrey Lee (213) 6048 posts |
Dick:
Good question. The German translation that Raik is using is about 400KB in size. If we add German, French and Dutch to the ROM that could be an extra 1.2MB. I’ll email ROOL and point them towards this thread, I’m not sure how official the plans are to add translations to the ROM/disc. Maybe they’ll be happy with bigger ROMs, or maybe they’ve got some other plan. Rick:
As far as I know there isn’t any tool available for tweaking territories. I think the easiest solution would be to build your own custom UK territory module.
Yes, there can be “sub-territories”. It looks like there’s only one territory for Belgium at the moment (not sure what language), but there are two for Canada, two for Russia, and (potentially) five for Switzerland. (The list is here, although I’m not sure what the warnings mean about using territory numbers > 127) |
Sprow (202) 1158 posts |
The boot sequence supports loading the territory messages/templates from !Territory, so I’m not sure there’s much to be gained by putting that data in ROM (though the build system does support it). As there are no mask ROM minimum order quantities to worry about it wouldn’t be out of the question to just make lots of 1 territory foreign language ROMs either, aside from the admin burden of checking in ~100 new sets of messages to CVS, and burning auto builder run time which is paid for through donations to ROOL. Adding some more territory modules to the ROM is on my roadmap (if ROOL will let me) since arguably they’re the bit that people can’t easily do themselves, and conversely I only have GCSE level foreign languages. There are a couple of naughty modules which aren’t internationalised which would soon come out of the woodwork.
That might be a useful starting point, but of course there are a number of extra modules and disc components in RISC OS 5, and a good number of corrections and additions to those that have been around for a while. You’d have to be really careful to make sure those are picked up.
The OS_Byte used to read and set the country has some meaning attached to bit 7, which in effect limits the number space. Ben’s comments in the UTF8 thread cover this. |
Uwe Kall (215) 120 posts |
I think that supporting different dialects would be nice but adding them into the romimage might overdo it. |
Uwe Kall (215) 120 posts |
Ah, and belgium also has a german region as well as italy.. |
Rick Murray (539) 13840 posts |
Hehe, can you imagine an OS with menus in Cockney? Or worse, various “northern” dialects? Having said this, there is a difference in regions where alternative words are used (70, 80, 90 in Belgium; navigateur in France vs the odd word the anti-English crowd came up with for Canadian French)… But this is very different to dialects, where devices are used in speech (“ee bye goom” or the Somerset abuse of “they”) which are simply not present in written language. I think a Valley Girl wannabe would freak if her computer popped up a message saying “Your computer just, like, totally went wrong, or something.” even if that is how she would have said it herself. |
Steve Pampling (1551) 8170 posts |
cough. Born in Yorkshire, living down south (midlands is south) and married to someone from the Black Country. On topic – wasn’t there an old RO programme that did translation to Valley (and others)? PS. T’ is often mispronouned by non-natives, simply because they pronounce it. It’s a glottal stop rather than an abrieviated word hence Mr. Mcintyre’s comment about the lack of “the” – imagine “Put – kettle on” with a pause where the “-” is |
Rick Murray (539) 13840 posts |
Eeeeeeek! Anything higher up the map page than the Watford Gap is “north”. As for the region known as “tThe Midlands”, that’s a sort of dusty wilderness where The North hasn’t quite started yet (so the accents are still semi-comprehensible). g,d&r |
Rick Murray (539) 13840 posts |
Looking for a possible RISC OS Valley Girl translator (I made one circa Y2K but it just bounced requests off a website so I wouldn’t count that…don’t think I ever publicly released it anyway); I noted that Google’s search is as uselessly random as ever, however, some fun stuff for a rainy Saturday:
There you go, that ought to waste half an hour of development time (or more if you actually get involved in the definition of Hymnnos !) |
Dick Tanis (1648) 36 posts |
Jeffrey Lee wrote:
Hello Jeffrey. Any news from the developers if they want to add extra languages in the official rom builds? |
Jeffrey Lee (213) 6048 posts |
Yes. As I understand it the plan is to add some extra territory modules to the ROM, but to continue to rely on !Territory for loading the necessary resources. |
Ben Avison (25) 445 posts |
There are actually quite a lot of Territory modules in CVS – they’re build variants of castle/RiscOS/Sources/Internat/Territory/Module (Australia, Canada1, Denmark, Finland, France, Germany, Ireland, Italy, Japan, Korea, Norway, SAfrica, Spain, Sweden, Taiwan, Turkey, UK, USA) – basically reflecting all the countries for which Acorn and Pace ever sold localised RISC OS products. Don’t be fooled by the Territory/Japan, Territory/UK and Territory/USA modules, they’re an older generation before the sources were merged. Starting with RISC OS 3.19 (the only localised desktop version of the OS to my knowledge), and heavily used in embedded products, the RISC OS build system lets you configure a build so that the localised resources (Messages files etc) are for some territory other than UK. This is a completely different approach from !Territory, which German, Dutch and other non-English-speaking Risc PC users are more familiar with – I guess it just wasn’t economically viable to make masked ROMs for Risc PCs for alternative localities. I don’t think the ROM modules in general currently support there being more than one set of localised resources in ROM at the same time – for example everything that tried to open Resources:$.Resources.<Module>.Messages would need to try suffixes according to the configured territory number. Not that it couldn’t be added, but it would be a tedious task. Plus, it would probably cause ROM size problems for older machines (IOMD and Iyonix) if we started putting multiple sets of resources in there. So the options are to (in the style of embedded RISC OS) produce one customised ROM per language per machine – which would mean an awful lot of ROM images – or to stick with !Territory, which I get the impression is the preferred approach in the community in general. As a native English speaker, I’ve never had to rely on !Territory. I did try one once out of curiosity, but I can’t say I’m very familiar with how it works. I don’t see any official documentation of it in the PRMs or in Acorn’s application notes – does anyone know if there ever was any documentation of it? I’m not even sure whether !Territory can hold resources for more than one language or not… |
Jerome Mathevet (1630) 19 posts |
Very interesting stuff, Ben. Where can I find a !Territory that would be ARMv7 compatible (nowhere to be found in “Downloads”) ? |
Raik (463) 2061 posts |
Take this Multilingual Territory Application (Release 1.20) full version http://www.a4com.de/riscos/down/IntlTerrV120all.zip from www.riscos.de |
Raik (463) 2061 posts |
Take this Multilingual Territory Application (Release 1.20) full version http://www.a4com.de/riscos/down/IntlTerrV120all.zip from www.riscos.de |
Jerome Mathevet (1630) 19 posts |
Ah, I overlooked your link the 1st time. Thanks Raik |
Steve Drain (222) 1620 posts |
Could someone correct me if I have got this cock-eyed, but are there two aspects to Territories? First, is to ensure a machine boots up with the correct current Territory for where the user is. I think that is the purpose of the !Territory configuration app in the absence of specially compiled roms. From what I can see it does not use standard Territory modules. Second, additional Territory modules can be loaded and then information can be derived from them through the Territory SWIs. The current Territory can be changed if the appropriate Territory module is loaded. In the latter case, there seemed to be a dearth of Territory modules publicly available, but perhaps I should trawl the CVS. My interest in this was with the datetime keywords in Basalt I wrote some years back. I found it tricky testing them because I could only change current Territory by re-configuring and rebooting. Was there an easier way? |
Sprow (202) 1158 posts |
That’s right. If on boot up the configured territory module is found to be absent it is searched for in various likely places (NetFS, the boot drive, possibly some others I forgot), and if in none of those places you get the big blue floppy disc icon to invite you to load the stuff off floppy.
You should still have the modules I put online from when you asked that exact same question last time, no? The (slow but steady) process of ditching dead wood modules is in preparation of putting the territory modules in ROM. |
Steve Drain (222) 1620 posts |
Yes, I do have them, and I tested with them, many thanks. But that was only 3. I think that still counts as a dearth. ;-) Is the !Territory application the one I have on my RPC written by Andreas Feldner et al from 2004? Else there is a confusion of names. AFAICT that one uses a patching method to implement territories, not modules. |
Sprow (202) 1158 posts |
They were carefully chosen to give you one sample of each of -ve, 0, +1, large +ve timezones, any more would cause unnecessary wear on my index finger. |
Pages: 1 2