14 Replies Latest reply on Jul 16, 2008 10:31 AM by Newsgroup_User

    =?iso-8859-1?Q?Problema_con_acentos_y_=D1_utilzando_ADOXtra.?=

    Level 7
      Cuando utilizo una etiqueta de texto, puedo teclear sobre ella caracteres
      con acento y Ñ sin ningún problema, pero cuando su contenido lo cargo con
      ADOXtra a partir de una base de datos de Access, se me muestran caracteres
      extraños.

      He probado eso de añadir la fuente al proyecto pero sigue sin funcionar.
      Utilizo el Adobe Director 11.

      ¿Alguna sugerencia?

      Muchas gracias y un cordial saludo.

        • 1. Re: =?iso-8859-1?Q?Problema_con_acentos_y_=D1_utilzando_ADOXtra.?=
          aldus
          Sorry - but my spanish is more than rusty - and the
          only thing i understand is "ADO xTra" and "Director11".
          As far as i know the ADO xTra is not compatible for D11 at this
          time - but i could be wrong in this place.

          Regards
          Aldus
          • 2. =?iso-8859-1?Q?Re:_Problema_con_acentos_y_=D1_utilzando_ADOXtra.?=
            Level 7
            I've just publish my question in spanish because it doesn't affect to
            english characters and also because my english is quite rusty too. ;-)

            The ADOXtra works perfectly on D11 with the exception of this. The spanish
            characters like: "ñ,á,é,í,ó,ú,ü" are not shown in a textbox control, but I
            don't know if it's due to the ADOXtra or not.

            Thank you very much for your answer.

            Regards from Spain.



            "aldus" <webforumsuser@macromedia.com> escribió en el mensaje de noticias
            news:g5kcsk$3kd$1@forums.macromedia.com...
            > Sorry - but my spanish is more than rusty - and the
            > only thing i understand is "ADO xTra" and "Director11".
            > As far as i know the ADO xTra is not compatible for D11 at this
            > time - but i could be wrong in this place.
            >
            > Regards
            > Aldus
            >

            • 3. =?iso-8859-1?Q?Problema_con_acentos_y_=D1_utilzando_ADOXtra.?=
              aldus Level 1
              Hm ... are you running a MySQL DB and have set the
              collation to "general utf-8"?
              Are the chars not display, or "miss"-displayed inside the
              textmember.
              And at last - are you using a font witch have the chars defined/inside?
              Got some problems with greek-chars a time ago - chars wasn't defined
              in the font itself - changing to another had solved it .

              Regards
              Aldus
              • 4. =?iso-8859-1?Q?Re:_Problema_con_acentos_y_=D1_utilzando_ADOXtra.?=
                Level 7
                I'm using an Access DB (.mdb).
                When I place a text box control on the stage, I check a font like "Arial"
                and I write inside, the chars are displayed perfectly.
                The problem appears when I load the text control with the .mdb data.

                Thanks again Aldus.


                "aldus" <webforumsuser@macromedia.com> escribió en el mensaje de noticias
                news:g5kkjl$b8v$1@forums.macromedia.com...
                > Hm ... are you running a MySQL DB and have set the
                > kollation to "general utf-8"?
                > Are the chars not display, or "miss"-displayed inside the
                > textmember.
                > And at last - are you using a font witch have the chars defined/inside?
                > Got some problems with greek-chars a time ago - chars wasn't defined
                > in the font itself - changing to another had solved it .
                >
                > Regards
                > Aldus
                >

                • 5. Re: =?iso-8859-1?Q?Problema_con_acentos_y_=D1_utilzando_ADOXtra.?=
                  aldus Level 1
                  I'm sorry as i'm not familar with Access.mdb and the ADOxtra so i
                  could only make a shoot in the dark and assumee/suggest
                  the database isn't utf-8 (compatible/formated).
                  But again: i could be (very) wrong in this place.

                  Sorry, but i'm sure someone here could help out

                  Regards
                  Aldus
                  • 6. Re: Problema con acentos y =?ISO-8859-1?Q?=D1_utilzando_ADOX?=   =?ISO-8859-1?Q?tra=2E?=
                    Level 7
                    Since ADOxtra has not been updated to use Director 11, it can not handle
                    Unicode characters. The accented characters will be unavailable in
                    Director 11 until the author of the xtra makes a new compatible
                    version... if they ever release a Director 11 version...
                    • 7. =?iso-8859-1?Q?Re:_Problema_con_acentos_y_=D1_utilzando_ADOXtra.?=
                      Level 7
                      Could you suggest me any solution? Any other Xtra or so.

                      Thanks Mike.

                      "Mike Blaustein" <mblaustein@gmail.com> escribió en el mensaje de noticias
                      news:g5krte$ikc$1@forums.macromedia.com...
                      > Since ADOxtra has not been updated to use Director 11, it can not handle
                      > Unicode characters. The accented characters will be unavailable in
                      > Director 11 until the author of the xtra makes a new compatible version...
                      > if they ever release a Director 11 version...

                      • 8. =?iso-8859-1?Q?Re:_Problema_con_acentos_y_=D1_utilzando_ADOXtra.?=
                        Level 7
                        Thanks again Aldus
                        I'll try to find any solution.

                        "aldus" <webforumsuser@macromedia.com> escribió en el mensaje de noticias
                        news:g5kqdr$h6q$1@forums.macromedia.com...
                        > I'm sorry as i'm not familar with Access.mdb and the ADOxtra so i
                        > could only make a shoot in the dark and assumee/suggest
                        > the database isn't utf-8 (compatible/formated).
                        > But again: i could be (very) wrong in this place.
                        >
                        > Sorry, but i'm sure someone here could help out
                        >
                        > Regards
                        > Aldus
                        >
                        >

                        • 9. Re: Problema con acentos y =?ISO-8859-1?Q?=D1_utilzando_ADOX?=   =?ISO-8859-1?Q?tra=2E?=
                          Level 7
                          The only database xtras I am aware of that have updated to D11 versions
                          are Arca and Valentina. Hopefully one of them will work for you.
                          • 10. Re: Problema con acentos y Ñ utilzando ADOXtra.
                            Level 7
                            Download:
                            http://xtrema.rtr.gr/beta/xtrema.rar

                            I believe that the codepage you should use is 1252. if not, check
                            http://www.microsoft.com/globaldev/reference/WinCP.mspx for the proper code.
                            Assuming the string you get from ado is adoStr, use:

                            uniStr= _aa(adoStr, 1252).dirstring
                            or
                            uniStr= _aa(adoStr).dirstring -- this will use your system's code page.

                            _aa() will perform a raw import of director string adoStr (ansi from ansi),
                            and .dirstring
                            will return a director string according to the dir version (ansi, or utf8
                            for
                            dir11).
                            To check if the import will work as expected, you can try:
                            _aa(adoStr,1252).pop()

                            To update the database to utf8 format, you can read all entries and replace
                            them with the converted strings.

                            You could also use the xtra's xCom object to access your database, which can
                            easilly handle such issues and supports all vb data types - just that it's
                            not documented yet. It soon will be though.

                            Let me know if the above works for you.


                            "Locknar" <no_gracias@paso.com> wrote in message
                            news:g5ktk7$kff$1@forums.macromedia.com...
                            > Could you suggest me any solution? Any other Xtra or so.
                            >
                            > Thanks Mike.
                            >
                            > "Mike Blaustein" <mblaustein@gmail.com> escribió en el mensaje de noticias
                            > news:g5krte$ikc$1@forums.macromedia.com...
                            >> Since ADOxtra has not been updated to use Director 11, it can not handle
                            >> Unicode characters. The accented characters will be unavailable in
                            >> Director 11 until the author of the xtra makes a new compatible
                            >> version... if they ever release a Director 11 version...
                            >



                            • 11. =?iso-8859-1?Q?Re:_Problema_con_acentos_y_=D1_utilzando_ADOXtra.?=
                              Level 7
                              ¡¡¡¡¡¡¡ IT WORKS !!!!!!!

                              I've used the 1252 codepage and works perfectly.
                              Now I understand your nick name.

                              Thank you very much "alchemist"


                              "alchemist" <unknown@domain.com> escribió en el mensaje de noticias
                              news:g5l1el$on1$1@forums.macromedia.com...
                              > Download:
                              > http://xtrema.rtr.gr/beta/xtrema.rar
                              >
                              > I believe that the codepage you should use is 1252. if not, check
                              > http://www.microsoft.com/globaldev/reference/WinCP.mspx for the proper
                              > code.
                              > Assuming the string you get from ado is adoStr, use:
                              >
                              > uniStr= _aa(adoStr, 1252).dirstring
                              > or
                              > uniStr= _aa(adoStr).dirstring -- this will use your system's code page.
                              >
                              > _aa() will perform a raw import of director string adoStr (ansi from
                              > ansi), and .dirstring
                              > will return a director string according to the dir version (ansi, or utf8
                              > for
                              > dir11).
                              > To check if the import will work as expected, you can try:
                              > _aa(adoStr,1252).pop()
                              >
                              > To update the database to utf8 format, you can read all entries and
                              > replace
                              > them with the converted strings.
                              >
                              > You could also use the xtra's xCom object to access your database, which
                              > can
                              > easilly handle such issues and supports all vb data types - just that it's
                              > not documented yet. It soon will be though.
                              >
                              > Let me know if the above works for you.
                              >
                              >
                              > "Locknar" <no_gracias@paso.com> wrote in message
                              > news:g5ktk7$kff$1@forums.macromedia.com...
                              >> Could you suggest me any solution? Any other Xtra or so.
                              >>
                              >> Thanks Mike.
                              >>
                              >> "Mike Blaustein" <mblaustein@gmail.com> escribió en el mensaje de
                              >> noticias
                              >> news:g5krte$ikc$1@forums.macromedia.com...
                              >>> Since ADOxtra has not been updated to use Director 11, it can not handle
                              >>> Unicode characters. The accented characters will be unavailable in
                              >>> Director 11 until the author of the xtra makes a new compatible
                              >>> version... if they ever release a Director 11 version...
                              >>
                              >
                              >
                              >

                              • 12. =?iso-8859-1?Q?Re:_Problema_con_acentos_y_=D1_utilzando_ADOXtra.?=
                                Level 7
                                Could you tell me how can I avoid the debug window who appears when you
                                execute and exit the program?
                                It's really annoying.
                                Thanks.

                                "alchemist" <unknown@domain.com> escribió en el mensaje de noticias
                                news:g5l1el$on1$1@forums.macromedia.com...
                                > Download:
                                > http://xtrema.rtr.gr/beta/xtrema.rar
                                >
                                > I believe that the codepage you should use is 1252. if not, check
                                > http://www.microsoft.com/globaldev/reference/WinCP.mspx for the proper
                                > code.
                                > Assuming the string you get from ado is adoStr, use:
                                >
                                > uniStr= _aa(adoStr, 1252).dirstring
                                > or
                                > uniStr= _aa(adoStr).dirstring -- this will use your system's code page.
                                >
                                > _aa() will perform a raw import of director string adoStr (ansi from
                                > ansi), and .dirstring
                                > will return a director string according to the dir version (ansi, or utf8
                                > for
                                > dir11).
                                > To check if the import will work as expected, you can try:
                                > _aa(adoStr,1252).pop()
                                >
                                > To update the database to utf8 format, you can read all entries and
                                > replace
                                > them with the converted strings.
                                >
                                > You could also use the xtra's xCom object to access your database, which
                                > can
                                > easilly handle such issues and supports all vb data types - just that it's
                                > not documented yet. It soon will be though.
                                >
                                > Let me know if the above works for you.
                                >
                                >
                                > "Locknar" <no_gracias@paso.com> wrote in message
                                > news:g5ktk7$kff$1@forums.macromedia.com...
                                >> Could you suggest me any solution? Any other Xtra or so.
                                >>
                                >> Thanks Mike.
                                >>
                                >> "Mike Blaustein" <mblaustein@gmail.com> escribió en el mensaje de
                                >> noticias
                                >> news:g5krte$ikc$1@forums.macromedia.com...
                                >>> Since ADOxtra has not been updated to use Director 11, it can not handle
                                >>> Unicode characters. The accented characters will be unavailable in
                                >>> Director 11 until the author of the xtra makes a new compatible
                                >>> version... if they ever release a Director 11 version...
                                >>
                                >
                                >
                                >

                                • 13. Re: Problema con acentos y Ñ utilzando ADOXtra.
                                  Level 7
                                  Great to hear this, Locknar!
                                  Far as the nickname is concerned though, it comes from when I often had to
                                  resort to awkward methods to deal with director quirks. Now it's all
                                  about solutions, not workarounds, so perhaps I should reconsider ;-).


                                  "Locknar" <no_gracias@paso.com> wrote in message
                                  news:g5l91n$3j4$1@forums.macromedia.com...
                                  > ¡¡¡¡¡¡¡ IT WORKS !!!!!!!
                                  >
                                  > I've used the 1252 codepage and works perfectly.
                                  > Now I understand your nick name.
                                  >
                                  > Thank you very much "alchemist"
                                  >
                                  >
                                  > "alchemist" <unknown@domain.com> escribió en el mensaje de noticias
                                  > news:g5l1el$on1$1@forums.macromedia.com...
                                  >> Download:
                                  >> http://xtrema.rtr.gr/beta/xtrema.rar
                                  >>
                                  >> I believe that the codepage you should use is 1252. if not, check
                                  >> http://www.microsoft.com/globaldev/reference/WinCP.mspx for the proper
                                  >> code.
                                  >> Assuming the string you get from ado is adoStr, use:
                                  >>
                                  >> uniStr= _aa(adoStr, 1252).dirstring
                                  >> or
                                  >> uniStr= _aa(adoStr).dirstring -- this will use your system's code page.
                                  >>
                                  >> _aa() will perform a raw import of director string adoStr (ansi from
                                  >> ansi), and .dirstring
                                  >> will return a director string according to the dir version (ansi, or utf8
                                  >> for
                                  >> dir11).
                                  >> To check if the import will work as expected, you can try:
                                  >> _aa(adoStr,1252).pop()
                                  >>
                                  >> To update the database to utf8 format, you can read all entries and
                                  >> replace
                                  >> them with the converted strings.
                                  >>
                                  >> You could also use the xtra's xCom object to access your database, which
                                  >> can
                                  >> easilly handle such issues and supports all vb data types - just that
                                  >> it's
                                  >> not documented yet. It soon will be though.
                                  >>
                                  >> Let me know if the above works for you.
                                  >>
                                  >>
                                  >> "Locknar" <no_gracias@paso.com> wrote in message
                                  >> news:g5ktk7$kff$1@forums.macromedia.com...
                                  >>> Could you suggest me any solution? Any other Xtra or so.
                                  >>>
                                  >>> Thanks Mike.
                                  >>>
                                  >>> "Mike Blaustein" <mblaustein@gmail.com> escribió en el mensaje de
                                  >>> noticias
                                  >>> news:g5krte$ikc$1@forums.macromedia.com...
                                  >>>> Since ADOxtra has not been updated to use Director 11, it can not
                                  >>>> handle
                                  >>>> Unicode characters. The accented characters will be unavailable in
                                  >>>> Director 11 until the author of the xtra makes a new compatible
                                  >>>> version... if they ever release a Director 11 version...
                                  >>>
                                  >>
                                  >>
                                  >>
                                  >



                                  • 14. Re: Problema con acentos y Ñ utilzando ADOXtra.
                                    Level 7
                                    > It's really annoying.
                                    You understand that the version you are using is a beta, and should not be
                                    used in release products, right?
                                    You can perform the required conversions, update your existing database, and
                                    then stop using it. If you don't call any commands, the debugger won't
                                    appear.
                                    Case you want to try some of it's features though: xDebuggerEnabled(0)
                                    I wonder how you could do that without the docs, though..
                                    The ones on the site refer to older versions of the xtra, and the new ones
                                    won't be released till next week.

                                    "Locknar" <no_gracias@paso.com> wrote in message
                                    news:g5la63$4n6$1@forums.macromedia.com...
                                    > Could you tell me how can I avoid the debug window who appears when you
                                    > execute and exit the program?
                                    > It's really annoying.
                                    > Thanks.
                                    >
                                    > "alchemist" <unknown@domain.com> escribió en el mensaje de noticias
                                    > news:g5l1el$on1$1@forums.macromedia.com...
                                    >> Download:
                                    >> http://xtrema.rtr.gr/beta/xtrema.rar
                                    >>
                                    >> I believe that the codepage you should use is 1252. if not, check
                                    >> http://www.microsoft.com/globaldev/reference/WinCP.mspx for the proper
                                    >> code.
                                    >> Assuming the string you get from ado is adoStr, use:
                                    >>
                                    >> uniStr= _aa(adoStr, 1252).dirstring
                                    >> or
                                    >> uniStr= _aa(adoStr).dirstring -- this will use your system's code page.
                                    >>
                                    >> _aa() will perform a raw import of director string adoStr (ansi from
                                    >> ansi), and .dirstring
                                    >> will return a director string according to the dir version (ansi, or utf8
                                    >> for
                                    >> dir11).
                                    >> To check if the import will work as expected, you can try:
                                    >> _aa(adoStr,1252).pop()
                                    >>
                                    >> To update the database to utf8 format, you can read all entries and
                                    >> replace
                                    >> them with the converted strings.
                                    >>
                                    >> You could also use the xtra's xCom object to access your database, which
                                    >> can
                                    >> easilly handle such issues and supports all vb data types - just that
                                    >> it's
                                    >> not documented yet. It soon will be though.
                                    >>
                                    >> Let me know if the above works for you.
                                    >>
                                    >>
                                    >> "Locknar" <no_gracias@paso.com> wrote in message
                                    >> news:g5ktk7$kff$1@forums.macromedia.com...
                                    >>> Could you suggest me any solution? Any other Xtra or so.
                                    >>>
                                    >>> Thanks Mike.
                                    >>>
                                    >>> "Mike Blaustein" <mblaustein@gmail.com> escribió en el mensaje de
                                    >>> noticias
                                    >>> news:g5krte$ikc$1@forums.macromedia.com...
                                    >>>> Since ADOxtra has not been updated to use Director 11, it can not
                                    >>>> handle
                                    >>>> Unicode characters. The accented characters will be unavailable in
                                    >>>> Director 11 until the author of the xtra makes a new compatible
                                    >>>> version... if they ever release a Director 11 version...
                                    >>>
                                    >>
                                    >>
                                    >>
                                    >