Jump to content

Jazira

Members
  • Posts

    217
  • Joined

  • Last visited

Everything posted by Jazira

  1. That looks interesting. Thank you for this.
  2. Hello, I hope this is not already reported. Moon Dog Sight (SPIN696.SPL bg2ee @103003), from Cerebus (MOONDOG.CRE), from Moon Dog Figurine (MISC7T.ITM) This ability states that it detects traps but it doesn't. There, that's all for me. Thanks.
  3. Thank you both, you rocks! To give an idea to what it look like: @3="Dur[^e]+e[^:]*:" // must exactly match duration in BG version of 'protection from fire' @4="1 tour par niveau" Here @4 is correctly displayed but @3 is not. @3="Durée :" // must exactly match duration in BG version of 'protection from fire' @4="1 tour par niveau" Here @3 is correctly displayed but @4 is not.
  4. Hello David, This is nowhere to be found on IWD:EE. I suspect @19 in Spell.tra to be just the post patch version of @18, am I right?
  5. Alright, I'm afraid I could not help much. Just in case, to replace accented characters or non-breaking space, it seems the following should work with Weidu regexps: "créatures" -> "cr[^a]+atures"
  6. Maybe we could provide some insights, what's the problem with ToF exactly?
  7. Maybe something to do with the new acces path lang_som?
  8. I'm sorry, David, you can dismiss this bug report. It's on me, I just realized that I've installed 35.6 selecting English game language while it's on French. So, yeah, everything was buggy indeed. Closed.
  9. Hey David, just a reminder that the first post with the translation locations need to be edited: Files to be translated are now in "stratagems\iwdspells\lang", "stratagems\lang", "stratagems\lang_som", and "stratagems\sfo2e\lua\lang".
  10. Happens on the special abilities "spells" and the items themselves. edit: and descriptions Edit 2: OP is dumb
  11. Hello again, David. Things are advancing at a good pace, but I have a few uncertainties that I'd like to clear up. The Rod of Resurrection, item.tra, everything is ok? Are the added details correct? The range parts, for example. I've been unable to test ingame. Next are the dagger "Nome Stikka" and the arrow "Deth Stik", kobold.tra. Are the details correct, especially the poison and save parts? I've been unable to test ingame. (https://www.gibberlings3.net/forums/topic/37575-kobold-items-dont-seem-to-apply-any-poison-effect/) Lastly, I haven't edited yet "Stone Fist" or "Pebble" inside extra_arcane_spells.tra. Could you provide me some details about the fix and the actual statistics of the items, please? (https://www.gibberlings3.net/forums/topic/37498-stonefist-description-looks-wrong/) I still have a few items to edit, but they will be done soon. Do you wish me to provide the English proofread (with the item format revision) as soon as possible? So, if you want, you can implement them rapidly or is this not an urgent matter? I imagine this is a stressful period for you, I hope I'm not overstepping.
  12. This is a known bug: The same happens with fine weapons component.
  13. If you want, I can help you out with some inactives pre-digested entries for every item, I'm doing some English proofreading alongside the French translation at the moment anyway. You could cherry-pick anything you want from it.
  14. Thanks, that's greatly appreciated. Try to avoid it as much as you can, because remember, we're dumb and lazy. But when there is no choice but to do it, fine, it's understandable. We'll call the lesser dumb and lazy to help us out.
  15. Alright, that's good to know. I can tell you that 99% of translators won't know this before trying to translate it. We're too lazy to check out all the scripts, and even if we do so, we're too dumb to figure it out. Still, there is something that bothers me. Vanilla and EE formats of anything below "STATISTICS:" greatly vary. Here is an example to compare: Vanilla EE Usually, we translators try to uniformize the formats to be seemingly the same as what the official content is. Here, even the descriptions vary. I still think that having two entries/files for each item, EE and vanilla is the best. For all languages. But that's your choice, we will adapt nonetheless. On a side note, I'll add that I feel a bit annoyed to be held back by the "deprecated" format of vanilla items for unique entries, most players are on the EE nowadays. Real question, what makes you choose this way (strips out (2) and (3)) instead of having 2 entries/files?
  16. Hey, Inside the setup.tra, what is the exact strref of the "Stratagems spell tweaks" component? @50013 = ~This component is now included in the 'Stratagems spell tweaks' component~ Also : @233 = ~Restoration and Lesser Restoration spells heal ability-score damage~ Is "Restoration" alone intended as it is? Or should it be "Greater Restoration"?
  17. This option could work too. But it brings me to something I'd wished to express for a while. A bit of criticism toward how SCS (and any mod) handle scripts to edit tiny parts of an entry instead of replacing the whole. I understand this is to maximize eventual compatibility but I find it a bit rather counter productive, and very difficult for translators, who usually don't have the same level of knowledge (regex for example) than say, a modder. We have this example with the Spellhold cost component and non-breaking spaces, as Alywena stated. But there are many others too, like in dw_iwdspells.tra: I find it overly complicated, add tons of investigative work (just BG2, for example got 4 sets of French localization: obg2, CorrectfrBG2, bg2ee and CorrectfrBG2EE with massive differences), and we don't even know if it covers every case possible. AND regex, additionally with non-breaking spaces, does not handle special characters (éèïîêôûù, etc.), very common in some languages, at all. I'd rather have something that replaces the whole entry than that. And eventually, we (the French translators) could remove the non-breaking spaces directly on unique entries to ensure compatibility for both EE and vanilla since it's our "shit" to deal with and it does not matter that much to have or not non-breaking spaces at the end.
  18. French translators use this rule: EE Baldur's Gate uses non-breaking spaces (before [;:?!%»], in the "middle" of [0-9]{4,} (1 500, 10 000, 25 000) and after [«]), vanilla Baldur's Gate does not. If a mod is compatible for both, then there are two options to translate: - Either the mod provides two sets of files/entries for every item, one for EE, one for vanilla. (This is the best option, for all languages, since the format of anything below "STATISTICS:" (and the item title) is not handled the same by the engine in EE and vanilla) - Or, there is a single file/entry for every item. This means that the translator has to adapt the EE format of anything below "STATISTICS:", be sure to remove every non-breaking space, and add a "(not )usable by:" for the vanilla users. BUT, the EE users will have "(not )usable by:" twice because it is automatically generated by the engine. Same for the item "title", the item name has to be directly in the description for vanilla users. But it is automatically generated on EE, so EE users will have 2 titles. In my opinion it would be best, for all languages, if we got two sets of files/entries for any item present in any mod compatible for both vanilla and EE.
  19. Can confirm. Happens on BGEE/SoD/BG2EE. The tpa point out to incorrect strrefs.
  20. Oh, and the Telekinesis spell in the same file seems to be missing the spell level (Level: ?).
  21. Hey, I don't know if it have already been evocated but the spell description of Stonefist and it's assiociated item feel off:
×
×
  • Create New...