texts&words, importing fields such as Reference

[Ellen Smith-Dennis]

Hi everyone,

I'm working in Texts and Words, and importing Standard Format Interlinear Texts, but there are certain fields which don't appear after the import.

For \rf, the FW Destination is 'Reference'. But I can't see the location of 'Reference' in Texts&Words. 

Then I have another field I want to import, which contains the original recorded orthography, but there aren't enough destinations available when modifying the Mapping. I've tried creating a custom field (which appears in the Gloss tab) but that custom field does not appear in the list of mapping options. 

Both of these fields do successfully import when I'm working in Lexicon, but not in Texts&Words.

Any suggestions?

I basically want to end up with a text which has this kind of structure in the Gloss tab:

1.1 Word/Sentence

Morphemes

Gloss

Free translation

Literal (original) translation

Original orthography

Note

(Source&page) reference

1.2 Word/Sentence

Morphemes

Gloss

Free translation

Literal (original) translation

Original orthography

Note

(Source&page) reference

etc.

Thanks in advance,

Ellen 

[Andreas_Joswig]

Dear Ellen,

I don't have a good response about the reference field, but hopefully a better idea on how to handle the original orthography. This should not go into a custom field, but should be addressed by a defining a different writing system. Once you have two writing systems for the vernacular language, each field using the regular writing system will also show up in the import mapping as available to receive information in the other writing system. So you would have a word/sentence field for the regular orthography, and another one using the other writing system. 

As for the reference: FLEx texts only have a reference (called source) for the whole text, which is set in the metadata of the text (the Info tab). So you cannot map any references to individual sentences in FLEx - FLEx then automatically counts the sentences, thus providing a more detailed reference. If you want to maintain the original reference from Toolbox, the best way to do it would be to store it in the Note field. I also see that FLEx doesn't allow me to create a custom reference field, as there already is one - this is indeed not visible in texts, as it is only used by the lexicon, as far as I can tell.

Andreas

--
"FLEx list" messages are public. Only members can post.
flex_d...@sil.org
http://groups.google.com/group/flex-list.
---
You received this message because you are subscribed to the Google Groups "FLEx list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flex-list+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/flex-list/82841a62-dc8a-485c-8203-db222bbf2143n%40googlegroups.com.

[Ken Zook]

Hi Ellen,

 

There is a Reference property on the interlinear Segment, and the SFM import will import the reference field into the project. Unfortunately, there isn’t any way to display it from the Reference field. You can create a custom field on interlinear segments and configure that in the Analyze tab to show, and it can be moved to the top of the segment fields, but it can’t be moved to the top of the interlinear bundle. In the Gloss tab, you can make the custom field show, but for some reason you can’t move it in the configuration. The other major problem is that you can’t assign anything to a custom field in the SFM interlinear import dialog. So at this point the best you could do to get the reference into something you can see is to import it into the Literal Translation or some other standard segment field. And still, you can’t get it to the top of the bundle as you would like.

 

The other limitation is on the Gloss line. I assume you are wanting this to show up in the Gloss field within the wordform. The SFM import does not provide any option to import the gloss in an analysis.

 

Sorry, this isn’t a very satisfactory answer.

 

Ken

To view this discussion visit https://groups.google.com/d/msgid/flex-list/17194683-dc47-4cbe-8b3f-f4e1caf009ef%40sil.org.

[Ellen Smith-Dennis]

Dear Andreas,

Thanks for your help. I tried your first suggestion, but it imports the regular/new orthography as line 1.1, with all the other information beneath it (translation, notes etc) and then it imports the original orthography as line 1.2, but the fields below are empty. Really, I want to see the original orthography as a field similar to the translation or note fields. Any ideas of how to do that? 

e.g. 

1.1 Word/Sentence

Morphemes

Gloss

Original orthography

Free translation

Literal (original) translation

Note

Thanks, Ellen

[Ellen Smith-Dennis]

Hi Ken,

Thanks for your help.

So, to double check - when importing SFM texts and you're specifying the Destination, you can assign markers 'Source of text' and 'Reference' destinations, but the 'Reference' field doesn't actually appear anywhere in Texts&Words after the import? And any custom fields you create, you can't actually assign a marker to that field?

Are there any other standard segment fields besides the following?

thanks, Ellen

[Andreas_Joswig]

Dear Ellen,

Please approach me off-list, best by sending me a link to your standard format project. I can then see what can be done to get it into the shape you need.

Andreas

To view this discussion visit https://groups.google.com/d/msgid/flex-list/093e34b8-5e2d-4937-9e39-dc119870a488n%40googlegroups.com.

[Natalia]

Dear Ellen,

To see the reference for each text unit that I assign prior to importing texts into Flex, I use a translation language that I know I will not be using (in my case German). For other custom fields like the original transcription if it is in a different orthographic system, I also proceed in a similar manner (configuring Latin as one of the analysis languages within the project).

Note that, as Ken Zook mentioned earlier, the information in the reference field is indeed assigned to each interlinear segment but there is no option to show (and eventually update this information after resegmentation). So you might want to double the information if you want it both as something that Flex can read and that you can read.

As for the line 1.2 having the translation fields empty, the workaround is to not use any of the punctuation marks with which Flex automatically creates a new interlinear segment (period, question and exclamation marks) so as to never have a subsegment. You could for example use a different consistent symbol for each punctuation mark.

Hope that helps!

Natalia

[Ellen Smith-Dennis]

Thank you for the help, Andreas and Natalia - using multiple Note fields and Translation fields with different writing systems seems to be a good solution.