> On Dec 18, 2015, at 2:39 PM, Maarten <netraa...@gmail.com> wrote:
>
> Just a few things:
Also, thanks for working on a Dutch translation.
>
Just some FYI,
Also, you can delete any of the comment text of you want. Add lines, etc.
The text resource file has a very strict look-up policy and everything that
does not
match the Key it is looking for at that moment is ignored. Just don’t change
anything before the = symbol.
These would all be different ID keys:
McDonalds=Not Burger King.
MCDONALDS=Not Taco Bell.
mcdonalds=Not Hardees.
And these ID keys would never be found: (because they contain spaces)
Mc Donalds=Not Subway.
McDonalds =Not Wendys.
McDonalds=Not White Castle.
Spaces are fine after the equal symbol, like:
McDonads= Not KFC.
(I’m about to eat dinner, So, food was on my mind. :-)
And any character other than Space and Equals can be used in a Key like:
**MCDONALDS**=Burgers
MC&DONALS=Fries
#MC_DONALDS:9.4?=Apple Pie
Actually, the look-up process even supports DOS and Unix line endings.
It could even work with a binary blob or executable. (provided the text was
wrapped in a CR)
Technically, The value of a key is treated like an addition to the command-line
parameters. So,
any switch or option that is supported by the related V8Power Tool can be used.
At present,
vecho, vframe and vask support the resource lookup. Most of the resource data
for text in FDI is
used by vecho.
These switches for vecho may also be of use when translating to Dutch.
/P Perform a CRLF now.
/S + Insert a space character between parameters. (DEFAULT)
/S - Do not add space character between multiple parameters.
/C code Write an ASCII character code. (like /c32, or /c0x20)
/R times Repeat the next write times number of times. (1-65535)
(Like /r5/c32 to do 5 spaces)
------------------------------------------------------------------------------
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
