Closed. This question is not written in English. It is not currently accepting answers.
Stack Overflow is an English-only site. The author must be able to communicate in English to understand and engage with any comments and/or answers their question receives. Don't translate this post for the author; machine translations can be inaccurate, and even human translations can alter the intended meaning of the post.
Closed 3 days ago.
Improve this question
Estoy intentando conectar FlutterFlow con Firebase siguiendo todos los paso de la documentacion, al agregar los roles del usuario editor firebase#flutterflow.io logro asignarle la funcion Usuario de Cuenta de servicio pero al intentar agregar la funcion Administrador de funciones en la nube(Cloud Function Admin) esta no me aparece para asignarla ya que no esta en la lista. Por favor alguien que sepa como hacerlo. Gracias.
enter image description here
enter image description here
Related
I want to do some text analysis of instagram photo descriptions which often contain a mix of text, hashtags, #username, urls etc. and are also written in different languages. My method of extraction of the text seems to have stored the text in UTF-8. My first task is to convert all the strings to latin1 before identifying languages and then translating. I have a feeling its because the italian text contains an emoji code ðŸ˜, which the converter cant handle? Any help or directions to good tutorials appreciated!
t.de <- "mein bozen. schönheit liegt im auge des betrachters. worauf
richtest DU tagtäglich deinen blick? auf die vielen kleinen wunder des
lebens\\, auf das lächeln eines gesprächspartners\\n#lavitaebella
#perspektivenwechsel #entscheidedich #blickwinkel
#schönheitliegtimaugedesbetrachters"
t.it <- "ðŸ˜\u008dðŸ˜\u008dCi si può innamorare di una ricamatice???
ðŸ˜\u008dðŸ˜\u008d Personalizzazioni di tutti i tipi!! #ricamo #ricamato
#personalizzato #elefante #palloncini #tenero #baby #nascita #amoredimamma
#cuccioloso"
iconv(t.de, "UTF-8","latin1") #this works fine
iconv(t.it, "UTF-8","latin1") #this doesnt work
rawde=stri_encode(t.de, from="UTF-8", to="latin1", to_raw=TRUE)
stri_encode(rawde, "latin1") #using the 'stringi' approach also works for de but not for it
I am using the translator component of symfony, always i have used this component and its work correctly, but, in a new project, i have started to use this component and the second level of translations are not recognized for my debugging bar.
Example:
//messages.es.yml
#USUARIOS
usuarios:
gestion: Gestion de usuarios
listado: Listado de usuarios
nuevo: Nuevo usuario
Using translate in controller or twig:
//SomeController.php
$breadcrumbs->addRouteItem($this->get("translator")->trans("usuarios.nuevo"), "backend_usuario_register");
// someFile.html.twig
{{ "usuarios.nuevo" | trans }}
In both cases return: usuarios.nuevo
Where is the problem? :/
EDIT 1
Fixed, the problem was that the keyword 'usuarios' was defined above as: usuarios: Usuarios.
Now I have another problem, how can I give a value to the primary id so that it leaves without error?
I have it now, but it returns error:
//messages.es.yml
#USUARIOS
usuarios: Usuarios
gestion: Gestion de usuarios
listado: Listado de usuarios
nuevo: Nuevo usuario
Thank!
Im trying to create a field in the team entity to be able to select its zone/territory.
Looking in the DDBB i see that the field comp_secterr uses the entry type with id 53 (Entry type Territory) with this SQL
SELECT * FROM Custom_Edits WHERE ColP_ColName LIKE ('comp_secterr');
but when creaing a new field, in the select, there is not option to choose the Entry Type 53
<select class="EDIT" size="1" name="entrytype" id="entrytype" onchange="document.EntryForm.hiddenmode.value=1;document.EntryForm.submit();"><option value="15">Texto con búsqueda de casilla de verificación</option><option value="25">Producto</option><option value="27">Selección inteligente</option><option value="28">Selección múltiple</option><option value="42">Fecha sólo</option><option value="51">Divisa</option><option value="56">Selección de búsqueda avanzada</option><option value="57">Minutos</option><option value="59">Símbolos de las monedas</option><option value="63">Selección de grupo de usuarios</option><option value="10" selected="">Texto</option><option value="44">Procedimiento almacenado</option><option value="45">Casilla</option><option value="50">Número de teléfono</option><option value="11">Texto MultiLínea</option><option value="12">Dirección de correo electrónico</option><option value="13">URL WWW</option><option value="21">Selección</option><option value="22">Selección de usuario</option><option value="23">Selección de Equipo</option><option value="31">Número entero</option><option value="32">Numérico</option><option value="41">Fecha y hora</option></select>
Entry Type 53 is reserved for Territory fields, but is not accessible via the front-end. To use it, you need to update the Custom_Edits table directly using a query similar to this:
UPDATE custom_Edits SET colp_entrytype = 53 WHERE ...
Make sure you do a full metadata refresh after as well.
While it is not absolutely necessary, it is also good for consistency to name Territory fields _secterr (E.g. comp_secterr)
Six Ticks Support
My doubt is, when I make a movie search by title in a another different language than English, why the search is more precise if use HTTP access than SQL ?
For example i want to retrieve info about the Movie "El gran Robo" (spanish title) original title "Flypaper".
case 1) using SQL access
ia = IMDb(accessSystem='sql', uri = "mysql://devel:password#localhost/imdb")
movies = ia.search_movie("el gran robo")
for m in movies:
print m['titles']
OUTPUT:
7 uomini e un cervello
El gran rabo
List item
Mathias Sandorf
La gran revista
Green River
Green River
The Grim Reaper
The Grim Reaper
La commare secca
Anthropophagus
La verte moisson
Granny R.I.P.
Gehirnreflexe
Rosso sangue
Green River Killer
Grammar Revolution
German Whorefare 4
Cuori in campo
Grim Reaper
Grim Reaping
case 2) using HTTP access
ia = IMDb()
movies = ia.search_movie("el gran robo")
for m in movies:
print m['titles']
OUTPUT:
Flypaper
The Big Steal
Robbery
El gran robo del tren
El gran robo de Lorenza
The Bank Job
The First Great Train Robbery
Grand Theft Auto
The Great Train Robbery
Hot Money
7 uomini e un cervello
The Great Missouri Raid
Le Great Dane Robbery
El gran río
Después del gran robo
Gran-Robo tonda
As you can see, the search with HTTP returned the right Movie, Flypaper.
Is it possible get the same results using SQL ?
Short version: some data are missing in the plain text data files.
Extended explanation in the imdbpy-help mailing list: http://sourceforge.net/p/imdbpy/mailman/message/33067664/
I have the following somewhere in a page:
<asp:Localize ID="locChangePasswordPrompt" runat="server"
Text="Change Your Password" meta:resourcekey="locChangePasswordPrompt" />
I am localizing using sql server database and I have stored the FRENCH corresponding values in the db.
Do if u do a query:
SELECT TOP 1000 [ResourceType]
,[CultureCode]
,[ResourceKey]
,[ResourceValue]
,[Preserve]
FROM [CLeX].[dbo].[StringResource]
where resourcekey like 'locChangePasswordPrompt%'
You get the values:
ResourceType CultureCode ResourceKey ResourceValue Preserve
common/UserPreferences.aspx en locChangePasswordPrompt 1
common/UserPreferences.aspx en locChangePasswordPrompt.Text Change Your Passwordss 1
common/UserPreferences.aspx en-US locChangePasswordPrompt 1
common/UserPreferences.aspx en-US locChangePasswordPrompt.Text Change Your Passwordss 1
common/UserPreferences.aspx fr locChangePasswordPrompt 1
common/UserPreferences.aspx fr locChangePasswordPrompt.Text Changez votre mot de passe 1
However, I am still not able to get the FRENCH values at all. In fact, not even the English values are being pulled from the DB. Localize simply pulls the text from its text attribute.
What could possibly be the reason?
Did you configure your DB Resource Provider?