Hi Rafaella,
Rafaella Braconi schrieb:
Hi Gregor,
Gregor Hartmann wrote:
Hi,
I am planing to change the sdf fileformat slightly.
there is the 3. filed in every line which seems to be unused.
which information is currently stored in the 3rd field?
I would like to use it to store information like the new KeyID
you mean the unique keyid which we can use both internally and with the
Community?
yes, but I woild rather not store it there permanently as it would be
redundant.
and other things which will help to identify strings which will have
to be retranslated after the sourcestring has changed, but that is
still to come.
When do you think it should be possible to store the unique keyids?
Anyways tzhe change would be to have a formated string in the 3. field
of the sdf file (right after the filename)
It should look like this:
fieldname:fieldcontent;filed2:data2;field3:data3
Can you please provide a couple of examples based on real strings? That
might help understanding better the new structure you have in mind....
keyid:se432q;sourcehash=ncmkuiwgtyxuzfngildhjfgnt
and so on, as required.
Would that break anybodys processes?
I think that it is critical to make sure that we can import translated
files in the current sdf file format as well as the new one. BTW: do you
think that it will be necessary to rename the updated sdf file name to
distinguish it from the current one?
I hope tools will not need to get changed too much, so that we can stay
with the sdf file extension. Currently it would not matter if the
content would get lost. but in the future at least the sourcehash filed
has to be persistent.
Gregor
Thanks,
Rafaella
If noone objects I would like to go on next week.
Comments as always welcome.
Thanks for your attention
Gregor
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
