Loading...
 
Multi-Language Add-In for Visual Studio

Multi-Language Add-In for Visual Studio

Forum List Topic List

Forums > Multi-Language Add-In for Visual Studio > Problem with DropDownList/ListItem in ASP.NET WebForms
 
Thread actions
Print this page
  • Print all pages

    • Problem with DropDownList/ListItem in ASP.NET WebForms

    Posted by jan-marten on Thu 11 of Feb, 2016 06:58 GMT

    We experience two issues while translating ASP.NET WebForms which contain multiple DropDownLists.

    1. Duplicate ListItems are added (see attached image, ListItemResource4)
    2. The Values of the ListItems are automatically saved as resource. Even after unchecking the boxes it is automatically checked again after refreshing/rescanning the list.


    The duplicate ListItemResource is created when adding a ListItem to the first DropDownList.

    I am using the latest version of the tool (version 6.01.0011) with Visual Studio 2015 Professional.

    Image

    Reads: 14183
    Link
    Posted by Phil on Thu 11 of Feb, 2016 21:20 GMT Germany

    Hi Jan Marten

    I have copied the image into your post (which is something normal users cannot do). I think that there is probably a bug in the attach function. The file you originally attached is 3 byte longer than the good file, because a Byte Order Mark (BOM) has been added to the start of the file (hex EF BB BF) which makes no sense for a binary file.

    I have uploaded a new version (6.1.13) of Multi-Language which I hope will fix this problem.

    It was a pretty stupid programming error on my behalf.

    The list item with the text "Value1.5" does not have a meta:resourcekey in the original file, so Multi-Language generates one. Obviously, it should generate a key which is unique in the whole file. In fact it generated a key which was unique in the names encountered so far, but not in the whole file.

    Phil

    Link

    Posted by jan-marten on Fri 12 of Feb, 2016 08:06 GMT

    Great. That works.

    Now for the second issue where the Value is stored as resource too after a full-rescan.

    1. Add a ListItem and enter a Value and a Text
    2. Do a Full-Rescan
    3. Check the new text to be translated
    4. Do a Full-Rescan again
    5. Now the Value is checked as well (and thus translatable)


    That is not wat I would have expected.

    Link
    Posted by Phil on Sat 13 of Feb, 2016 18:24 GMT Germany

    I agree. I have taken a closer look and decided that the behavior is incorrect.

    If a tag already has a meta:resourcekey attribute, then Multi-Language was automatically selecting other attributes for translation. There is no real reason to do this, unless relevant resource strings have already been defined.

    I have changed the behavior in version 6.1.14 so that attributes are only automatically selected, if corresponding resource strings already exist.

    Phil

    Link
    Posted by jan-marten on Wed 17 of Feb, 2016 11:12 GMT
    Thanks for the update.
    Link